Workflow Triggers

A workflow trigger determines when a user will enter a given workflow. It is represented by a green node at the top of the workflow.

# Table of contents

# Types of triggers

Iterable workflows can use the triggers described below:

# Received API Trigger

Triggers the workflow after a call to the POST /api/workflows/triggerWorkflow API.

# Triggered by Workflow

Triggers a workflow from another workflow. For more information, read Trigger a Workflow from Other Workflows.

# Added Item to Cart

Triggers a workflow after a user adds an item to their cart. Use the POST /api/commerce/updateCart API to send cart events. This is the trigger for a shopping cart abandonment campaign.

# Purchased

Triggers a workflow after a customer makes a purchase. Send purchase events with the POST /api/commerce/trackPurchase API endpoint. This is the trigger for an order confirmation or post-purchase review email.

# Scheduled Recurring List

Periodically checks a specified list (standard or dynamic) and passes the members of that list into the workflow. Use the node to configure the frequency with which this happens.

# Subscribed To List

Triggers a workflow when a user joins a static list. This can be useful if you have a subscriber list for new users and you would like to send new signups through a welcome email series. When uploading the list or adding new users to the list, check the box for Send List Membership & Field Change Events to Trigger Workflow.

# Unsubscribed From List

Triggers a workflow when a user unsubscribes from a list. This may be useful for sending one last confirmation email when a user unsubscribes from a list.

# Unsubscribed From Message Type

Triggers a workflow when a user unsubscribes from a message type. This may be useful for sending one last confirmation email when a user unsubscribes from a message type or changes their subscription preferences.

For more information, read Message Channels and Message Types Overview.

# Unsubscribed From Channel

Triggers a workflow when a user unsubscribes from a message channel. This may be useful for sending one last confirmation email when a user unsubscribes from your marketing communications.

For more information, read Message Channels and Message Types Overview.

# User Profile Field Updated

Triggers a workflow after an update to a specified user profile field. For example, when a person moves to a new city and their location changes, this node could trigger a workflow to send a welcome email.

This trigger works regardless of how user profile updates are made (CSV or API) or whether the new user profile value differs from the old value.

To trigger this workflow during a CSV upload, check the Send Events option:

# Triggered Custom Event

Triggers a workflow after a custom event has occurred. Examples of custom events: when a user clicks a button, downloads a file, views five items on your website, etc. Send custom events with the POST /api/events/track API.

# Opened an Email / Clicked an Email

Triggers a workflow after a user opens, or clicks a link in, a specific email campaign. For example, this might be useful when a user opens or clicks a promo email about an upcoming product, which may indicate an interest in learning more.

# Received an SMS

Triggers a workflow when a subscriber responds to an SMS (for example, if you want to follow up with that user in some way).

# Opened Push

Triggers a workflow when a subscriber opens a push notification associated with a particular push notification campaign.

# Clicked An In App

Triggers a workflow when a subscriber clicks an in-app message associated with a particular in-app campaign.

# Filters in workflow triggers

Use filters to narrow the circumstances in which a trigger kicks off a workflow. Filters can examine user profile fields, historical event fields or fields on the triggering event for the workflow.

To apply a filter to a workflow trigger node, double-click the node and enable the Use Filter toggle. Then, configure the filter as necessary.

For example, the following configuration specifies that the trigger should apply only to purchase events for which grandTotal is greater than 50:

To learn more about workflows, read Workflow Overview.