Is this just a webhook?

It's a native connection: FormWire's new-submission trigger appears inside Make, so you start a scenario without wiring a raw webhook URL by hand. Prefer the plumbing bare? The webhooks integration is right there.

What data reaches the scenario?

The submission's fields arrive as structured scenario data (name, email, message and any custom fields), ready to map into the modules that follow, alongside metadata like the form and timestamp.

Does spam trigger scenarios?

No. Submissions are filtered for spam before Make is notified, so a scenario only starts for a real lead — your operation budget isn't spent running modules on bots.

What if a scenario errors?

The submission is unaffected. It's stored in your dashboard and emailed to you before Make runs, so a failed scenario never costs you the lead. You can replay it in Make once the fix is in.

My scenario isn't starting on new submissions. What should I check?

Check that the scenario is switched on and scheduled to run. A scenario left off won't fire. Then confirm the FormWire connection is still authorized and watching the right form, and that the submission cleared spam filtering. Make's history log shows each trigger it received, which pinpoints where it stopped.

Can one form trigger multiple scenarios?

Yes. Point as many Make scenarios as you like at the same form's trigger: one to update the CRM, another to notify the team, a third to enrich the record.

Make integration

Start Make scenarios on every form submission.

A submission should kick off work the moment it lands (enrichment, a CRM record, a notification) rather than wait for you to notice it. FormWire starts your Make scenarios on every submission, while the email and the stored record land as usual.

Get your access key → See how it works

One submission, a whole scenario

What each Make scenario starts with.

Trigger a visual scenario

Every lead enters Make's visual builder, where you chain enrichment, CRM records and notifications across as many modules as the work needs.

Fields ready to map to modules

Each submission arrives as scenario data (name, email, message and custom fields), dropping straight into the modules that follow.

Fan out to many scenarios

Point several Make scenarios at one form's trigger: one updates the CRM, another notifies the team, a third enriches the record.

Spam never spends an operation

Bot submissions are filtered before the trigger fires, so your Make operations budget runs real work, not noise.

Set up in under a minute

Connect FormWire to Make in 3 steps.

Connect from the form
Open your form's Integrations tab and connect Make. FormWire hands Make the credentials it needs, so there's nothing to copy between tabs.
Pick the trigger
In your Make scenario, choose FormWire's new-submission trigger as the starting module. It fires the moment a submission passes spam checks.
Map the fields
Drop the submission's fields into the modules that follow (a CRM row, a Slack message, an enrichment call) and turn the scenario on.

Make integration FAQ

Setup, triggers and the details that matter.

Want a different destination?

All integrations

Route submissions elsewhere too.

All integrations

Slack, Sheets, Zapier, webhooks and more.

n8n

The self-hosted sibling to Make.

Webhooks

The raw plumbing, wired your way.

Pricing

See which plan includes Make.

Ready in a minute

Wire every submission into Make.

Connect once, pick the trigger, and every submission starts the scenario you built: enrichment, CRM, notifications, all on autopilot.

Get your access key → Read the docs