> 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/integrations/n8n/send-messages-using-n8n.md).

# Send Messages using n8n

WhatsApp Business API Node Setup in n8n

* Go to **Settings → Community Nodes**
* Click on **Install Community Node**
* Paste the npm package name as **n8n-nodes-whatsapp-business-api-by-automations-builder**
* Click **Install**

**Step 2: Add WhatsApp Business API Node**

* Create a new workflow
* Search for **WhatsApp Business API**
* Select **WhatsApp Business API by Automation Builder**
* Add it to the workflow

**Step 3: Configure Credentials**

Enter the following details:

* Access Token
* Phone Number ID
* WABA ID
* Graph API Version

Click **Save** and test the connection.

**Step 4: Select Message Type**

The node supports:

* Text Messages
* Contacts
* Interactive Messages
* Location
* Media Messages
  * Image
  * Video
  * Audio
  * Document
  * Sticker
* Reactions
* Template Messages

**Step 5: Send Template Message**

* Select **Template Message**
* Choose the template
* Add variable values
* Enter recipient phone number
* Execute the workflow step

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


---

# 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/integrations/n8n/send-messages-using-n8n.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.