Automate MakeForms With Make: 2 Modules, Zero Code Needed

What you can automate

What can the MakeForms Make integration do for you?

The MakeForms Make integration links your MakeForms account to Make so that a new form response can start an automation, called a scenario, without any code. Each scenario is a chain of modules, and each module is one brick: here, a trigger that notices responses and an action that talks to the MakeForms API.

Responses that reach your team. Watch New Response hands each answer to the next module as a bundle, one item passed along the chain. Add a module from your messaging or email app after it, and a sales rep hears about a new lead without opening the form dashboard.

A tidy record of every submission. Put a spreadsheet or database module behind the same trigger and each response becomes a row. The support lead gets one place to sort requests, and nobody copies answers by hand.

The parts of MakeForms the list leaves out. Make an API Call reaches any endpoint of the MakeForms API with the connection you already set up. It is the route to take when the two listed modules stop short of what you need.

Know the limit before you start: Make's documentation for MakeForms is marked as limited, because little public information exists about the app. Field details are not described there, so the Run once test is where you discover what a response contains. If you are still weighing platforms, the n8n vs Make comparison lays out the differences, and the Make pricing guide explains how operations are counted. Stuck on an error? See Make troubleshooting.

Connect

How do you connect MakeForms to Make?

01
Add a MakeForms module
In a scenario, search for MakeForms and pick any of its modules. Then click Create a connection. A connection is your MakeForms account linked to Make once, and every MakeForms module in your scenarios reuses it.
02
Name the connection
Giving the connection a name is optional, but it pays off the day you link a second MakeForms account, for a client or a test workspace. A clear label keeps you from picking the wrong one later.
03
Authorize and save
Depending on what MakeForms asks for, either approve access for Make on the MakeForms page or paste the key the app gives you. Click Save, and the module shows your account as ready to use.

First scenario

Build your first scenario with MakeForms

GoalWhen someone submits a form in MakeForms, Make passes the new response to the MakeForms API endpoint you choose.

01
Create the scenario
Open the Scenarios page, create a new scenario and click the big + in the middle of the editor. That empty circle becomes your first module.
02
Add Watch New Response
Search for MakeForms, choose Watch New Response and select your connection, or click Create a connection if you have none yet. Fill in the fields Make shows for this trigger.
03
Add Make an API Call
Click the + on the right of the trigger and add Make an API Call from MakeForms. It reuses your connection; enter the endpoint from the MakeForms API reference and map values from the response.
04
Test with Run once
Submit a test answer to your form, then click Run once. Open the bubble above each module to read the bundle it received and check that the data landed where you expected.
05
Schedule and switch on
Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. From that point, new responses flow through without you.

Triggers

What starts a MakeForms scenario

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

MakeForms1Watch New Response

Watch New Response

triggerIn the docs only

This trigger gives your scenario a starting point every time a form collects a fresh answer, so the response can move on to a CRM, a sheet or an inbox without anyone forwarding it.

How it fires

it is a scheduled trigger, so Make checks MakeForms on the scenario's schedule rather than being called the moment a response arrives. On the Free plan the shortest gap between two checks is 15 minutes; paid plans go down to 1 minute.

When to use it

a contact or quote form whose answers need to reach a person or a tool without manual copying.

Watch out

each response is one bundle, and every module after it spends an operation on that bundle.

Modules

What else Make can do with MakeForms

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

MakeForms1

Make an API Call

ActionIn the docs only

This action opens the rest of the MakeForms API to your scenario: you call any endpoint of the app while reusing the connection you already created, instead of setting up authentication again.

When to use it

when Watch New Response alone does not cover your need and the MakeForms API offers the operation you are after.

Watch out

you need the endpoint and its parameters from the MakeForms API reference, since Make's own documentation for this app is limited.

Need help

Need help automating MakeForms with Make?

A person reads every message.

FAQ

MakeForms and Make: common questions

01Is the MakeForms Make integration free?

Yes, MakeForms is a standard app in Make, so you can use it on the Free plan. That plan has its own limits: 2 active scenarios, at least 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 (Core, Pro, Teams and Enterprise) lift the scenario cap and bring the interval down to 1 minute. Usage is counted in operations, one per module per bundle.

02What do you need to connect MakeForms to Make?

You need a MakeForms account and a Make account. Make's documentation lists no specific prerequisite for this app and gives no dedicated connection steps, so the standard flow applies: add a MakeForms module, click Create a connection, optionally name it, authorize Make or paste the key MakeForms provides, then click Save. The connection is then reused by both MakeForms modules in any scenario you build. Once saved, it appears in the connection list of every MakeForms module you add later.

03Does the MakeForms trigger react in real time?

No. Watch New Response is a scheduled trigger: Make checks MakeForms on the scenario's schedule instead of being notified the moment someone submits a form. A new scenario runs every 15 minutes by default. On the Free plan that is also the shortest possible interval, while paid plans allow checks as often as every 1 minute. For most form follow-ups this delay stays acceptable, and you can tighten it later if needed.

04What if a MakeForms module you need is missing in Make?

It depends on what you are missing. The app has only 2 modules, and Make an API Call is the way to go further: it can reach any endpoint of the MakeForms API with the same connection. Keep in mind that Make marks its MakeForms documentation as limited because little public information exists about the app, so you will rely on the MakeForms API reference to know which endpoints and parameters to use.

05Should you use Make or n8n for MakeForms?

It depends on the criteria that matter to you. In Make, MakeForms offers a scheduled trigger for new responses plus an open API call, both available on the Free plan, and the editor lets you test each step with Run once. Many apps also have an n8n node, so check whether that holds for MakeForms before choosing. Compare the two tools on the modules you need and how each one counts usage.

Add a MakeForms module

Name the connection

Authorize and save

Create the scenario

Add Watch New Response

Add Make an API Call

Test with Run once

Schedule and switch on

Need help automating MakeForms with Make?