Trigger Action

The Trigger Action utility is used to automatically trigger a specific bot action using an Action ID. This helps automate response flows by jumping directly to a predefined action after a user interaction.

This is especially useful for:

• Redirecting to a specific action

• Reusing existing bot actions

• Automating next-step responses

• Creating fallback routing

• Building modular chatbot workflows

Overview

Trigger Action allows you to:

• Trigger another bot action using Target Action ID

• Define a Fallback Action ID

• Reuse existing action blocks

• Create advanced workflow automation

• Improve flow control

Use Case Example

Send Buttons ↓ Customer clicks button ↓ Trigger Action ↓ Start Action / Welcome Action

Example: When the customer clicks Track Order, the bot automatically triggers the Order Status action.

1. Open Bot Actions

1. Navigate to Bot Actions

2. Open the required bot flow

3. Select the current working path

Example:

Welcome message

2. Open Existing Action Menu

Locate the existing action node that you want to trigger later.

Example:

Send Buttons

Click the dropdown menu / options icon on the action card.

This opens the action management menu.

3. Copy Action ID

From the dropdown options, click:

Copy Action ID

This copies the selected action’s unique identifier.

This Action ID will be used as the Target Action ID.

4. Add New Node

After copying the Action ID:

1. Click:

Add Node

This opens the action selection panel.

5. Open Utilities Tab

From the action tabs:

• Send

• Ask

• Utilities

• Connections

Click:

Utilities

This section contains utility actions.

6. Select Trigger Action

Click:

Trigger Action

This opens the Trigger Action configuration panel.

7. Configure Action Name

In Action Name, enter a descriptive name.

Example:

welcome

Recommended naming examples:

• welcome

• order status trigger

• feedback trigger

• payment success trigger

Use meaningful names for easy flow identification.

8. Enter Target Action ID

In Target Action ID, paste the copied Action ID.

Example:

68bde8e2019ae1a737891252

This is the action that will be triggered next.

9. Add Variables (Optional)

If required, click:

Add variable

This can be used to pass dynamic variables into the triggered action.

Example use cases:

• customer name

• order id

• ticket number

• product name

This step is optional.

10. Configure Fallback Action ID

In Fallback Action ID, enter another action ID.

Example:

68bde8e2019ae1a737891252

This action is triggered if the target action fails.

This ensures workflow continuity.

11. Save Trigger Action

Click:

Create

This saves the Trigger Action configuration.

12. Connect the Flow

Connect the previous action node to the Trigger Action node.

Example:

Send Buttons ↓ Trigger Action

This ensures the workflow executes in sequence.

13. How It Works

Once the customer clicks the Send Button:

• Trigger Action runs

• Target Action ID is executed

• Configured action is triggered automatically

• Fallback action runs if needed

14. Example Workflow

Welcome Message ↓ Send Buttons ↓ Customer Click ↓ Trigger Action ↓ Welcome Action

15. Example Real-Time Use Case

Scenario: Order Status

Customer clicks "Track Order"

↓

Trigger Action

↓

Order Status Action

Message example:

Your order is ready for pickup.

16. Publish Changes

After configuration, click:

Publish

This saves and activates your bot configuration.

Without publishing, changes will not go live.

Final Workflow Summary

Send Buttons ↓ Trigger Action ↓ Target Action ↓ Fallback Action (if failed)

Best Practices

Use Descriptive Action Names

Good:

order status trigger

Bad:

action 1

Always Copy Correct Action ID

Always copy the exact action ID from the existing action node.

Incorrect Action IDs may break the workflow.

Configure Fallback Action

Always configure a fallback action to avoid dead-end flows.

Example:

Error message action

Publish After Changes

Always publish after:

• editing actions

• updating IDs

• changing fallback routing

Common Use Cases

Welcome Flow

Welcome → Trigger Action → Greeting Action

---

Order Tracking

Track Order → Trigger Action → Status Action

---

Feedback Flow

Delivered → Trigger Action → Feedback Action

---

Escalation Flow

Issue Reported → Trigger Action → Agent Transfer

---

Expected Output

After successful configuration:

• Action ID is triggered automatically

• Workflow continues seamlessly

• Fallback action handles failures

• Flow becomes modular and reusable