> For the complete documentation index, see [llms.txt](https://docs.ownchat.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ownchat.app/bot/utility/trigger-action.md).

# 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

{% embed url="<https://app.supademo.com/demo/cmmuad0zr20dwf3u9rtcyvl1r?utm_source=link>" %}

### Overview &#x20;

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 &#x20;

Send Buttons\
&#x20;  ↓\
Customer clicks button\
&#x20;  ↓\
Trigger Action\
&#x20;  ↓\
Start Action / Welcome Action

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

### 1. Open Bot Actions &#x20;

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 &#x20;

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.<br>

{% embed url="<https://app.supademo.com/demo/cmpao48x505mrz80jkqotgff0?utm_source=link>" %}

### 3. Copy Action ID &#x20;

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**.<br>

{% embed url="<https://app.supademo.com/demo/cmpao58cm06p7xa0j64pw336o?utm_source=link>" %}

### 4. Add New Node &#x20;

After copying the Action ID:

1. Click:

Add Node

This opens the action selection panel.<br>

{% embed url="<https://app.supademo.com/demo/cmpao6c3b06lfz70j2mtopm68?utm_source=link>" %}

### 5. Open Utilities Tab &#x20;

From the action tabs:

* Send
* Ask
* Utilities
* Connections

Click:

Utilities

This section contains utility actions.<br>

{% embed url="<https://app.supademo.com/demo/cmpaobfti06p9xa0j5mmuezbe?utm_source=link>" %}

### 6. Select Trigger Action &#x20;

Click:

Trigger Action

This opens the **Trigger Action configuration panel**.<br>

{% embed url="<https://app.supademo.com/demo/cmpaocqu505myz80jiaa4xx5k?utm_source=link>" %}

### 7. Configure Action Name &#x20;

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.<br>

{% embed url="<https://app.supademo.com/demo/cmpaodn7606pbxa0j4h8qzevg?utm_source=link>" %}

### 8. Enter Target Action ID &#x20;

In **Target Action ID,** paste the copied Action ID.

Example:

68bde8e2019ae1a737891252

This is the action that will be triggered next.<br>

{% embed url="<https://app.supademo.com/demo/cmpaoem6r05n0z80j5iulo492?utm_source=link>" %}

### 9. Add Variables (Optional) &#x20;

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 &#x20;

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 &#x20;

Click:

Create

This saves the Trigger Action configuration.<br>

{% embed url="<https://app.supademo.com/demo/cmpaogenk06lkz70jzp1qgja0?utm_source=link>" %}

### 12. Connect the Flow &#x20;

Connect the previous action node to the Trigger Action node.

Example:

Send Buttons\
&#x20;  ↓\
Trigger Action

This ensures the workflow executes in sequence.

### 13. How It Works &#x20;

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<br>

{% embed url="<https://app.supademo.com/demo/cmpaojkcl06pixa0jeliqt5lf?utm_source=link>" %}

### 14. Example Workflow &#x20;

Welcome Message\
&#x20;  ↓\
Send Buttons\
&#x20;  ↓\
Customer Click\
&#x20;  ↓\
Trigger Action\
&#x20;  ↓\
Welcome Action

### 15. Example Real-Time Use Case &#x20;

#### Scenario: Order Status &#x20;

Customer clicks "Track Order"

↓

Trigger Action

↓

Order Status Action

Message example:

Your order is ready for pickup.

### 16. Publish Changes &#x20;

After configuration, click:

Publish

This saves and activates your bot configuration.

Without publishing, changes will not go live.<br>

{% embed url="<https://app.supademo.com/demo/cmpaoox1j06pkxa0jd4q7it7s?utm_source=link>" %}

### Final Workflow Summary &#x20;

Send Buttons\
&#x20;  ↓\
Trigger Action\
&#x20;  ↓\
Target Action\
&#x20;  ↓\
Fallback Action (if failed)

### Best Practices &#x20;

#### Use Descriptive Action Names &#x20;

Good:

order status trigger

Bad:

action 1

#### Always Copy Correct Action ID &#x20;

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

Incorrect Action IDs may break the workflow.

#### Configure Fallback Action &#x20;

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

Example:

Error message action

#### Publish After Changes &#x20;

Always publish after:

* editing actions
* updating IDs
* changing fallback routing

### Common Use Cases &#x20;

#### Welcome Flow &#x20;

Welcome → Trigger Action → Greeting Action

***

#### Order Tracking &#x20;

Track Order → Trigger Action → Status Action

***

#### Feedback Flow &#x20;

Delivered → Trigger Action → Feedback Action

***

#### Escalation Flow &#x20;

Issue Reported → Trigger Action → Agent Transfer

***

### Expected Output &#x20;

After successful configuration:

* Action ID is triggered automatically
* Workflow continues seamlessly
* Fallback action handles failures
* Flow becomes modular and reusable

&#x20;