# Direct integrations, webhooks, and unsupported providers

You'll learn when to connect your email platform directly and when to send form data to Zapier, Make, or another service with a webhook.

You can read and update contact records through a direct email-platform connection, or send form data to another service with a webhook. Here's how to choose the right connection for what you want to do.

## Can I connect RightMessage to Zapier or Make?

Yes, through an outbound webhook, but there's no native Zapier or Make connector in RightMessage's directory. You can send supported data to an HTTP webhook endpoint that your automation service provides.

A webhook sends the data you've configured. It doesn't give RightMessage a field list, contact lookup, tags, or reverse answer mappings from that service.

## Why connect my email platform directly?

A direct connection lets RightMessage look up an identified contact, use their existing data on your website, and send supported updates back. It also supplies the contact actions and answer destinations your platform supports.

For example, [WorkForge](https://workforge.rightmessage.com) can read a known contact's `work_style` field to choose an offer, then update that field when they submit a new answer. Both directions need a supported provider and a recognized visitor.

Update timing varies. There's no single timing guarantee across all providers and automation services.

## Can I send a form's name, email, and answers to a webhook?

Yes. A form webhook sends the submitted email and fields, visitor context, page URL, and submission identifiers. Optional extra data goes under `meta`. It doesn't include every historical response.

You don't need an email-platform connection for a form's **Send a webhook** action. Sending form webhooks requires **Pro**. If the destination URL contains a secret, treat it like a password.

To connect a form to your automation:

1. Open the form's **Actions** tab and choose **Send a webhook**.
2. Enter your destination's HTTPS URL in **Where to send it**.
3. Review the method and optional **Extra data**. The [form webhook settings reference](https://rightmessage.com/help/form-actions-reference) covers supported HTTP methods, Liquid variables, and JSON requirements.
4. Open **Payload preview** to see an example request.
5. Review and [publish the form changes](https://rightmessage.com/help/publishing-your-changes).
6. Submit the form with test data you control and check that your endpoint received it.

**Extra data** adds `meta` to the standard form data rather than replacing it. **Payload preview** shows an example, so you'll still need that live submission to test delivery.

![Form webhook action with a POST method, an example HTTPS destination, optional extra data, and the payload preview control](https://rightmessage.com/help/screens/verify-integrations-form-webhook.light.webp)

Each request includes an `X-RightMessage-Signature` HMAC-SHA256 signature. Verify it with your project's webhook signing secret before processing the request. The [webhook reference](https://rightmessage.com/help/webhook-reference) covers signatures, destination restrictions, and delivery limits. Check your automation service to confirm its actions completed.

## Does a webhook replace my signup action?

No. Collecting an email answer, identifying a visitor, creating a contact, and delivering a webhook are separate actions.

A webhook doesn't create a contact in your connected email platform or remove that platform's requirements elsewhere in your form or flow. Check the Email question's **Contact action** and any provider-dependent fields or rules. If you see a validation message, fix the incompatible action.

## What if my email platform isn't listed?

Contact RightMessage support with its name and what you'd like to do. First, check **Integrations**, then **Email platforms & CRMs**, or browse the [supported providers](https://rightmessage.com/help/topics/esps-and-crms).

Tell us whether you need to look up existing contacts, create subscribers, or write custom fields. A connector request doesn't make the connection available or put it on a release schedule.

You can still personalize your website with anonymous visitor behavior and question answers. An unsupported platform's forms, cookies, or contact IDs won't necessarily identify visitors in RightMessage.