When new form submission is received in Divi Form, send the data to external app using Outgoing Webhooks

Every time someone submits a Divi form on your site, FlowMattic posts the submitted fields as JSON to the webhook URL of the external app, service or script you choose.

Divi Forms

Webhook Outgoing

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 1.6k sites Free to import

The When new form submission is received in Divi Form, send the data to external app using Outgoing Webhooks workflow on the FlowMattic canvas, with 2 steps across Divi Forms, Webhook Outgoing — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Divi forms are quick to build, but on their own they only email you the entry. When the data has to reach another system, such as a booking platform, a custom database or an automation tool outside WordPress, a webhook is often the simplest bridge. This workflow sends each Divi entry across as it is submitted.

The Divi Forms trigger starts a run for each new submission and makes every field from the form available to map. The Webhook Outgoing step then sends those values to a URL with a POST request in JSON format.

The template doesn't fill in the outgoing step. After import, enter the receiving app's webhook address and add the keys it expects, mapping a Divi field to each one, such as name, email and message. If the other side needs a particular structure, follow its documentation, since FlowMattic sends what you configure.

A test submission shows in Task History with the JSON that was sent and the reply from the receiving app, which helps you fix key names or a mistyped address before real visitors use the form.

Leads into a sales platform outside WordPress

A consultancy's Divi enquiry form posts each lead to the incoming webhook of its sales platform, so the sales team never copies details by hand.

Registrations to a custom app

A training provider with its own student portal receives Divi sign-up entries at an endpoint that creates the student record.

Handing off to another automation service

A marketer who builds most automations elsewhere starts them from that tool's catch-hook URL, fed by Divi form entries.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Divi Forms New Form Submission
Starts a run whenever a visitor submits a Divi form. All submitted fields become values you can map into the outgoing request.
Step 2Action
Webhook Outgoing Submit Data to Webhook
Sends the mapped Divi fields as JSON to the webhook address you enter, using a POST request. Set the address and the key names the receiving app expects after import.

What you need

FlowMatticCore
Divi Forms PluginPlugin

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Test against a temporary request-catching URL before you switch to the real address, so you see the exact JSON your Divi form produces.
If your site has several Divi forms, include a key with a fixed value naming the form, so the receiving app can tell entries apart.
Put a Filter between the Divi trigger and the Webhook Outgoing step if only some entries should leave your site, for example when a consent checkbox is ticked. Use whichever field your own form has for that.