Triggers vs. Nodes
Triggers are different from regular Nodes in a few ways:- You can’t transition from a regular Node to a Trigger. Any Triggers in your Workflow will only execute when the event they listen for occurs.
- Unlike other Nodes, you can’t add or remove Cards from a Trigger. Each Trigger is built around a single Card that determines when it executes.
Add a Trigger
To add a Trigger, just right-click anywhere in a Workflow:Test a Trigger
Triggers won’t work in the Studio’s emulator, even when the event they’re expecting occurs. Instead, you can use a previous event to test your Trigger. For example, to test the Conversation Started Trigger:1
Add the Trigger to your Workflow
Right-click anywhere in your Workflow. Select Trigger, then Conversation Started:
2
Configure a test
Select Test in the bottom-left corner of the Trigger:Then, select Show last received events. This will display a list of past events that would set off your Trigger:For the Conversation Started Trigger, each of these is a
conversationStarted event, which fires every time a user starts a new conversation with your bot.You can use any one of these events as a dummy event to test your Trigger. Just pick one and select Add as Test. Then, select Save.If there are no events available to choose, make sure your bot is published and that the event your Trigger is listening for has occurred at least once before.
3
Test the Trigger
Now, you should see the name of the event in the Trigger:Just press the play icon to fire the Trigger. Any logic you have connected to the Trigger will execute in the emulator: