Automate Form.taxi With Make: 2 Modules, No Code Required

What you can automate

What can the Form.taxi Make integration do for you?

The Form.taxi Make integration links your Form.taxi forms to Make, a tool where you build a scenario, meaning an automation made of bricks called modules. Each time someone fills in one of your forms, Make can pick up that submission and pass it on to the next step, with no code to write.

Every submission lands where your team works. Watch new Form Submission hands each new entry to your scenario as a bundle, the item that flows from one module to the next. From there you add the module of any other app you already use, and the answer reaches the right person without anyone copying it by hand.

Answers you can check before trusting the flow. Run once executes the scenario a single time and shows the bundle each module received, so you see a real test entry travel through before switching anything on. Each module run counts as one operation, the unit Make uses on your plan.

The parts the trigger does not cover. Make an API call reaches any endpoint of the Form.taxi API with the same connection. When the two modules are not enough, that is the door to use rather than a workaround.

Keep the limits in mind: the Make documentation for this app is marked as AI-generated from the Form.taxi docs, so double-check what matters in your Form.taxi account, and the app needs a paid Standard plan on the Form.taxi side. The same app may also exist as an n8n node; the n8n vs Make comparison lays out the criteria, and the Make pricing page explains what your plan counts. If a run fails, start with the Make troubleshooting guide.

Connect

How do you connect Form.taxi to Make?

01
Copy your form code and API key
In Form.taxi, open the Forms panel and click the form you want to automate. Its Information section shows two values: the form code and the API key. Copy both, you will paste them into Make in a moment.
02
Add a Form.taxi module in Make
Log in to Make, open your scenario and add a Form.taxi module. Make then shows a Create a connection button, which opens a small window where your account gets linked once and reused by every Form.taxi module.
03
Name the connection and paste your credentials
The Connection name field is optional, but a clear name such as the form it serves helps when you have several. Paste the credentials you copied from Form.taxi, or follow the on-screen instructions, then save.

First scenario

Build your first scenario with Form.taxi

GoalWhen a visitor submits your Form.taxi form, Make picks up the entry and calls the Form.taxi API with it.

01
Create the scenario
On the Scenarios page, create a new scenario and click the big + to place the first module. Search for Form.taxi and pick Watch new Form Submission.
02
Link your account
Click Create a connection and paste the form code and API key from the Information section of your form. Since the form code is part of it, the connection is most likely tied to that one form.
03
Add the API call
Click the + on the right of the trigger and choose Make an API call. Point it at the Form.taxi endpoint you need and map fields from the submission the trigger just passed along.
04
Test with Run once
Send a test entry through your form, then click Run once. Open the bubble above each module to read the bundle it received and confirm the answers arrived where you expected.
05
Schedule and switch on
Click the clock on the first module to set how often Make checks the form; a new scenario runs every 15 minutes by default. Switch the scenario on and it keeps working without you.

Triggers

What starts a Form.taxi scenario

1 module starts a scenario when something happens in Form.taxi. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Form.taxi as soon as it happens.

Form.taxi1Watch new Form Submission

Watch new Form Submission

triggerIn the docs only

Hands your scenario every new entry sent through one of your Form.taxi forms, so the answers start their journey the moment Make sees them. Each submission becomes a bundle, ready to be mapped into the next module.

How it fires

scheduled (deduced from its name), so Make checks the app on the scenario's schedule rather than being alerted by Form.taxi. On the Free plan the shortest gap between two checks is 15 minutes, 1 minute on paid plans.

When to use it

it is the only way this app starts a scenario, so it opens any flow built on a contact, quote or sign-up form.

Watch out

the Make documentation for Form.taxi is marked as AI-generated, so confirm in your Form.taxi account which form the connection reads.

Modules

What else Form.taxi can do in Make

Form.taxi gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Form.taxi1

Make an API call

ActionIn the docs only

Lets you reach any endpoint of the Form.taxi API from your scenario, reusing the connection you already created, so you are not stuck when the trigger alone does not cover your need.

When to use it

as soon as you need something from Form.taxi that Watch new Form Submission does not give you.

Watch out

you choose the endpoint and write the request yourself, so keep the Form.taxi API documentation open next to Make.

Need help

Need help automating Form.taxi with Make?

A person reads every message.

FAQ

Form.taxi and Make: common questions

01Is the Form.taxi Make integration free?

Yes on the Make side: Form.taxi is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and raise execution time to 40 minutes. On the Form.taxi side, though, the integration requires an active account on the Standard paid plan, so the free part stops at Make.

02What do you need to connect Form.taxi to Make?

You need an active Form.taxi account on the Standard paid plan and the API key of the form you want to automate. Both the API key and the form code sit in the Information section of that form, which you reach from the Forms panel. In Make, add a Form.taxi module, click Create a connection, give it a name if you like, and paste those credentials. The connection is then reused by both Form.taxi modules.

03Does the Form.taxi trigger in Make fire in real time?

No. The documentation gives Watch new Form Submission no type, but its name points to a scheduled trigger: Make checks Form.taxi on the scenario's schedule instead of being called by the app through a webhook. A new scenario checks every 15 minutes by default. On the Free plan that is also the shortest possible gap, while paid plans go down to 1 minute. If you need answers to move faster, a paid Make plan is the setting that changes it.

04What if the Form.taxi module you need is missing in Make?

Use Make an API call. It reaches any endpoint of the Form.taxi API with the same connection as the trigger, so anything the API offers stays within reach even though Make only lists 2 modules for this app. You pick the endpoint and build the request, which takes a little more care than a ready-made module. Keep in mind that the Make documentation for Form.taxi is flagged as AI-generated, so confirm details with Form.taxi directly.

05Should you use Make or n8n for Form.taxi?

It depends on the tool your team already works in. Many apps that exist in Make also have an n8n node, so check whether Form.taxi has one before choosing. On the Make side, this page covers what you get: a scheduled trigger for new submissions and an API call for the rest, with no code to write. The honest criteria are the modules available in each tool for your use case and where your other automations already live.

Copy your form code and API key

Add a Form.taxi module in Make

Name the connection and paste your credentials

Create the scenario

Link your account

Add the API call

Test with Run once

Schedule and switch on

Need help automating Form.taxi with Make?