--- title: "Trigger node" slug: "automations-trigger-node" updated: 2026-10-19T11:15:22Z published: 2026-10-19T11:15:22Z canonical: "docs.voiso.com/automations-trigger-node" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.voiso.com/llms.txt > Use this file to discover all available pages before exploring further. # 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. Use your own lead data With the **Dialer call ended** trigger, every field you map from your dialer leads on the [Interaction context mapping](/docs/interaction-context-mapping) page becomes a variable too. Send *"Hi {{context_first_name}}, here is your code: {{context_promo_code}}"*, or send a message only to `Gold` customers. Refer to [Your lead fields](/docs/automations-trigger-node#your-lead-fields-dialer-call-ended). ### 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: | Event | When it fires | | --- | --- | | **Dialer call ended** | A call from a dialer campaign ends. | | **Conversation ended** | A digital conversation ends. | ### 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. Note Only WhatsApp conversations include the customer's phone number. For the other channel types, a Send message node can only send to a number you type in **To**. Refer to [Creating an Automation](/docs/creating-an-automation). ## 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 | Variable | Description | Example | | --- | --- | --- | | `uuid` | The ID of the call. | `07771c38-c159-4965-a878-be0162118b2b` | | `started_at` | When the call started. | `2026-08-21T14:32:05Z` | | `ended_at` | When the call ended. | `2026-08-21T14:35:40Z` | | `call_date` | The date of the call, in your contact center's time zone. | `Monday, 21 August 2026` | | `call_time` | The time of the call, in your contact center's time zone. | `14:32` | | `timezone` | Your contact center's time zone. | `Europe/Bucharest` | | `ani` | The number the call came from. | `447520641491` | | `dnis` | The number that was dialled. | `97155674300` | | `disposition` | How the call ended: `answered`, `no_answer`, `busy`, `failed`, `machine_answered`, `dialer_abandoned`. | `no_answer` | | `end_reason` | Why the call ended. | | | `wrapup_code.id`, `wrapup_code.code`, `wrapup_code.name` | The wrap-up code set on the call. | `Sale` | | `campaign.id`, `campaign.name` | The campaign the call belongs to. | `Spring promo` | | `user.id`, `user.name`, `user.email` | The agent who handled the call. | `Andrew S.` | | `redial_scheduled` | Whether the dialer will call the number again: `true` or `false`. | `false` | | `redial_scheduled_at` | When the dialer will call again. | | | `attempt` | Which attempt this call was. | `2` | | `max_attempts` | The maximum number of dial attempts set for the campaign. | `3` | | `duration_overall`, `duration_talk`, `duration_hold`, `duration_dialing` | How long each part of the call lasted, in seconds. | `95` | ### 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](/docs/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](/docs/outbound-dialer-campaign-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](/docs/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 | Variable | Description | Example | | --- | --- | --- | | `uuid` | The ID of the conversation. | | | `started_at`, `ended_at` | When the conversation started and ended. | | | `call_date`, `call_time`, `timezone` | The date and time, in your contact center's time zone. | `Monday, 21 August 2026` | | `disposition` | How the conversation ended. | | | `source` | Where the conversation came from. | | | `cost` | What the conversation cost. | | | `wrapup_code.id`, `wrapup_code.code`, `wrapup_code.name` | The wrap-up code set on the conversation. | | | `queue.id`, `queue.name` | The queue the conversation went through. | | | `channel` | The channel type: `whatsapp`, `chat` (Webchat), `telegram`, `viber`, `facebook`, `instagram`. | `whatsapp` | | `channel_profile.id`, `.identifier`, `.name` | Your Voiso channel that the conversation came in on. | | | `contact_channel_account.id`, `.identifier`, `.name` | The customer's account on that channel. | | | `user.id`, `user.name`, `user.email` | The agent who handled the conversation. | | | `sla_first_response`, `sla_avg_reply`, `sla_resolution` | Time to first response, average time to reply, and time to resolution. | | | `duration_overall`, `duration_talk`, `duration_queue` | How long each part lasted, in seconds. | | ## Related articles - [Automations overview](/docs/automations-overview) - [Creating an Automation](/docs/creating-an-automation) - [Interaction context mapping](/docs/interaction-context-mapping) - [Variable management](/docs/flow-builder-variable-management)