Workflow Actions

There are a number of actions that can be performed against a user in a workflow. To apply an action, drag the type of node that you want from the left tray to the desired position in the workflow. Then, link it to any nodes that you want to precede or follow. Actions are represented by light grey nodes once dropped into the workflow.

This document describes the various types of workflow actions available in Iterable.

# Table of contents

# Send email, in-app, push, SMS, or web push

Workflows can send email, in-app message, push notification, SMS, and web push campaigns. To do this, use the Send Email, Send In-App, Send Push, Send SMS, and Send Web Push workflow nodes:

Send nodes allow you to select a base template and configure a campaign directly within the workflow. For an overview of this process, see Creating a basic workflow.

Once a campaign has started, the Campaign Analytics tab inside the send node shows metrics about the campaign's performance. For more details, take a look at Workflow Analytics.

# Add user to list

Use this action to add a user to an existing static list. For example, you may have a welcome series workflow. At the end of the workflow, you'd like to add all users who have completed the workflow to a list called Finished Welcome Series or Regular Users, rather than new users.

# Remove user from list

You can remove users from an existing static list in a workflow. This would be a good step to add at the end of a welcome series workflow, which you would remove people from the New Users Welcome list.

# Change contact field

You can use workflows to add or update a contact property on a user's profile. The field change will need to be written in JSON like so:

If triggering the workflow from an event, you can set a contact property to equal a value being passed through by that event. To do so, you would put the event field name merge parameter in quotes like below. Note that any merge parameters you reference will check only the fields in the event payload, not the fields on the user's profile. You may use Handlebars helpers and you may set numeric fields, as long as the value being returned can be coerced into a number.

Another JSON example:

{"TotalPurchaseValue":"{{numberFormat (math HighestPurchaseValue '-' lastPurchaseValue) 'integer'}}"}

Use this action if you would like Iterable to make an HTTP GET request to another system with an email parameter and update the user's Iterable profile with the requested info. Read Using Webhooks for more information.

# Update user profile webhook

Use this action if you would like Iterable to make an HTTP GET request to another system, passing a user's email address as a URL parameter, and update the user's Iterable profile with the requested info.

For more information, read Using Webhooks.

# Modify channel subscription

A workflow can allow you to either subscribe or unsubscribe a user from a specific message channel. Read Message Channels and Message Types Overview for more information.

# Modify message type subscription

A workflow can allow you to either subscribe or unsubscribe a user from a specific message type. This is useful if you have an email preferences center. Read Message Channels and Message Types Overview for more information.

# Call webhook

Use this action if you would like to Iterable to make a HTTP request to another service to trigger an action outside of Iterable. Read Using Webhooks for more information.

# Delay

Delays allow you to add time delays before the next step happens. For example, you can add a delay of 72 hours before a user receives the next email.

You can add a standard delay. The example below is a three-day delay:

You can also add a delay using the time from a property. You'd pass in a contact property or custom event field with a specific time in the format YYYY-MM-DD 00:00:00 +00:00. This can be useful if you store a user's membership expiration date as a contact field and would like to notify the user 15 days prior to the expiration date to renew their membership.

You can also choose to skip specific days of the week. The selected days will be skipped and the email will be sent on the next allowed day. Another option would be to delay until a specific time. You can choose to delay further until a specific time based on the project time zone or the recipient's local time zone.

In the example below, we are adding a delay that is waiting until 15 days before the time stored in stateIdExpiration, skipping the weekend and also waiting until 6:00 PM.

# Editing a delay node

When you update a delay node, the new amount of delay will be applied to the new users only. The users that are already delayed will still carry the original amount of delay.

# Trigger workflow

This action will allow you to trigger another workflow, which must be set to be triggered by a workflow.

# Add user to Facebook Custom Audience

This action will allow you to add the user to a Facebook Custom Audience that you have already set up. You will need to select a Facebook Ads Account ID and Facebook Custom Audience name.

# Remove user from Facebook Custom Audience

This action will allow you to remove the user from a Facebook Custom Audience that you have already set up. You will need to select a Facebook Ads Account ID and Facebook Custom Audience name.

For a complete overview of Iterable workflows, read the Workflow Overview document.