> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chatsyncs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Send Automated WhatsApp Messages on WP Form Submission in ChatSyncs

> A worked example of a Webhook Workflow: wiring a WordPress form plugin (Elementor, Gravity Forms, WPForms) to trigger a WhatsApp message on form submission.

This is a worked example of a [Webhook Workflow](/learn/chatsyncs-webhook-workflow/introduction) — the
ChatSyncs feature that sends a WhatsApp message automatically whenever an outside event happens.
Here, that event is a WordPress form submission.

```text theme={null}
Website visitor fills out a WordPress form
        │
        ▼
WordPress form plugin sends the data to a webhook URL
        │
        ▼
ChatSyncs Webhook Workflow receives it
        │
        ▼
WhatsApp message sent
```

## Step 1: Make your WordPress form send a webhook

WordPress doesn't send webhooks on its own — the form plugin needs to be told to POST the
submission somewhere. How you do this depends on the plugin:

* **Elementor Forms** — has a built-in **Webhook** action; add it under the form's Actions After
  Submit and paste in the webhook URL.
* **Gravity Forms** — install the official **Webhooks** add-on, then add a webhook feed pointing
  to the URL.
* **WPForms** / **Contact Form 7** — use a webhook-capable add-on or connect through an
  automation tool like Zapier or Make.com that can call a webhook on form submission.

<Tip>
  Whichever plugin you use, the goal is the same: get the form's field values (name, phone
  number, message) posted as JSON or form data to one URL — the callback URL you'll get from
  ChatSyncs in Step 2.
</Tip>

## Step 2: Create the workflow in ChatSyncs

Follow [Create a Webhook Workflow](/learn/chatsyncs-webhook-workflow/create-a-webhook-workflow-in-chatsyncs) to create the workflow, get
its callback URL, and map the form's fields to your message template's
[Variables](/learn/chatsyncs-message-templates/creating-a-whatsapp-message-template-in-chatsyncs#create-a-template-variable-first). The one
WordPress-specific detail: paste that callback URL into your form plugin's webhook settings from
Step 1 (e.g. Elementor's **Actions After Submit → Webhook** field), not into a third-party app.

**Example:** A contact form on `mywebsite.com` collects **Name**, **Phone**, and **Message**. On
submit, Elementor's Webhook action posts that data to the ChatSyncs callback URL, which sends the
customer an instant WhatsApp confirmation — *"Hi Rahul, thanks for reaching out! We'll get back
to you shortly."*

## Step 3: Add a delay, conditions, or post-call actions (optional)

Want to wait before sending, only send for certain submissions, or auto-assign the conversation
to a team? See [Webhook Automation Settings](/learn/chatsyncs-webhook-workflow/webhook-automation-settings-in-chatsyncs) — it
applies the same way regardless of which app triggered the workflow.

## Monitoring your workflow

See [Webhook Workflow Reporting](/learn/chatsyncs-webhook-workflow/webhook-workflow-reporting-in-chatsyncs) for reading delivery stats
and troubleshooting a workflow that isn't sending.

## Other common uses beyond WordPress

The same Webhook Workflow works for any system that can send an HTTP request, not just
WordPress:

* **Order confirmation / shipping updates** — from Shopify or another store platform.
* **Appointment reminders** — from a booking system's webhook.
* **Payment confirmation** — from a payment provider's webhook.
* **Lead follow-up** — instantly message a new lead captured by another system.
* **Event registration** — confirm a signup with a personalized message.

<Warning>
  - **Always include a `phone` field in your form** — it's mandatory; without it ChatSyncs has no
    destination for the message.
  - **Send phone numbers in international format** (e.g. `919876543210`).
  - **Keep field names consistent** — renaming a form field breaks its mapping silently.
  - **Use an approved template** — a workflow can't send a template that hasn't come back
    **Approved** from Sync Template.
</Warning>

## Frequently asked

<AccordionGroup>
  <Accordion title="Does WordPress send webhooks by default?">
    No — the form plugin needs a webhook feature or add-on (Elementor Forms has one built in;
    Gravity Forms needs its Webhooks add-on) to POST the submission to a URL.
  </Accordion>

  <Accordion title="What's actually receiving the webhook on the ChatSyncs side?">
    A **Webhook Workflow** — the same feature used for any external system (Shopify, Postman, a
    custom script) that posts data to trigger a WhatsApp message. See [What Is a Webhook
    Workflow](/learn/chatsyncs-webhook-workflow/introduction).
  </Accordion>

  <Accordion title="Can I send the message to the person who filled out the form, not just my team?">
    Yes — map the form's phone number field to the recipient, the same way you'd map any other
    field to a template variable in [Create a Webhook Workflow](/learn/chatsyncs-webhook-workflow/create-a-webhook-workflow-in-chatsyncs).
  </Accordion>

  <Accordion title="Can I test this without a live WordPress form yet?">
    Yes — click **Capture Webhook Response** in ChatSyncs, then send a POST request to the
    workflow's callback URL from any tool (Postman, curl, a no-code automation app) with your
    test JSON body. See [Create a Webhook Workflow](/learn/chatsyncs-webhook-workflow/create-a-webhook-workflow-in-chatsyncs).
  </Accordion>
</AccordionGroup>