{"id":18067,"date":"2018-11-23T18:50:40","date_gmt":"2018-11-23T18:50:40","guid":{"rendered":"https:\/\/developer.kore.ai\/v10-1\/?post_type=docs&p=15475"},"modified":"2024-02-21T07:54:28","modified_gmt":"2024-02-21T07:54:28","slug":"event-based-bot-actions","status":"publish","type":"post","link":"https:\/\/developer.kore.ai\/v10-1\/docs\/bots\/bot-intelligence\/event-based-bot-actions\/","title":{"rendered":"Event Based Bot Actions"},"content":{"rendered":"
\r\n\t
\r\n\t\t
\r\n\t\t\t

Events are triggered when specific actions occur during conversation with the Virtual Assistant\u00a0 or when specific events are triggered on any active channels.<\/span><\/p>\n

For example, when a user clicks the <\/span>Get Started<\/b> button to initiate a chat with your FB Messenger VA, it triggers the Facebook Welcome event. You can use this event to customize the welcome greeting such as personalizing it with the user\u2019s first and last names, capturing additional information from users, and updating the back-end systems.<\/span><\/p>\n

To generate the Get Started<\/b> button, please use the following Curl code:<\/p>\n

curl –location -g –request POST ‘https:\/\/graph.facebook.com\/v2.6\/me\/messenger_profile?access_token={{page access token}}’
\n–header ‘Content-Type: application\/json’
\n–header ‘Cookie: fr=0DjuarxRV9YWitxAN..BfXHzR…1.0.BfXHzR.’
\n–data-raw ‘{
\n“get_started”: {“payload”: “Facebook”}
\n}’
\n<\/span><\/p>\n

Note<\/b>: You must provide access_token<\/code>, the Page access token for the specific Facebook page in the curl to run the API.<\/p>\n

To access Event Handlers<\/strong>, navigate to <\/span>Build > Intelligence > Events.<\/strong>
\n<\/strong><\/p>\n

\"\"<\/a><\/p>\n

<\/div><\/div>\n

Event Actions<\/span><\/span><\/h1>\n

Developers can define the VA should take when an event is triggered using one of the following options:<\/span><\/p>\n

Run a Task<\/span><\/span><\/h2>\n

Select a Dialog task (Standard or Hidden) to be invoked when the event triggers. Once the event is triggered, the dialog starts executing. If it is interrupted because of other intent detections, the <\/span>Hold <\/span><\/em>and <\/span>Resume <\/span><\/em>settings come into play. During execution, if the selected Dialog is not published in the VA, the event is discarded.<\/span><\/p>\n

In some cases, the Dialog may not be available to the user during a conversation for various reasons such as the task\u00a0not yet being published, being suspended, or simply not having been assigned to the user. In such cases, the VA\u00a0 shows an error message that the task is not currently available for execution. Developers can preempt such situations by testing the VA in Debug mode. The Debug Console shows full details about the error, including the reason why the task is not available.<\/span><\/p>\n

Run a Script<\/span><\/span><\/h2>\n

Define a JavaScript to run when the event triggers. The script can make use of all applicable components such as session, context objects, variables, and functions. You can also fix the code using the Debug mode.<\/span><\/p>\n

Show a Message<\/span><\/span><\/h2>\n

Define a simple or advanced message to the user when the event triggers. It supports all messaging formatting features available in the XO Platform, including multiple messages with channel override options.<\/span><\/p>\n

\"\"<\/a><\/span><\/p>\n

Multilingual VA Behavior for Messages<\/span><\/span><\/h3>\n