Resources · Make integration

DataForms.io Make integrationAutomate DataForms.io with Make.

What happens to a form answer once someone clicks submit? The DataForms.io Make integration gives you 10 modules: 1 trigger, 5 actions and 4 searches. This page is for people who run forms and want the answers to reach other tools without copy and paste, and it walks you through your first scenario.

Try the DataForms.io integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the DataForms.io Make integration do for you?

The DataForms.io Make integration links your DataForms.io account to Make so that form submissions, forms and templates can move between DataForms.io and your other apps on their own. You build a scenario, which is the automation itself: a chain of modules, each module being one brick such as a trigger, an action or a search.

Every new submission lands somewhere useful. Watch Form Submits picks up the answers people send, and the next module hands them to your spreadsheet, CRM or inbox. Each answer travels as a bundle, one item passed from a module to the next.

Forms that follow your other tools. When a project opens in another app, Create a Form can prepare a form for it, and Update a Form or Update a Template keep existing ones in line when something changes on your side.

Answers you can look up on demand. Search Entries, Search Forms, Search Fields and Search Templates let a scenario find what already exists in your account before it acts, which avoids duplicates and lets you pull older answers into a report.

What the integration does not cover: anything outside those 10 modules needs Make an API Call, which reaches the DataForms.io API with the same connection. The Make documentation for this app is AI-generated from the vendor docs and may contain mistakes, so test before you rely on a detail. If you are weighing tools, read n8n vs Make; to learn the editor properly, see Make training, and for plan details, Make pricing.

Connect

How do you connect DataForms.io to Make?

  1. 01

    Create your API key in DataForms.io

    Sign in to your DataForms.io account, open Settings, then the Security section, and create a new API key. Copy the key shown on screen right away and keep it at hand for the next step.

  2. 02

    Add a DataForms.io module in Make

    In your scenario, add any DataForms.io module and click Create a connection. A connection is your DataForms.io account linked to Make once, then reused by every module of the app. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the API key you copied from DataForms.io, or follow the on-screen instructions, and save. Make now lists what it can read in your account when you fill the fields of each DataForms.io module.

First scenario

Your first scenario with DataForms.io

GoalWhen a new client appears in another app, Make creates a DataForms.io form ready for that client.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. This first module is the app where a new client shows up, such as your CRM.

  2. 02

    Add Create a Form

    Click the + on the right of that first module, search for DataForms.io and pick Create a Form. Choose your DataForms.io connection or create it with your API key.

  3. 03

    Map the client data

    Fill the fields of Create a Form, and drag the client name or other values from the first module into them. Make shows the data the previous module returned, so there is nothing to type twice.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time, then add a test client in the first app. Open the bubbles to read the bundle each module received and check the new form in DataForms.io.

  5. 05

    Schedule and switch on

    Set the schedule on the first module with the clock icon. A new scenario runs every 15 minutes by default. Then switch the scenario on so it keeps working without you.

Triggers

What starts a DataForms.io scenario

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

DataForms.io1Watch Form Submits

Watch Form Submits

triggerIn the docs only

Watch Form Submits brings each new form answer into your scenario, so the rest of the chain can file it, forward it or notify someone. Every submission becomes one bundle, and the modules after it run once per bundle.

How it fires
scheduled, which means Make checks the app on the scenario's schedule instead of being told the moment someone submits.
When to use it
as the first module whenever a filled form should lead to something in another tool, like a new row in a sheet or a message to a sales rep.
Watch out
the type is inferred from the module name in the Make docs, so check the clock badge on the module in your editor.
Modules

What DataForms.io can do in Make

DataForms.io gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

DataForms.io1

Create a Form

ActionIn the docs only

Create a Form adds a brand new form to your DataForms.io account from inside a scenario, so a form exists the moment the need for it appears elsewhere.

When to use it
a new event, client or project is logged in another app and each one needs its own form.
Watch out
run it once per record, or a scenario that loops over many bundles creates many forms.
DataForms.io2

Delete a Form

ActionIn the docs only

Delete a Form removes a form from your DataForms.io account, which keeps the account tidy once a campaign or project is closed in your other tools.

When to use it
after a project is archived and its form should no longer collect answers.
Watch out
a delete cannot be undone from Make; place a Search Forms module first to be sure you target the right one.
DataForms.io3

Make an API Call

ActionIn the docs only

