Skip to main content

Developer tools

Webhooks in Core Forms

Send submission payloads to Zapier, Make, n8n, Slack, or any custom endpoint.

Bundled with Core Forms, the WordPress forms plugin with every premium feature in the box. No add-on tax.

Bundled, no add-on tax Unlimited sites Use code BLACKFRIDAY for 40% off either plan. Ends December 2 (IST).

The Core Forms WordPress form webhook action POSTs each submission to a URL you choose, encoded as JSON or standard form data. You can add one authentication header, such as Authorization or X-API-Key, and verify payloads with HMAC-SHA256 signatures. Failed deliveries show up in the action logs, and background runs retry automatically.

Webhooks are the universal escape hatch. Point Core Forms at any HTTP endpoint and it POSTs the submitted fields as JSON or form-encoded data. That covers Zapier zaps, Make scenarios, n8n flows, or your own API.

Webhooks at a glance

Action
Trigger Webhook
Method
POST
Body
Form-encoded (default) or JSON
Auth
One optional custom header
Signing
HMAC-SHA256, X-CF-Signature + X-CF-Timestamp
Retries
2, 4 and 8 minutes in the background queue

Full reference: Webhook action reference

What you get

How Webhooks works in Core Forms

JSON or form-encoded

Send the form fields as a JSON object or as standard form data.

Auth header

Add one header such as Authorization: Bearer … or X-API-Key. Add more, or reshape the body, with the cf_webhook_request_args filter.

Retry on failure

Actions that fail during background processing retry with exponential backoff, and every run is logged.

Conditional firing

Only POST when the submission matches your conditions.

Use cases

What people build with Webhooks and Core Forms

Send leads to your own API

Post JSON to an endpoint like https://api.example.com/submissions with an Authorization header carrying a Bearer token.

Feed an older form handler

Keep the default form-encoded body when the receiver expects a standard HTML form POST.

Verify the sender

Recompute the HMAC-SHA256 of timestamp.payload with your shared secret and reject requests older than five minutes.

Fire only for some answers

Add a condition to the action, for example department equals sales, so other submissions skip the webhook.

Set it up

Connect Webhooks in 3 minutes

  1. 1

    Get a webhook URL

    Zapier, Make, n8n, your own API — anything that speaks HTTP.

  2. 2

    Paste it into Core Forms

    Form → Actions → Add Action → Trigger Webhook, paste the URL and choose JSON or form-encoded.

  3. 3

    Add an auth header if needed

    Enter a header name and value, such as Authorization and Bearer your-token.

Every setting, filter, and error message is documented in the Webhook action reference.

Example JSON body Core Forms sends

{
  "name": "Jane Smith",
  "email": "jane@example.com",
  "message": "Hi! Interested in a demo."
}
Good to know

Requirements and limits

  • Form-encoded bodies send checkbox values in PHP array notation, so switch to JSON when the receiver needs clean arrays.
  • The auth header is sent only when both Header Name and Header Value are filled, and Bearer tokens need the full Bearer prefix.
  • Automatic retries happen in the background queue, which needs a saved submission and a running WordPress cron.
  • Retries give at-least-once delivery, so deduplicate on the receiving side if a repeated request would cause harm.
FAQ

Webhooks integration questions

Can I send JSON instead of form data?
Yes. Set Content Type to json and every field goes out as a JSON object with Content-Type: application/json. The default is application/x-www-form-urlencoded.
How do I verify a webhook came from my site?
Read the X-CF-Signature and X-CF-Timestamp headers, compute HMAC-SHA256 over {timestamp}.{body} with your secret, and compare in constant time. Reject anything older than five minutes. The webhook signatures guide has PHP, Node.js and Python examples.
What happens if my endpoint is down?
When the action runs in the background, a failure is retried after 2, 4 and 8 minutes, then marked failed. You can re-queue a failed item with POST /wp-json/cf/v1/action-queue/{id}/retry once the endpoint is back. Details are in retries and logs.
Can I add headers or change the payload with code?
Yes. The cf_webhook_request_args filter lets you add headers or edit the body before sending, and the cf_webhook_response action receives the response so you can log errors.
Should I use this or the Zapier, Make or n8n action?
Use the dedicated Zapier, Make or n8n actions when you're sending to those tools, since they shape the payload for them. Use the generic webhook for your own API or any service that needs a specific content type or auth header.

Bundled with every Core Forms license.

Webhooks and every Core Forms-built integration on this site are included with your license. Use code BLACKFRIDAY for 40% off either plan. Ends December 2 (IST).

Black Friday Sale

40% off Core Forms

Forms, polls, surveys, payments, and licensing — every feature, unlimited sites, one plugin.

Copy your code

Those are the after-discount prices. Paste BLACKFRIDAY at checkout to apply it. BLACKFRIDAY40 works too.

Ends December 2 (IST)