Starts of Automation 360 Flow

SendPulse users can set up Automation360 flows with the following start conditions:

Flow start events require at least one of these two variables: email or phone.

Starting a flow with the "Add subscriber" event

To start a flow with the event "Add subscriber," first, specify a mailing list that will be tracked for the event.

Additionally, users can turn on the option that starts the flow when the mailing list is updated with a contact who is already on it.

Generally, mailing lists are updated from one of the following sources: integrations with third-party resources, in the SendPulse user panel, via REST API, signup forms, manual updates of mailing lists, transfer of a mailing list segment from one list to another, or changes caused by the "Action" block of Automation360.

Also, you can re-launch an autoflow to the entire mailing list. This feature allows you to launch a flow for contacts you added to a list before creating the autoflow or during a pause (start "Add to mailing list" tracks only those contacts that were added to the book after starting autoflow. Feature “Launch on mailing list” allows sending to those, who were added before.)

Please note that if you enable the "Start when a subscriber is added to the list multiple times” option as a start condition of the flow, contacts who have already received the flow will be moved to the flow start again.

To start the autoflow for your mailing list, open the flow and click "Launch for mailing list."

You can run an autoflow for a mailing list once every 5 minutes. You can run multiple autoflows for the same mailing. When uploading addresses to the send queue, you can upload addresses to the mailing lists, the two processes do not interfere with each other.

Starting a flow with the "Special date" event

Start your flow with the "Special date" event, when you need to start the sequence after the "Date" variable on your mailing list gets a specific value.

Special date events are usually used to send clients messages on important dates or to inform customers about the upcoming expiration of their subscription. Naturally, the mailing list must contain that variable.

Starting a flow with the "Contact webhook" event

Starting your flow with the "Contact webhook" event tracks actions of subscribers, who have somehow reacted to an email: opened it or clicked a link in the message.

Starting a flow with the "Change variable" event

Start your flow with the "Change variable" event, when the value of a specific variable on the mailing list changes. To choose this type specify a mailing list that will be monitored for updates.

This event also offers an option to set a specific value for the variable to trigger the flow starts when the variable receives it.

Starting a flow with a custom event

An event is a condition set up by the user, a sort of a webhook you on your end integrate and send to SendPulse to trigger the flow to start. Select a previously created event that will trigger your auto-flow.

This start type has an option to use variables from your mailing list — for instance, if clients' names are on the list, but custom event can't transfer these details to SendPulse. So, if the user can transfer corresponding clients' phone number, email address, other details, like name, will be taken from the mailing list automatically.

To use variables from your mailing list in auto-flow, turn the toggle switch to ON and select a mailing list.

Starting a flow with a "Create deal" event

You can start your flow with a "Create deal" event. To do this, choose deal stage, deal type and source.

Starting a flow with a "Change deal stage" event

With the "Change deal stage" event, a flow starts when a deal stage changes, for example, from "In progress" to "Successfully closed." You can also start your flow by changing the deal type and source.

Last Updated: 12.09.2022