Make an API Call lets you reach any endpoint of the DataForms.io API with your existing connection, which covers the jobs the listed modules leave out.

When to use it
you need an operation none of the other nine modules offers, and the DataForms.io API documentation describes it.
Watch out
you write the request yourself, so read the vendor documentation and test with Run once before switching the scenario on.
DataForms.io4

Search Entries

SearchIn the docs only

Search Entries finds submissions already stored in DataForms.io and returns them as bundles, useful when you need past answers rather than only new ones.

When to use it
building a report from older answers, or checking whether a person already replied before sending a reminder.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle, which counts operations.
DataForms.io5

Search Fields

SearchIn the docs only

Search Fields looks up the fields that make up your forms, so a scenario knows which questions exist before it reads or updates anything.

When to use it
you map answers to columns in another tool and want the scenario to work from the real field list instead of a guess.
Watch out
no match returns zero bundles, and the rest of the route simply does not run for that pass.
DataForms.io6

Search Forms

SearchIn the docs only

Search Forms returns the forms of your account that match what you ask for, giving later modules the exact form to work on.

When to use it
right before Update a Form or Delete a Form, to find the form tied to a client or project named in another app.
Watch out
several forms can match, so add a filter if only one should move on to the next module.
DataForms.io7

Search Templates

SearchIn the docs only

Search Templates lists the templates saved in DataForms.io, so you can pick the right starting point without leaving the scenario.

When to use it
your team keeps several templates and the scenario must choose one before updating it.
Watch out
like every search, it can hand over several bundles; one Update a Template run follows for each of them unless you narrow the results.
DataForms.io8

Update a Form

ActionIn the docs only

Update a Form changes an existing form in place, so its content stays in step with what changes in your other apps without editing it by hand.

When to use it
a product, date or offer changes in the tool you trust, and the matching form must follow.
Watch out
the module needs to know which form to change; place Search Forms before it when the form comes from another app.
DataForms.io9

Update a Template

ActionIn the docs only

Update a Template edits a saved template, which means every form you create from it afterwards starts from the corrected version.

When to use it
legal text, branding or a standard question changes and the template should carry it for future forms.
Watch out
the docs do not say whether forms already built from that template follow the change, so check one and use Update a Form if needed.
Need help

Need help automating DataForms.io with Make?

A person reads every message.

FAQ

Questions about DataForms.io and Make

01Is the DataForms.io Make integration free?
Yes, on the Make side. DataForms.io is a standard app, so it works on the Free plan. That plan gives you 2 active scenarios, a shortest gap of 15 minutes between scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the gap to 1 minute and remove the cap on active scenarios. Your DataForms.io subscription is separate and set by DataForms.io. Enterprise apps are the only ones kept for the Enterprise plan, and this is not one of them.
02What do you need to connect DataForms.io to Make?
An active DataForms.io account and an API key. In DataForms.io, open Settings, then Security, create a new API key and copy it. In Make, add any DataForms.io module, click Create a connection, give it a name if you like, and paste the key. That single connection is then reused by all 10 modules, so you only do this once per account. For the subscription itself, the DataForms.io pricing page is the reference.
03Does the DataForms.io trigger in Make work in real time?
No. Watch Form Submits is a scheduled trigger: Make checks DataForms.io on the scenario's schedule and collects the answers sent since the last check. A new scenario runs every 15 minutes by default. On the Free plan, 15 minutes is also the shortest gap, and paid plans allow 1 minute. Note that the Make docs list this trigger without a description, so its type comes from its name; the clock badge in the editor confirms it.
04What if a DataForms.io module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the DataForms.io API with the connection you already set up, so you are not limited to the 9 other modules. You build the request from the DataForms.io API documentation and test it with Run once. The Make documentation for this app is AI-generated from the vendor docs, so if a detail looks wrong, check it with DataForms.io directly. Keep the call narrow and check the bundle it returns before building on it.
05Should you pick Make or n8n for DataForms.io?
It depends on the tool you already work in. On Make, DataForms.io has 10 ready modules, including a trigger for new submissions and searches for entries, fields, forms and templates, plus Make an API Call for the rest. Many apps also have an n8n node, so check whether one exists for DataForms.io before choosing. The deciding factor is where the rest of your automations live, since keeping them in one tool is easier to maintain. The n8n vs Make comparison linked above goes through the criteria in more detail.
Same platform

Other docs you might need on this stack.

Browse all integrations