> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user/automations-builder/trigger-workflow-via-inbound-workflow-or-send-whatsapp-messages-via-inbound-webhook-trigger.md).

# Trigger Workflow Via Inbound Workflow Or Send WhatsApp Messages Via Inbound Webhook Trigger

1. Go to **Automation Builder → Workflow**
2. Click **Create Workflow**
3. Give your workflow a name
4. Click **+ → Webhook → Custom Webhook**
5. Add a title and click **Generate Hook**
6. Copy the **Webhook URL**
7. Click **Capture Incoming Webhook**
8. Send sample data (e.g., Name, Phone Number)
9. Confirm data is received

#### Send WhatsApp Message Using Webhook Data

10. Add **CRM → Send Template Message**
11. Select Channel & Template
12. Map:

* Number → Phone from webhook
* Name → Webhook name variable

13. Click **Run & Save**
14. Save & **Enable** the workflow

Now, whenever data is sent to the webhook URL, the automation will trigger and send the WhatsApp message automatically.

{% embed url="<https://www.youtube.com/watch?v=LZbhWB4zhbA>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpdocumentation.gitbook.io/user/automations-builder/trigger-workflow-via-inbound-workflow-or-send-whatsapp-messages-via-inbound-webhook-trigger.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.