Sending a WordPress contact form to Make or n8n

Make

1. Create a scenario starting with Webhooks → Custom webhook and copy its address.
2. Send one real entry from your form while Make is listening, so it can determine the data structure.
3. Add the modules that do the work — a CRM, a spreadsheet, a chat message.

n8n

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

With Formsafe Pro

Formsafe Pro, the paid add-on to Formsafe Contact Form, posts each entry as JSON to the webhook URL you add: the form's name and id, the entry's id, when and from which page it was sent, the email address, and every field with its label. Add a secret, and every request carries X-Formsafe-Signature: sha256=… — an HMAC-SHA256 of the body — which a code step in Make or a Code node in n8n can check before trusting the data. The Test button only posts {"test": true}, which proves the address answers; it tells Make nothing about your fields.

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 — and any port other than 80, 443 and 8080. A self-hosted n8n on the same machine therefore needs a public address, and one on n8n's default port, 5678, needs to sit behind an ordinary https address first. Pro takes only https addresses, because each entry carries a person's details across the internet to get there.

When the webhook stops answering

An entry counts as delivered only on a 2xx answer; anything else keeps the entry for another try. A refusal — a 404 for a webhook address the service doesn't know, a 410 for a hook that was switched off — marks the connection as failing at once, and a server error, a rate limit (429) or a timeout does so after three deliveries in a row. While it is failing, Pro 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.

What Pro can't see is a service that answers success and then doesn't run your automation. After changing a scenario or workflow, send a real entry and check the run history. See Formsafe Pro for the price and what a licence includes.