- Home
- Resources
- Integrations
- Form.taxi
Form.taxi Zapier integrationAutomate Form.taxi with Zapier.
The Form.taxi Zapier integration does one thing, and does it fast: 1 trigger, 0 actions, 0 searches. Each form submission Form.taxi delivers can start a Zap in another app, on any plan, the moment it lands, free plan included.
Verified Trustpilot reviews · AI, automation & growth agency
What the Form.taxi Zapier integration actually gives you
Form.taxi is a service that receives the forms on your website and delivers each submission safely. Hooking it to Zapier means every new submission can kick off work in another app, without you copying anything by hand. That is the whole deal: one event in, as many follow-ups as your plan allows.
Everything here hangs on a single operation, New Submission. Still, it covers three very different outcomes. First, an alert: a message lands in your team chat as soon as a visitor hits send, so nobody refreshes an inbox. Second, a record: each submission becomes a row or a card in the tool where your team already tracks requests. Third, a routed lead: with a filter in between, only the submissions that match a value you pick go on to the next step (say, the ones where a visitor chose a given topic).
Now the limits, because they matter more than the promise. Zapier cannot write anything into Form.taxi. There is no action to create a submission, edit one or delete one. There is no search either, so a Zap cannot look up an older submission to reuse it. And nothing submitted before you switch the Zap on will ever be picked up (that backlog stays where it is).
So think of Form.taxi as a starting point only. It fires; other apps do the work. If you are weighing tools before you build, the n8n vs Zapier and Make vs Zapier comparisons lay out the trade-offs.
Zapier words, in plain English
Seven terms come back on this page. Here they are once, so the rest reads easily.
- Zap
- Your automation on Zapier, in one line: when the starting event happens, the steps you lined up behind it run, every time.
- Trigger
- The event that starts a Zap. Here it is a new Form.taxi submission; once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something in another app for you.
- Task
- The unit Zapier bills. One task equals one action that finished successfully; your plan counts those.
- Polling vs instant
- Polling means Zapier checks an app on a timer. Instant means the app calls Zapier itself the second the event occurs.
- Filter
- A step that lets the Zap continue only when the incoming data meets your condition, and stops it otherwise.
- Multi-step Zap
- Any Zap with more than one trigger and one action. A second action or a filter makes it one, and it needs a paid plan.
What a Form.taxi Zap costs you
Form.taxi is not a premium app, so it runs on the free plan. The trigger itself never costs a task.
- Free plan100 tasks a month, two-step Zaps
- Trigger cost0 tasks
- Premium appNo
You pay in tasks, and only for actions that succeed: a failed action is not counted. One submission turned into a Trello card is one task; the same submission sent to three apps is three. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap. Add a filter and the Zap becomes multi-step, which means a paid plan. The check intervals below concern polling triggers; New Submission is instant, so they never slow it down.
Connect Form.taxi to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your Form.taxi account linked once, then reused by every Zap that needs it.
- 02
Find Form.taxi
Type Form.taxi in the search box of the dialog, select it, then click Add connection. You need an existing Form.taxi account for this to go anywhere.
- 03
Sign in and allow access
Log in to Form.taxi in the new tab and grant Zapier access to the account. If the forms belong to someone else, ask them for access first, or the Zap will see nothing.
Your first Zap: turn project requests into Trello cards
GoalA design studio wants every brief sent through its website form to become a card on its Trello board, but only for one type of request.
- 01
Create the Zap
Start a new Zap and pick Form.taxi as the app, with New Submission as the event. Choose the Form.taxi connection you set up earlier.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent submissions of your account, so send one from the live form first if the list looks empty.
- 03
Add the filter
Click the plus icon, choose Filter, then pick the field that holds the request type, a rule, and the value you spotted in the test. Use a text rule for text.
- 04
Add the Trello action
Add Trello with Create Card, choose the board and the list, and map the submission values into the card title and description so the team sees the brief at a glance.
- 05
Test and publish
Run each step once and read what came back. When the card looks right on the board, click Publish to switch the Zap on. Remember: the filter makes it a paid-plan Zap.
The Form.taxi trigger
1 event starts a Zap when something happens in Form.taxi, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Submission
Instant triggerIn Zapier“Triggers when a new form submission is done.”
Each time a visitor completes one of your forms and Form.taxi receives it, this trigger hands the submission to Zapier. Every value the visitor typed becomes available to the steps that follow.
Where a Form.taxi Zap breaks
No help article is attached to Form.taxi on Zapier, and no app-specific limit is on record. What can go wrong is general Zapier behaviour.
Four cases are worth knowing before you publish. If one keeps biting, the Zapier troubleshooting guide is the next stop.
Old submissions never arrive
The Zap only sees submissions received after it is switched on. Anything older stays in Form.taxi and needs a separate move.The filter never lets anything through
A text rule only reads text and a number rule only reads numbers. Choose the wrong one for the request-type field and the action never runs.The filter pushes you off Free
Free plans run one trigger and one action. The filter in the example above adds a step, so that Zap is multi-step and needs a paid plan.A sudden wave of submissions is held back
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those runs back.
Need help automating Form.taxi with Zapier?
A person reads every message.



