Get Plugin

Docs Integrations

Send form submissions to a webhook

Push WordPress form submissions to Zapier, Make, n8n, or your own API with a versioned JSON payload—and retry failed deliveries from Logs.

The problem

You need form data somewhere else: a CRM, Slack, a custom backend, or an automation tool. Copy-pasting from the inbox does not scale. Email-only integrations are fragile.

The solution

Sobi Forms can POST a versioned JSON payload to a URL you choose, per form. Delivery is asynchronous (WP-Cron). Failed sends appear under Settings → Webhooks → Logs with Retry.

Spam is never sent at ingest. If you later mark a submission as not spam, the webhook fires once.

How to configure it

  1. Open the form in the builder.
  2. In the sidebar, open After submit.
  3. Add action → Trigger webhook.
  4. Enter a valid https:// URL (saved only when the URL is valid).
  5. Use the Test button if available, then save the form.

There is no global on/off switch. A form has a webhook when that action is configured with a valid URL.

Where to manage webhooks

Sobi Forms → Settings → Webhooks

  • Overview — lists forms with a configured webhook (URL + link to the builder)
  • Logs — failed deliveries only (30-day retention). Retry resends the stored URL and payload

Payload

The body is a fixed, versioned JSON structure (not custom-mapped in v1). Uploaded files are referenced as objects with name, url, mime_type (and id when applicable)—not raw file bytes in the POST body.

Tips

  • On low-traffic sites, WP-Cron may wait until the next page request before the webhook runs.
  • Combine with inbox save if you want a backup while automating downstream.
  • Custom payloads, multiple URLs per form, and conditional webhooks are planned for Pro later—not in the free plugin yet.

Related