Reusing event context from preceding nodes

While defining the settings of a node, you can use data (event parameters) received in the preceding nodes in a diagram. This enables inserting dynamic values (for example, a customer’s name or ID) in the input of the following nodes in a workflow or a request in a webhook. Such reuse in automations is called the event context.

How it works

The context of an event is kept in the {{ event.params }} Jinjava variable. This variable contains all parameters of the event from the preceding node (either Profile Event (a trigger) and/or Profile Event Filter (a condition)).

At the beginning of the workflow, {{ event.params }} holds the context of an event from the trigger, it can be kept throughout the whole workflow and can be referred to at any moment unless the workflow contains a Profile Event Filter (which is the only node that changes the context). Then, {{ event.params }} takes over the event context from the Profile Event Filter node. You also have the possibility to refer to event context from any trigger or Profile Filter in the workflow.

You can refer to the event parameters in two ways:

When to use it

When a workflow contains nodes (building elements) that are based on events: Profile Event and Profile Event Filter.

Tips and tricks

• You can put a parameter name in square brackets: {{ event.params['example'] }}. It is helpful when a parameter name contains special characters, like in og:url or $orderStatus, the jinjava formula for these parameters is as follows: {{ event.params['og:url'] }} and {{ event.params['$orderStatus'] }}.
• You can use {{ event.params }} in Schema builder and in the message templates sent from the Automation module as well.
• It is a good practice to use {{ event.params }} wherever you can instead of using aggregates, filters, and any other elements that require a call to the database.
• If you want to set {{ event.params }} as a variable in your Jinjava code, you must omit the brackets: {{ }}.
  Example:

{% set foo = event.params.example %}

Example of use

The example presents a workflow that is triggered by a particular customer activity (event), as a result a webhook is sent to the external tool, the Synerise system waits until it gets the response from the tool. If so, the customer data is updated with information received through the webhook response.

Select a trigger

1. Add the Profile Event node.
2. Click the node twice and select the event.
3. Confirm by clicking Apply.
   Result: The selected event launches a workflow.
4. Click the plus icon on the node.

Send a webhook to an external tool

4. From the dropdown list, select Outgoing Webhook.
5. Click the node twice and define the settings of the node.
   
   Tip: Read more about Outgoing Webhook.
6. Select the Custom webhook tab.
7. Prepare the body of the webhook request.
8. Confirm by clicking Apply.
   Result: Right after the event occurrence (defined in the Profile Event node), a webhook is sent to the external tool.

Check if the response is received

8. On the Outgoing Webhook node, click the plus icon.
9. From the dropdown list, select Profile Event Filter.
10. Click the Profile Event Filter node twice.
11. From the All events dropdown list, select webhook.response.

    

12. Confirm by clicking Apply.
    Result: When the workflow launches and the webhook is sent, the system checks if a webhook response is received (the webhook.response event is visible on the customer’s card in Profiles). If so, the customer continues the workflow.

Modify customer data with info received from response

13. Click the plus icon on the Profile Event Filter node.
14. From the dropdown list, select the Update Profile node.
15. Click the node twice.
16. Select the customer attribute to be modified.
17. Select the Change option.
    Result: A field appears.
18. In the field, enter: {{event.params['response_parameter_name']}} (replace parameter_name with the actual name of the parameter).

    

19. Confirm by clicking Apply.
20. Click the plus button on the Update Profile node.
21. Select End.