Triggers Builder
Last updated
Was this helpful?
18.5
Last updated
Was this helpful?
The Triggers Builder provides the tools to define and manage how Sessions begin. Sessions are started by external Triggers, which fall into three categories: User Interactions, App APIs, and Subscriptions.
Like most Builders, the layout of the Triggers Builder maps comfortably onto the general structure of the Studio: to the immediate right of the Builder Bar is the Tree, to the right of which is the Stage, to the right of which is the Inspector, when applicable. Depending on the element being examined, there might not always be an imagine on display in the Stage:
Sessions can be triggered by direct user interactions: users can begin a Session by texting a particular phone number, calling a particular phone number, or clicking on a Starting Link.
To add a new User Interactions Trigger, click on the '+' icon to the right of the User Interactions section of the Tree and select the relevant Trigger type:
The Receive an SMS Trigger begins a Journey when a new user sends a text message to a particular number.
The Receive a Call Trigger begins a Session when a new user calls a particular phone number.
New base URLs can be created in the Tree, by clicking on the '+' icon to the right of App APIs. New endpoints can be added to a base URL by clicking on the '+' icon to the right of the relevant base URL:
Within the Triggers Builder, Subscriptions connected to an application by clicking on the '+' icon to the right of Subscriptions in the Tree. From there, the interface that appears in the Stage can be used to view and modify the data source and the category of web hook. It can also be used to access the details of Journey Mapping.
The provides the means to connect your phone numbers to your . Once connected to an Org, phone numbers will become available in the when accessing your application in the Studio. Under the Chat Bot section, you can select an available number to receive, send, and manage texts associated with your application.
For more on how to associate your phone numbers with Airkit apps, see .
For more on Actors, see . For a more detailed dive into how incoming texts are processed – both when they trigger the start of a Journey and when they don't – see .
Invoking the Receive an SMS Trigger is an capable of triggering an Action Chain. This Action Chain is constructed in the Inspector. Clicking on the '+' icon to the upper right lets you select an Action to add to the Action Chain:
Most commonly, this Action Chain issued to call upon the Action or Action. This makes it possible to designate an outgoing SMS message to reply to the incoming SMS message that triggered the start of the Journey.
(For more context on initializing Actors, see and .)
The Invoke Event described here is technically distinct from the application's , which comes out of the box tied to the necessary Actions to initialize the Actor. The Action Chain associated with the Starting Event are run immediately before Action Chain associated with this Invoke Event, meaning the Actor would be initialized shortly before sending the outgoing SMS notification.
The provides the means to connect your phone numbers to your . Once connected to an Org, phone numbers will become available in the when accessing your application in the Studio. Under the Voice Bot section, you can select an available number to receive, send, and manage associated calls.
For more on how to associate your phone numbers with Airkit apps, see .
For more on Actors, see . For a more detailed dive into how incoming calls are processed – both when they trigger the start of a Journey and when they don't – see .
Invoking the Receive a Call Trigger is an capable of triggering an Action Chain. This Action Chain is constructed in the Inspector. Clicking on the '+' icon to the upper right lets you select an Action to add to the Action Chain:
Most commonly, this Action Chain issued to call upon the Action. This makes it possible to reply to the incoming call that triggered the start of the Journey.
(For more context on initializing Actors, see and .)
The Invoke Event described here is technically distinct from the application's , which comes out of the box tied to the necessary Actions to initialize the Actor. The Action Chain associated with the Starting Event are run immediately before Action Chain associated with this Invoke Event, meaning the Actor would be initialized shortly before starting activating a Voice Bot.
The Visit a Link Trigger begins a Session when a user navigates to a Starting Link. Inspecting this Trigger allows you to select the that will begin the web portion of your application.
Starting Links are referred to as a "Web URLs" in , which is where they are configured.
For more on how to conceptualize Starting Links, see . For more on how to configure a white-label domain that can be used to define a Starting Link, see .
describe custom API endpoints that tie incoming HTTP requests directly to an Airkit application.
The details of base URLs and their endpoints are defined in the Stage. For more on how to create custom base URLs and endpoints, see .
Subscriptions allow Airkit apps can to receive (and subsequently respond to) data updates from out-of-the-box integrations with Zendesk and Salesforce. For more on how this is done, see .
