Actions

An action is a side effect that starts when the flow reaches it. Use an action to track an event, to send data to an external service, or to call a webhook.

Set up an action

Name: The name that the dashboard shows. Your visitors do not see it.

Key: The identifier that your application uses for this action. Your visitors do not see it.

Register in your application

Each action key must match a key in the actions object that you pass to createClient(). See How to register an action handler for the code, and SDK actions for what the handler receives and returns.

Use actions in flows

In the flow builder, drag an action from the library onto the canvas. Connect it to the point in the flow where you want it to start.

An action runs when the flow reaches its node. It does not interrupt your visitor. By default the flow continues to the next connected node.

An action node can carry a success branch and a failure branch. Which one the flow takes depends on whether your handler throws, and a returned false is a success. See How an action decides which way to go.

Reuse actions

An action belongs to the project. Use the same action in more than one experience flow. A change to the options of an action applies at every place that uses it.

Related

• How to add a step, a field, an action, or a condition
• How to register an action handler
• SDK actions — what the handler receives and returns.