Upon receiving a new form submission in Bricks Form, send the data to an external app using Outgoing Webhooks

Each new Bricks form submission is sent as a JSON POST request to a webhook URL you choose, so an external app, script or service receives the entry the moment it arrives.

Bricks Forms

Webhook Outgoing

Download this workflow Browse more workflows

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

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

What this workflow does

Plenty of tools accept data through a webhook but have no direct connection to WordPress forms: an internal dashboard, a custom script, a CRM with an inbound endpoint. This workflow passes each entry from a form built with Bricks Builder straight to that endpoint, so you don't need extra plugin code to forward submissions.

The Bricks Forms trigger starts a run when a visitor submits the form you connect. Every field in the submission is available to the next step.

The Webhook Outgoing step, Submit Data to Webhook, sends that data to a URL using the POST method in JSON format. The template ships it unmapped. After import, paste the receiving app's webhook URL and choose which form fields go into the request, along with the names the receiver expects for them.

One entry on the form means one call to that URL. Submit a test entry, then open Task History to see the data Bricks passed in and the response the receiving URL sent back, which tells you whether the other side accepted it.

Leads into a CRM with an inbound webhook

An agency site built with Bricks posts every quote request to the inbound webhook of a CRM the sales team uses, without installing a connector plugin.

Entries for a custom script

A developer points the webhook at their own endpoint, which checks the details of each booking enquiry and saves it to a separate database.

Hand-off to a second automation tool

A team that already runs part of its lead handling in another automation service sends Bricks contact-form entries to that service's webhook URL so its existing process picks them up.

How this workflow runs

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

Step 1Trigger
Bricks Forms New Form Submission
Starts the workflow when a visitor submits the connected Bricks form. The submitted fields arrive in FlowMattic, ready to place in the outgoing request.
Step 2Action
Webhook Outgoing Submit Data to Webhook
Sends the submission to a webhook URL as a POST request in JSON format. It ships unmapped: after import, add the destination URL and map the Bricks form fields you want to send, named the way the receiving app expects.

What you need

FlowMatticCore
Bricks 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.

Check the receiving app's documentation for the field names it expects, and use those exact names when you map the Bricks fields into the request.
To send only certain entries, place a Filter between the Bricks Forms trigger and the webhook step that checks a form field, such as a service-type choice. That field is only an example; set it to one from your form.
Put a test URL from a request-inspection service in the webhook step first, submit the form once, and compare the JSON it receives with what the real endpoint expects before you switch the URL.

Questions about this workflow

What format does the Bricks entry reach the other app in?

The Bricks entry travels as JSON in the body of a POST request. The keys and values in that body are the ones you map from the Bricks form after import.

Do I need a Bricks Builder form already on my site?

Yes. The trigger listens to a form built with Bricks, so create the form first, then connect it in the trigger and send a test submission so its fields can be mapped.

How can I tell if the external app accepted the data?

Look up that run in Task History. It shows the request the webhook step sent and the response the receiving URL returned, including any error message from that service.

Can one Bricks submission go to more than one webhook URL?

Yes. Add another Submit Data to Webhook step after the first one, give it the second URL and map the fields that endpoint needs. Both requests then go out for each submission.