The name of the module where you can create automated workflows. Sometimes it’s used as an adjective to describe the type of workflow you can create in the module.
The type of the workflow that involves data integration with external sources. Such a workflow can be triggered by receiving data requests from external tools (for example, an ecommerce platform) and the data from Synerise can be sent to external tools in response to circumstances specified in the workflow. To build such a workflow, users can use only business-oriented nodes and it doesn’t require customer data.
The area on the interface where you create a diagram.
All nodes on canvas must be connected in an order. Remember that some nodes have more than one required connection. You can also split connections between nodes using Split Path node.
The structure of the workflow (nodes and paths).
The counter you can find in the statistics of a node. It shows the number of times profiles entered and left a node.
The counter you can find in the statistics of a node. It shows the number of times profiles arrived at a node.
While defining the settings of a node, a user has the possibility of using data (event parameters) received in the trigger nodes or in Profile Filter nodes in a diagram. This provides a possibility of inserting dynamic values, for example in the input or request in a webhook.
Full documentation about event context is available here.
In the workflow that has the following structure:
Transaction (trigger) > Send email (action) > End
The template of the email in the Send email action contains a dynamic value taken from the parameters of the
transaction.charge event that defines the total cost of the purchase:
Thank you for your purchase. The total value of your cart is:
The number of times customers arrived at the final step of the workflow (the End node). The number is not equal to the number of unique customers who finished the workflow - one customer can participate in the workflow many times (if the customer meets the conditions of the trigger that starts the workflow).
It is selected in the beginning of data transformation and it is designed to help you receive the output data of the transformation. There are standard and custom goals. The standard goals are import of transactions, events, and profiles to Synerise. The Custom goal requires you to know the output of the transformation.
It allows you to receive data from external sources, which triggers a workflow. Check how to create an incoming integration.
These statistics are displayed on the list of workflows. It informs about the number of times a workflow is launched (and still in progress).
Node Context menu
The menu that appears after clicking on the node the icon.
The type of the workflow that uses profile data and reacts to the profile behavior in a defined way.
It allows you to send data to external sources but also use Synerise open API. Check how to prepare an outgoing integration.
A profile starts a path every time they meet the requirements of the trigger of a workflow. The path reflects the progress of a profile in a workflow.
The duration of the state between arriving at the step and execution of the activity set in the node logic (it’s connected with the Delay node). This piece of information is available in the statistics of the node.
This piece of information is available in the statistics of a node. Time it took a path to reach a step from the starting point (trigger).
See the complete documentation on the workflow statistics here.
A sequence of nodes that together describe a scenario and define the course of actions to be performed in defined circumstances. This term refers to the concept of an automated process - a customer entering and completing this process. The structure of the workflow is referred to in the documentation as a diagram.
The limit users use to define the allowed number of repetitions of the entire worfklow. It also concerns the limits within the nodes. You can find more information about capping here.
A workflow can have one of the following statuses:
- Draft - It is a workflow that has been saved but it hasn’t been activated yet.
- Running - It’s an activated workflow.
- Paused - It’s a workflow that is stopped temporarily.
- Stopped - It’s a workflow that is stopped permanently.
The status of the workflow changes to Stopped when (applies only to workflows triggered by Audience):
- it’s been 62 days from the latest execution of the trigger,
- it is a one-off workflow and it is completed,
- the limit of repetitions in the trigger settings runs out
In the audit log, this change of the workflow status will be marked as a change done by
Each status allows certain scope of actions. The scope of actions:
*The editing option allows changing the settings in the nodes only. You won’t be able to add new nodes to the diagram.