The workflow trigger is what determines when a user will enter a given workflow. It is represented by a green node at the top of the workflow (see below).
There are many types of potential triggers:
- Received API Trigger
- Triggered By Workflow
- Added Item To Cart
- Scheduled Recurring List
- Subscribed To List
- Unsubscribed From List
- Unsubscribed From Message Type
- Unsubscribed From Channel
- User Profile Field Updated
- Triggered Custom Event
- Opened An Email
- Clicked An Email
- Received An SMS
Received API Trigger
You can trigger the workflow by calling the Iterable triggerWorkflow API.
Triggered By Workflow
You can trigger the workflow from another workflow. More information here.
Added Item to Cart
A customer can enter the workflow after they add an item to their cart. You can send cart events via the Iterable commerce updateCart API. This is the trigger for a shopping cart abandonment campaign.
A customer can enter the workflow after they’ve made a purchase. You can send purchase events via the Iterable commerce trackPurchase API. This is the trigger for an order confirmation or post-purchase review email.
Scheduled Recurring List
This option will check a specified list (standard or dynamic) on a recurring basis, then pass the members of that list into the workflow. The schedule of that recurrence is set directly within the node (see screenshot below).
Subscribed to List
A workflow can be triggered when someone joins a static list. This is 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, be sure to check the box for “Send list membership & field change events to trigger workflow.”
Unsubscribed from List
You can also trigger 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
You can also trigger 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 his/her subscription preferences. Learn more about message types here.
Unsubscribed from Channel
You can also trigger a workflow when a user unsubscribes from an entire message channel. This may be useful for sending one last confirmation email when a user unsubscribes from your marketing communications. Learn more about message channels here.
User Profile Field Updated
A workflow can be triggered when a field on a user profile is updated. For example, when a person moves to a new city and his/her location changes, you may want to create an email that welcomes them to a new city. This will be triggered whether you are updating the field via CSV or API.
If triggering via CSV upload, be sure to check this box while uploading:
If you update the field and supply a value for a field that has the same value as the current field (for example, if currentCity = San Francisco and you update the field with currentCity = San Francisco again) , the workflow will still be triggered. Iterable will not verify that the new value is different from the old value before triggering.
Triggered Custom Event
A workflow can begin when a custom event has occurred. Examples of custom events could be when a user clicks a button, downloads a file, views 5 items on your website, etc. You can send custom events via the Iterable events API.
Opened/Clicked an Email
You can send a user through a workflow after they opened or clicked on a link in a specific email campaign. This can be useful if a user opens/ clicks a promo email about an upcoming product, which indicates their interest in learning more. You can then send them through a workflow with more details about the product.
Received an SMS
This allows you to trigger a workflow in the event that a subscriber responds to an SMS (for example, if you want to follow up with that user in some way).
Filters in Workflow Triggers
You can apply filters in the first trigger node. If you are including data fields in the API for the trigger event, then you can use the filter to query on these fields. For example, here is a workflow is triggered off a purchase event.
Double click the node and check "Filter on data fields". Directly in the trigger node, we've added a filter to include only 'Purchase' events where the grandTotal field is greater than 50.
Here's another example of a filter applied to a custom event called "Viewed foobar Page" that is triggering the workflow.
The filter on the trigger node is looking for users with the "viewed foobar Page" event with an event field called "name" that is equal to "foobar".
For a complete overview of Iterable workflows, click here.