> 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/create-a-drip-campaign.md).

# Create a Drip Campaign

1. **Create a Super Field**
   * Go to **CRM → Super Fields**.
   * Create a Super Field such as **Lead Stage** with values like **Cold** and **Hot**.
2. **Create a CRM Trigger**
   * Go to **Automation Builder** and create a new workflow.
   * Click **+ → CRM**.
   * Select **Trigger on Specific Custom Field Update**.
   * Select the **Lead Stage** Super Field and generate the webhook.
   * Copy the generated webhook URL.
3. **Configure the CRM Trigger**
   * Go to **CRM → Triggers → Add New Trigger**.
   * Enter a trigger name and paste the webhook URL.
   * Select **Edited** and choose the **Lead Stage** field.
   * Save the trigger.
4. **Capture the Webhook**
   * Return to **Automation Builder**.
   * Add **Capture Incoming Webhook**.
   * Update the Lead Stage of a contact from **Hot to Cold** (or vice versa) to test the trigger.
   * Capture and save the webhook response.
5. **Create Lead-Based Routes**
   * Add a **Basic Router**.
   * Create separate filters for **Cold Leads** and **Hot Leads**.
   * Set the condition based on the **Lead Stage** value.
6. **Add WhatsApp Messages**
   * Under each route, add a **WhatsApp message**.
   * Select the channel and template.
   * Map the WhatsApp number and template variables from the contact profile.
   * Save the message.
7. **Add Delays**
   * Add a **Time Delay** between messages if required.
   * Configure the required delay, such as **24 hours**, and continue adding messages.
8. **Activate the Workflow**
   * Save and enable the workflow.
   * When the Lead Stage changes, the corresponding drip campaign will automatically be triggered.

**Note:** Text messages can be sent only when the WhatsApp 24-hour customer service window is active. Otherwise, use an approved WhatsApp template.

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


---

# 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/automations-builder/create-a-drip-campaign.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.