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

Every time an Avada form is submitted, FlowMattic posts the entry as JSON to a webhook URL you choose, so an app without its own FlowMattic integration still receives your form data.

Avada Forms

Webhook Outgoing

Download this workflow Browse more workflows

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

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

What this workflow does

Some tools you rely on, such as an in-house system, a niche CRM or an automation service, accept data through a webhook but have no ready-made connection in FlowMattic. This workflow bridges an Avada form to any of them by sending each submission to the URL they give you.

The Avada Forms New Form Submission trigger fires when a form built with the Avada theme receives a submission. FlowMattic passes the submitted field values to the next step.

The Webhook Outgoing Submit Data to Webhook step sends data to a webhook URL using the POST method in JSON format. It ships unmapped: after import you paste the receiving app's webhook URL and map the form fields into the data you send. Keep the keys the receiving app expects, which its own documentation will list.

Each submission makes one request. Submit a test entry, then check Task History for the response the receiving app returned, and confirm on its side that the fields arrived where you expected.

Feeding an in-house lead system

A company with its own sales database exposes a webhook endpoint, and each Avada contact form entry is posted to it as a new lead.

Handing entries to another automation tool

An agency already runs its client processes in another automation service. Avada form entries are posted to that service's catch-hook URL.

Sending applications to a hiring platform

A recruiter's Avada job application form posts each candidate's details to the webhook of an applicant tracking system that has no FlowMattic app.

How this workflow runs

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

Step 1Trigger
Avada Forms New Form Submission
Starts each time an Avada form receives a submission. The entered values are made available to map into the outgoing request.
Step 2Action
Webhook Outgoing Submit Data to Webhook
Sends a POST request in JSON to the webhook URL you enter. The step ships unmapped, so after import add the URL and map the Avada fields into the data the receiving app expects.

What you need

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

Name the keys in the outgoing data exactly as the receiving app expects them, for example email rather than Email Address, to avoid fields landing in the wrong place.
Map the submission date or the page the form was on as an extra key, so the receiving app knows where each entry came from.
If more than one Avada form starts a run, put a Filter between the New Form Submission trigger and the webhook step that continues only for the form whose entries the other app should get.

Questions about this workflow

What format does the Avada data arrive in?

The Submit Data to Webhook step sends JSON using the POST method. The keys and values are whatever you map from the Avada form after import.

How do I know whether the receiving app accepted the form entry?

Look at the run in Task History. It shows the response the webhook URL sent back, which usually tells you whether the receiving app took the data.

Do I need an account with the receiving app?

You need a webhook URL from it that accepts POST requests in JSON. Most apps that offer incoming webhooks show the URL in their settings or integration pages.