> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/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-documentation/automations-builder/how-to-trigger-missed-call-webhook-in-automations-builder.md).

# How To Trigger Missed Call Webhook In Automations Builder ?

You can create an automation flow based on missed calls received on your virtual number.

To do this, select your number, click on the "Automations" builder, create a new flow, and enter a title for the flow.

Before saving the flow, click on "Capture Incoming Webhook" so you can receive sample data.

You can then set the destination mobile number and the person who is calling you.

Click on "Save" and then, in the next step, you can trigger a WhatsApp message by using the CRM functionality and sending the message.

You can create various flows, like sending the data to Google Sheets from the incoming webhook data.

{% embed url="<https://youtu.be/c4PqKUdzABc?si=MWitfNCwFfkiQP5W>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpdocumentation.gitbook.io/user-documentation/automations-builder/how-to-trigger-missed-call-webhook-in-automations-builder.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.