Sending a WordPress contact form to Make or n8n

Make and n8n both start an automation from a webhook URL: a Custom webhook module in Make, a Webhook node in n8n. Give that URL to your form plugin, and each entry arrives as JSON your scenario or workflow can route anywhere.

Make

Create a scenario starting with Webhooks → Custom webhook and copy its address.
Send one test entry so Make can determine the data structure.
Add the modules that do the work — a CRM, a spreadsheet, a chat message.

n8n

Add a Webhook node set to POST. Use the test URL while building, and switch to the production URL when you activate the workflow.
If you self-host n8n, make sure the URL is reachable from your WordPress server.

With Mailbag Pro

Mailbag Pro, the paid add-on to Mailbag Contact Form, sends each entry as JSON to the webhook URL you add, with the fields you choose per form. Add a secret, and every request carries an X-Mailbag-Signature header computed with HMAC-SHA256, which a Code step in Make or a Function node in n8n can check before trusting the data. The Test button sends a small test message, handy for Make's structure detection.

Because the address is one you type in, Pro calls it with WordPress' safe request functions, which refuse addresses inside your own server's network. A self-hosted n8n on the same machine therefore needs a public address.

When the scenario is off

If Make or n8n stops accepting — the scenario paused, the workflow deactivated, the server down — Pro keeps each entry, marks the connection as failing, and emails you at most once a day per connection. When the webhook answers with a 2xx again, the kept entries are sent and you get one working again email. Retries run after 5 minutes, 30 minutes, 2 hours, 12 hours and then daily, for up to 7 days.

See Mailbag Pro for the price and what a licence includes.

This is Mailbag Pro, the paid add-on to the free Mailbag Contact Form plugin. See what it costs, and what happens if you ever stop paying.

Mailbag Pro and pricing