Triggers can help you automate certain processes in the chatbot. For example, when a user has opted-in for email you might want to sync this data with a CRM or Google Sheet.
To get to the trigger section you need to go to the left-hand menu and select Automation then choose Triggers. From here you will be able to create a new trigger by pressing the blue button on the top right named + New trigger.
Once pressed you will get to see the available triggers you can choose from;
How to create a new trigger
Let’s take an example of a trigger when someone pays for order inside your chatbot. Press the blue button + New trigger then select the trigger named as such: Order Paid
From here a new pop-up window will open where you can set up the details of your trigger.
You will be able to enable or disable the trigger, set up a condition if you need the bot user to match a certain filter before the trigger is activated, and you can add a note that will explain more about this trigger.
Great if you are working with a team or creating a template and need to clarify things.
Once done press the bottom right button named Save and you are now halfway done setting up your trigger.
Selecting your Sub Flow
Now that the trigger has been created we will be needing to add an action to it. You can do this by pressing the Choose Sub Flow space to the right of that trigger.
Once done it will open up a pop-up window for you where you can select your desired flow to be connected once this trigger has been activated.
You can also type to find your flow more easily if you prefer. Once you found your flow just select it and it will return you to the Trigger overview.
From here you have a few options when it comes to managing the triggers.
Managing your Triggers
You have two options if you want to manage your triggers:
You can enable or disable them by pressing the slider on the left of the actual trigger
You can edit the trigger settings. Inside of here you also have the option to delete the trigger entirely
Glossary
Trigger Type | Description | Notes |
This Trigger is used when a new bot user enters the bot. | This will not work when a user is created manually. | |
This trigger happens when a Bot_User has subscribed to the bot. | ||
This trigger happens when a Bot_User has unsubscribed to the bot. | ||
This trigger happens when a Bot_User has Opted-in for Email either manually or by flow | ||
This trigger happens when a Bot_User has Opted-out for Email either manually or by flow | ||
This trigger happens when a Bot_User has Opted-in for SMS either manually or by flow | ||
This trigger happens when a Bot_User has Opted-out for SMS either manually or by flow | ||
This trigger happens when a Bot_User conversation is moved to the Open folder in livechat | ||
This trigger happens when a Bot_user conversation is moved to the Pending folder in livechat | ||
This trigger conversation is moved to the Done folder in livechat | ||
This trigger conversation is moved to the Invalid folder in livechat | ||
This triggers when Bot_user is assigned to the Agent either manually or by flow | ||
This triggers when a certain specified userfield value is changed for a bot user | ||
This triggers when Tag added to Bot_user | ||
This triggers when Tag applied to Bot_user is removed. | ||
This triggers when Bot_user is subscribed to sequence. | ||
This triggers a sub-flow, when Bot_user is unsubscribed from sequence. | ||
This trigger is used when you want to trigger a subflow based on time after or before an event has to occur. | You can only use dateTime CUFs in this trigger. | |
This triggers when Bot_user has paid for the Order | ||
This triggers a sub-flow, when status of an order is changed to Ordered | ||
This triggers a sub-flow, when status of an order is changed to Processing | ||
This triggers a sub-flow, when status of an order is changed to Shipped | ||
This triggers a sub-flow, when status of an order is changed to Completed | ||
This triggers a sub-flow, when status of an order is changed to Cancelled | ||
This triggers a sub-flow, when status of an order is changed to Refunded | ||
This triggers a sub-flow, when an order is places using whatsapp catalogue | ||
This triggers when a product enquiry is asked using whatsapp catalogue | ||
This triggers when a bot user is created via whatsapp ad referral | ||
This triggers when a bot user is created via facebook ad referral | ||
This triggers when a lead is generated through Facebook Ads referral | ||
This triggers when Bot_user payment is success when using native Stripe payment gateway | ||
This triggers when Bot_user payment has failed when using native Stripe payment gateway | ||
This triggers a subflow, when the bot receives a inbound webhook from CRM V2. You can specify the webhook within the trigger | Only works if GHL/CRM is connected. | |
This triggers a subflow, when the bot receives a native trigger from Shopify | You can specify the event such as order creation, abandoned cart etc | |
This triggers a subflow, when the bot receives a native trigger from Woocommerce | You can specify the event such as order creation, abandoned cart etc | |
This triggers a subflow, when the Guest Bot_user ends his conversation. | This is helpful for webchat channel for deleting guest users | |
This triggers a subflow, when a Bot_user books a Calendly Appointment | ||
This triggers a subflow, when a Bot_user reshedules a Calendly Appointment | ||
This triggers a subflow, when a Bot_user Cancels a Calendly Appointment | ||
This triggers a subflow when someone mentions the user in a story on Instagram | ||
This triggers a subflow when someone replies to user’s story | ||
This triggers a subflow, when someone shares the post of the user |
Add Comment