Actions allow your chatbot to perform tasks behind the scenes when the user interacts with your chatbot, such as adding or removing tags, subscribing a user to broadcasts, scheduling notifications, storing data, running scripts, or sending custom analytics.
Actions can be added to conversations, passages, and any button-like Bot Message content type or Expected User Response, such as:
Conversation-level actions are triggered every time the flow enters that conversation, including if a conversation has been resumed, or if a passage has been configured to retain the previous conversation context. Conversation-level actions trigger before any passage-level or message-level actions.
Passage-level actions are triggered when the flow enters the passage, before the chatbot sends the first message of the passage.
Message-level actions are triggered when the user interacts with the button or quick reply with the configured action.
You can:
- Configure an action. You can add as many actions as you need.
- Remove an action.
When a Bot Message or Quick Reply has an action attached, it displays an icon to indicate the type of action that has been configured.
| Action | Description |
|---|---|
| Save data |
Store the value of the button label or a value you define to the user's context data. You can use this data elsewhere in the chatbot as a variable. See more information on the Save data configuration fields. |
| Remove data | Remove the data stored for this variable from the user's context data. |
| Subscribe to broadcasts | Subscribe the user to broadcasts. |
| Unsubscribe from broadcasts | Unsubscribe the user from broadcasts. |
| Schedule an event notification |
Schedule a notification for this user. For example, a reminder message for an appointment they have booked. The date and time the notification is sent is determined by the notification settings, relative to when it is scheduled for the user. |
| Unschedule an event notification |
Remove a scheduled event notification for this user. For example, if they have cancelled the appointment, they should not receive a reminder message. |
| Send a custom event to analytics |
Send a custom event to your integrated analytics platform. You can define the name of the event, and optionally define the value that is sent. See more information on the Send a custom event to analytics configuration fields. |
| Run script |
Select a script to be run when the user presses this button or Quick Reply. |
| Add tag |
Add a tag to the user conversation to provide metadata and direct live chat requests in your integrated livechat platform. See Tags. Tags that you have removed from your livechat platform are shown as expired. Expired tags cannot be added. See Expired tags. |
| Remove tag |
Remove a tag from the user conversation. |
| Remove all tags |
Remove all tags from the user conversation. |
Save data
Define the name and value to save.
| Field | Description |
|---|---|
| Name | The variable name used to access the data in the store. If this name is already in use, the existing value will be overwritten. |
| Override Value | By default, this action stores the button label as the value. Select this setting to define the value to store. |
| Value | The value you want to store. |
Send a custom event for analytics
Define the name and value to send.
| Field | Description |
|---|---|
| Name | The name of the event you want to send. |
| Override Value | By default, this action sends the button label as the value. Select this setting to define the value to store. |
| Value | The value you want to send. |
Comments
Article is closed for comments.