> 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/how-to-create-drip-campaigns.md).

# How To Create Drip Campaigns ?

1. Go to the CRM and create a custom field named **"lead stage."**
2. In the **Automations Builder**, create a workflow triggered by the update of the **"lead stage"** custom field.
3. Capture the incoming webhook data by updating the **"lead stage"** custom field in the CRM.
4. Add a basic router to create different branches for **hot and cold leads** based on the updated value of the **"lead stage"** custom field.
5. Send **WhatsApp template messages** with personalized variables and buttons for each branch.
6. Add **delays** between messages to create a drip campaign.
7. **Save and enable** the workflow to start the drip campaign.
8. You can create multiple drip campaign automation flows for different custom fields or triggers in the CRM.

{% embed url="<https://youtu.be/iAjPqzZVDK8>" %}


---

# 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/how-to-create-drip-campaigns.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.