- Home
- Resources
- Integrations
- Funnelforms Legacy
Funnelforms Legacy Zapier integrationAutomate Funnelforms Legacy with Zapier.
Funnelforms Legacy Zapier integration: 1 trigger, 0 actions, 0 searches. Each new form entry can start an automation that hands the lead to another tool, checked on a timer and usable on the free plan. Below: the cost, the setup, and the failure cases.
Verified Trustpilot reviews · AI, automation & growth agency
What the Funnelforms Legacy Zapier integration really does
Funnelforms Legacy is a form builder plugin for WordPress, aimed at lead generation. Plugged into Zapier, it does one thing: each time someone submits one of your forms, that entry can kick off an automation and land in another app, without anyone copying it by hand.
Everything rests on a single trigger, New Entry. That sounds thin, yet it covers the job most form owners want done. Three typical outcomes:
A fresh contact in your CRM. The entry arrives, and a sales tool such as HubSpot gets a new record built from what the visitor typed. A ping for the team. The same entry can post a message in a chat channel so somebody calls the lead back while it is still warm. A running log. Each submission adds a row to a spreadsheet, which gives you a list you can sort, share or hand to an accountant.
Now the part the official page skips. Zapier cannot write anything into Funnelforms Legacy: there is no action, so no Zap creates an entry, edits a form or deletes a submission. There is no search step either, so a Zap cannot go back and look up an older entry. The flow runs one way, out of the plugin. And the trigger works on a timer (it is not instant), so on the free plan a lead can wait up to 15 minutes before it shows up anywhere.
If you are weighing another automation tool for the same plugin, the Funnelforms Legacy Make integration page exists too, and the Make vs Zapier comparison sets the two side by side.
The Zapier words you will meet, in one minute
Seven terms come back on every screen. Here they are in plain English, once.
- Zap
- The automation you build: one starting event, then one or more steps that run every single time that event happens.
- Trigger
- The event that starts the Zap. Here it is a new form entry. Once the Zap is switched on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something in another app on your behalf.
- Task
- The unit Zapier bills you for. One task is one action that went through; your plan gives you a monthly count of them.
- Polling trigger
- A trigger Zapier checks on a timer. It asks the app for new items at a fixed interval and keeps only the ones it has not seen.
- Instant trigger
- The opposite: the app calls Zapier the moment the event happens. New Entry is not one of these, it works by polling.
- Filter
- A step that lets the Zap continue only when the incoming data meets a condition you set, and stops it quietly otherwise.
What it costs to run
Funnelforms Legacy is not a premium app, so it works on the free plan. The bill depends on actions, never on the trigger.
- TriggerFree, never counted
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps only
- Premium appNo, works on the free plan
Checking for new entries costs nothing, however often Zapier looks. Only an action that succeeds counts as a task, and one that fails is not billed. The free plan gives you 100 tasks a month, as many Zaps as you like, and a check every 15 minutes. The catch: it only builds two-step Zaps, one trigger and one action. Add a second action or a filter and the Zap becomes multi-step, which needs a paid plan.
Connect Funnelforms Legacy to Zapier in three steps
- 01
Open your connections
In your Zapier account, go to the Apps page and click + Add connection. A connection is your Funnelforms Legacy account linked once, then reused by every Zap that touches it.
- 02
Find the app
Type Funnelforms Legacy in the dialog, pick it from the results, then click Add connection. You need an existing account on the plugin before this works.
- 03
Sign in and allow access
Log in to Funnelforms Legacy in the tab that opens and grant Zapier access to the account. If a form belongs to someone else, you also need read access to it.
Your first Zap: from a form entry to a CRM contact and a Slack alert
GoalEvery new entry on a quote form becomes a HubSpot contact, then the sales team gets a message in Slack.
- 01
Create the Zap and pick the trigger
Start a new Zap, choose Funnelforms Legacy as the app and New Entry as the event, then select the connection you set up earlier.
- 02
Point it at the right form
Fill in the Formular ID of the quote form. Run the test: Zapier pulls the three most recent entries of that form so you can pick a real one to map from.
- 03
Add the HubSpot step
Add HubSpot as the first action and map the answers of the entry you picked into the contact fields. Test it once and check the record in HubSpot.
- 04
Add the Slack message
Add Slack as a second action and write a short line that quotes the lead's name. This second action makes the Zap multi-step, so it runs on a paid plan.
- 05
Publish
Click Publish to switch the Zap on. From then on, each new entry costs two tasks when both actions go through: one for HubSpot, one for Slack.
The Funnelforms Legacy trigger
1 event starts a Zap when something happens in Funnelforms Legacy. Zapier checks for them at the interval your plan allows.
New Entry
Polling triggerIn Zapier“Triggers when a new form entry was made.”
Picks up every submission made on the form you choose and passes its answers to the next step of the Zap, so a lead never sits unread inside WordPress.
When the Zap breaks, and why
Zapier attaches no help article to Funnelforms Legacy, and no limit specific to the plugin is documented. What breaks here comes from how Zapier itself behaves.
Four cases cover almost every surprise. All four come from how Zapier treats triggers, so knowing them before you publish saves a bad surprise. For deeper digging, the Zapier troubleshooting page is there.
Old entries are never sent
A Zap only reacts to what happens after you switch it on. Submissions already sitting in Funnelforms Legacy stay there; moving that backlog is a separate job.A loop that eats your tasks
If a later step writes into the very place a trigger watches, the Zap sets itself off again and again. Keep each Zap's output away from its own starting point.A sudden flood gets held back
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those items back instead of running them all.The same entry only counts once
Zapier remembers what it has already seen on a polling trigger, so an entry does not start the Zap twice.
Need help automating Funnelforms Legacy with Zapier?
A person reads every message.



