Skip to main content

Event-triggered Workflow campaign

1. Introduction

Event-Triggered workflows enable you to trigger personalized campaigns based on user actions. These workflow campaigns enable reaching out to your users on multiple channels at the right time, in the right context.

Use cases

The following are some examples of where you can use Event-Triggered workflows:

  • Reducing cart abandonment - Send reminders to complete the purchase to users who have added items to their cart and didn't proceed with the purchase.
  • Welcome mail to new users - Welcome your new users after they have successfully signed up.
  • Driving up LTV - Engaging loyal customers at critical moments to drive sales.

2. Create an Event-Triggered workflow campaign

Step 1: Add an event:

To create a custom user event, follow these steps:

  1. In Automation, go to the Event tab and click Custom events > +Add event.
  2. In Event name, name the event.
  3. In Event description, enter a brief description about the event.
  1. Click Create event.

  2. Push the custom event data of a user using the Push user event API. It needs the userId of the registered user. Events help you track user actions or trigger a Journey or Campaign for that user.

    If the userId does not exist on yellow.ai's User360 module, you need to call the User create API and then push the event data.

    You can use a phone number or email address as a UserID and needs to be unique. For more details, see userId.

Step 2: Create Workflow

Workflow campaign is like a flow which you can trigger from the Engage Module.

To create a Workflow campaign, follow these steps -

  1. Create a new flow to use in your Workflow campaign.

    From Automation > Create flow. [OR]

    From Automation > Flows > Create flow.

  2. Set to trigger the flow when the event occurs.

  3. To the Start node add a new Action node, Outbound notification. There is no need to configure the start node for workflows.

    .

  1. Map To to a CDP attribute of the notification type (for example, phone for WhatsApp, email for Email).
  2. Use various Action nodes in between flows to fetch notification status; use the Delay node to add timeout.

  1. Map Template params properly with CDP Attribute or Bot variable so that the Template can be sent to the user.
note
  • There should be at least 1-2 minutes delay between an Outbound Node and Notification Status Node.
  • It is recommended to have at least 2-3 channels configured in a bot for Workflow Campaigns to have better fallbacks.
  • Currently, not all the Action Nodes are supported in a Workflow. Basic functionalities such as Outbound Nodes, Delay Nodes, and DB Updates are compatible with Workflow Campaign.

Step 3: Schedule an event-triggered workflow

  1. Once the flow configuration is completed, go to the Engage module > Journeys.

  2. Click Create campaign.

  3. Enter a Journey trigger name.

  4. Select a flow with the Outbound node that you want to associate with the campaign from the list of workflow journeys.

  5. Click Next.

  6. Select your preferred target audience (segment). Make sure to add your users' CDP records to use for any type of campaign. Know more about User 360.

  7. On the Schedule screen, select User event-based.

OptionDescription
Campaign triggers when userChoose the event for which the campaign should trigger.
After the event, the campaign triggersChoose when to trigger the event.
Immediately: To trigger the event as soon as the event occurs.
At a specific time: To trigger the event at your preferred time after the event occurred.
After a delay: To trigger the campaign for the user after specific hours, minutes, or seconds from the event occurred time.
Run this campaignChoose Once per user to trigger the campaign only once per user, and choose Every time the event is fired to trigger any number of times whenever the event occurs for the user.
Exclude if conversion has happenedEnable this to stop triggering the campaign when the conversation has happened, and choose the Conversation event. For example, for a Cart abandonment event, a transaction could be a Conversation event.
Start this campaignChoose when to start the campaign - Now or at a Later date and time.
End this campaignChoose when to end the campaign. Choose a future date and time.