Forum Discussion

Thijs Lecomte's avatar
Thijs Lecomte
Bronze Contributor
Feb 25, 2020

Get full data into Playbook

Hi   We are currently trying to automate some alerts through Playbooks. We created a custom alert that checks for Impossible Travel Alerts from MCAS. This works well. But the issue is that some d...
GaryBushey's avatar
GaryBushey
Bronze Contributor
Jun 07, 2021

SocInABox 1) I don't think there is a set rule, it really depends on what type of information you are trying to obtain

2)  Usually, I run the playbook without the parse JSON action first, look at the run, copy the data that I need to parse from the output of the action that creates it, and then paste it into the parse JSON action as sample data and let the action handle the parsing. 

SocInABox's avatar
SocInABox
Iron Contributor
Jun 07, 2021

Thanks GaryBushey 

"look at the run" is what I needed to know, thanks!

 

What I'm saying about the parse json rule is that some operators don't need it as a predecessor and some do - for example if you want to include fields from your alert in the email function you must use parse json first. But maybe the send email is a special exception?

  • GaryBushey's avatar
    GaryBushey
    Bronze Contributor
    Jun 07, 2021

    SocInABox It depends on the field you are looking to use.  Some of the information is stored as JSON and some of it is returned directly as a variable.

    • SocInABox's avatar
      SocInABox
      Iron Contributor
      Jun 20, 2021
      thanks Gary.
      Turned out a bit more practice with playbooks showed me the light :).
      simply monitoring the output results and understanding where to place your functions (in or our of a FOR loop) were my weaknesses.