When data is received via webhook in FlowMattic workflow, send it to Pabbly Connect

FlowMattic gives you a webhook URL that captures data from any app or script, then forwards the values you map to Pabbly Connect as a JSON POST, so your Pabbly automations can use it.

Webhook

Pabbly Connect

Download this workflow Browse more workflows

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

The When data is received via webhook in FlowMattic workflow, send it to Pabbly Connect workflow on the FlowMattic canvas, with 2 steps across Webhook, Pabbly Connect — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Some tools can send a webhook but have no direct connection to Pabbly Connect, or you want a single address on your WordPress site that several sources can post to. This workflow puts FlowMattic in the middle: it receives the data on your site and passes it on to Pabbly Connect.

The Webhook trigger gives the workflow its own URL. Whatever an app, form or script sends to that URL is captured and its values become available to map. The Submit Data step then sends the values you choose to your Pabbly Connect webhook as a POST request in JSON format, where a Pabbly workflow picks it up.

Every request to the FlowMattic URL produces one forward to Pabbly Connect. The workflow does not check what it receives, so treat the URL like a password and only give it to the sources you trust. Task History lists every request with the captured data and Pabbly's response.

A form tool without a Pabbly connector

Your form builder can post to any webhook URL. Point it at FlowMattic, and each entry is passed on to the Pabbly Connect workflow you already run.

One endpoint for several sources

Two landing page tools and a custom script all post to the same FlowMattic URL, and Pabbly Connect receives the data from each through one webhook.

Reshaping data before Pabbly sees it

Map only the values your Pabbly workflow needs instead of passing on everything the source sends, then check in Pabbly what arrives.

How this workflow runs

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

Step 1Trigger
Webhook Capture Webhook Response
Gives you a unique FlowMattic webhook URL. Each request sent to it is captured, and its values are available to map in the next step.
Step 2Action
Pabbly Connect Submit Data
Sends the mapped data to your Pabbly Connect webhook URL as a JSON POST request. Paste in the URL from your Pabbly trigger and choose which captured values to include.

What you need

FlowMatticCore
Pabbly Connect AccountAccount

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.

Send one sample request to the FlowMattic webhook URL after import, so the trigger captures real data you can map in the Pabbly Connect step.
Add a Filter after the trigger that continues only when a value you expect is present, such as an email field that is not empty, so incomplete requests are not forwarded.
If a FlowMattic app exists for the service you send the data to in Pabbly, you could add its action here directly and skip the extra hop.

Questions about this workflow

Where do I get the URL for the Pabbly Connect step?

Create a workflow in Pabbly Connect with a webhook trigger and copy the URL it gives you. Paste that URL into the Submit Data step in FlowMattic.

Can any app send data to the FlowMattic webhook?

Any app or script that can send an HTTP request to a URL can post to it. Send a test request to see how its data is captured before mapping.

Does Pabbly Connect receive the request exactly as it arrived at FlowMattic?

Pabbly receives what the Submit Data step sends, as JSON, based on your mapping. Send a test request and look at what arrives in Pabbly before you build on it.