Trigger node

Who should read this article: Administrators

The Trigger node is the first node of every Automation. It sets the event that starts the Automation and the traffic it covers.

Introduction

Every Automation has exactly one Trigger node. It is added automatically when you create an Automation.

The event you select in the Trigger node decides which variables you can use in the rest of the Automation, in the Conditions node and in the SMS message text.

Connections

The Trigger node has no input connection and one output connection, Next step.

Configuring the Trigger node

Click the Trigger node to open its settings.

Event

Select the event that starts the Automation:

Campaigns (Dialer call ended)

Select one or more campaigns. The Automation runs only for calls from these campaigns.

• Only campaigns that can still make calls are listed, with their status next to the name. Completed, Stopped, and Error campaigns will not make more calls, so they are not shown.
• Select all selects the campaigns that exist today. It does not add campaigns you create later.

Auto-include all newly created campaigns (Dialer call ended)

Select this option to make the Automation also cover every campaign you create after you save it. It works together with the campaigns you selected above, whether you selected specific campaigns or Select all.

If this option is not selected and all your selected campaigns become Completed, Stopped, or Error, the Automation can no longer run. A red error icon appears next to it in the Workflows list, and the Trigger node shows a notice. Click Remove them in the notice to remove the campaigns that have ended, then select a campaign that can still make calls.

Channels (Conversation ended)

Select one or more channel types: Webchat, WhatsApp, Telegram, Facebook, Instagram, or Viber. The Automation runs for conversations on all your channels of the selected types.

Variables

Use these variables in Conditions rules and in SMS message text. In message text, a variable is written in double curly brackets, for example {{campaign.name}}.

Dialer call ended

Your lead fields (Dialer call ended)

On top of the variables above, the Dialer call ended trigger gives you the data from your own leads: a first name, a plan, a promo code, a customer tier, or any other column you send. Every field you map from your dialer leads on the Interaction context mapping page becomes a variable. On each call, it takes its value from the lead that was called.

Use lead fields like any other variable:

• In the SMS text, to personalise the message: Hi {{context_first_name}}, sorry we missed you. Your {{context_plan}} offer is waiting: {{context_offer_link}}
• In Conditions rules, to send a message only to some leads: context_tier equals Gold.

To use a lead field in an Automation:

1. Add the field to your leads, as a column in the campaign's CSV file or as a field in the Calling List API. Refer to Part 2: Dialer campaigns.
2. Navigate to Administration > Interaction context mapping and add a mapping field. Under Metadata source, select Dialer campaign lead list and enter the field name exactly as it is in your file or API. Refer to Interaction context mapping.
3. Open your Automation. The field is now in the variable list, under its Auto-generated context key. For example, a field with the label First name becomes context_first_name.

The variable is available whatever you select under Show in on the mapping page.

Conversation ended

Related articles

• Automations overview
• Creating an Automation
• Interaction context mapping
• Variable management