Resources · Make integration

Web Data Forms Make integrationAutomate Web Data Forms with Make.

Can a new form submission start work in your other tools on its own? The Web Data Forms Make integration gives you 8 modules: 2 triggers and 6 actions. This guide is for teams that collect data through forms and want to link your account, build one working scenario and pick the right module.

Try the Web Data Forms integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Web Data Forms Make integration do?

The Web Data Forms Make integration links your Web Data Forms account to Make, a no-code automation tool. You build a scenario, the automation itself, out of modules: small bricks that each watch for something, read data or change it. Web Data Forms brings 8 of them, so submissions, datasets, workflows and reports can move without copy and paste.

Pass every submission to the rest of your stack. Watch New Submissions spots new entries, and Get a Submission pulls the full record so a later module can file it in a spreadsheet, a CRM or a chat channel. If you are comparing form tools, the 123FormBuilder Make integration covers a similar need with another app.

Keep datasets current. Get a Dataset reads a dataset, and Update a Dataset writes changes back after another app has done its part, for example once a record is approved elsewhere.

Follow and steer workflows. Watch Workflows, going by its name, starts a scenario from activity on your workflows, Update a workflow edits one, and Create a Report produces a report when a batch of work is done.

Know the limits before you start. Make's own documentation for this app is marked as limited: it lists the modules but describes none of their fields, and gives no connection steps of its own. Expect to discover each module's options in the editor, and use Make an API Call for anything the list does not cover. The Make troubleshooting guide helps when a run fails. The same app may also have an n8n node; the n8n vs Make comparison lays out how the two tools differ.

Connect

How do you connect Web Data Forms to Make?

  1. 01

    Add a Web Data Forms module

    In your scenario, click the +, type Web Data Forms in the search box and pick any of its modules. The first time, Make shows a Create a connection button: a connection is your account linked to Make once and reused by every module of the app.

  2. 02

    Name it and authorize Make

    Give the connection a name you will recognize later, such as the account or team it belongs to. Then either approve access on the Web Data Forms page that opens, or paste the key your Web Data Forms account gives you, depending on what the window asks for.

  3. 03

    Save and check the fields

    Click Save. The module now shows its fields, and Make can list the items it is able to read from your account. If that list stays empty, the connection is the first thing to check.

First scenario

Your first scenario with Web Data Forms

GoalWhen a new submission lands in Web Data Forms, Make fetches the full record so you can send it anywhere.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle of the editor to place the first module.

  2. 02

    Add Watch New Submissions

    Search Web Data Forms, choose Watch New Submissions and select your connection, or click Create a connection if this is your first module of the app. Fill the fields the module shows.

  3. 03

    Fetch the full submission

    Click the + to the right of the trigger and add Get a Submission. Map the identifier coming from the trigger into it, so each run reads the exact entry that was just detected.

  4. 04

    Send the data on

    Add one more module from the app that should receive the entry, a sheet or a CRM for instance, and map the submission data into its fields. Each item passing between modules is called a bundle.

  5. 05

    Test with Run once

    Submit a test entry in your form, then click Run once. Open the bubble above each module to read the bundles it received and confirm the data arrived where you expected.

  6. 06

    Schedule and switch on

    Click the clock on the first module to set how often Make checks for entries: every 15 minutes by default, 15 minutes at the shortest on the Free plan. Then switch the scenario on.

Triggers

What starts a Web Data Forms scenario?

2 modules start a scenario when something happens in Web Data Forms. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Web Data Forms as soon as it happens.

Web Data Forms1Watch New Submissions

Watch New Submissions

triggerIn the docs only

This trigger opens a scenario each time someone sends a new entry through one of your Web Data Forms forms, so the answers reach your other tools without you exporting anything. Make's documentation describes no fields for it, so check its options in the editor once your connection is set.

How it fires
listed as a scheduled trigger, going by its name: Make checks the app on the scenario's schedule, every 15 minutes by default, rather than being called the moment a form is sent.
When to use it
a contact or registration form whose answers must reach a sheet, a CRM or a team channel.
Watch out
each check uses operations even when nothing new arrived, so a tighter schedule costs more.
Web Data Forms2Watch Workflows

Watch Workflows

triggerIn the docs only

With this trigger, activity on your Web Data Forms workflows becomes the starting point of an automation instead of something you track by hand. The documentation gives no description and no fields, so what counts as a change is best confirmed with a test in the editor.

How it fires
scheduled, going by its name. Make checks the app on the scenario's schedule, so a change shows up at the next check rather than the instant a workflow moves.
When to use it
you want a manager alerted, or a record updated elsewhere, whenever a workflow shows up in your account.
Watch out
run it once on a test workflow and read the bundle before relying on it, since its output is not documented.
Modules

What else can Web Data Forms do in Make?

Web Data Forms gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Web Data Forms1

Create a Report

ActionIn the docs only

You get a report generated in Web Data Forms from inside the scenario, instead of opening the app and building it yourself once a batch of data is ready.

When to use it
as the last module, after a set of submissions has been processed and someone needs a summary.
Watch out
the documentation lists no report options, so run a test and open the result in Web Data Forms before you switch the scenario on.
Web Data Forms2

Get a Dataset

ActionIn the docs only

Reading one dataset from your account puts its content in the scenario, ready to map into any later module. It acts on a single dataset per run, so you need to know which one to ask for.

When to use it
before Update a Dataset, to see the current values, or to copy a dataset into a spreadsheet.
Watch out
the fields it returns are not documented; read them in the bundle after Run once.
Web Data Forms3

Get a Submission

ActionIn the docs only

Pulling one submission by its identifier gives the next module the complete answer set for that entry. It pairs naturally with Watch New Submissions, which spots the entry, while this module fetches the whole record.

When to use it
whenever a trigger or another app hands you a submission reference and you need the answers themselves.
Watch out
map the identifier from the previous module rather than typing it, or every run reads the same entry.
Web Data Forms4

Make an API Call

ActionIn the docs only

When none of the other seven modules does what you need, this one lets you call any endpoint of the Web Data Forms API from the scenario, with the same connection and no separate login.

When to use it
any action of the Web Data Forms API that the module list does not show, once you know the endpoint.
Watch out
you write the request yourself, so keep the Web Data Forms API reference open; Make's own page for the app says nothing about it.
Web Data Forms5

Update a Dataset

ActionIn the docs only

Changing an existing dataset from the scenario keeps it in line with what happened in your other apps, without editing it by hand in Web Data Forms. It writes to one dataset, the one you point it at.

When to use it
after an approval or a payment recorded elsewhere should be reflected in the dataset.
Watch out
Make does not document which values it changes, so read the dataset first with Get a Dataset and compare after a Run once.
Web Data Forms6

Update a workflow

ActionIn the docs only

This action edits a workflow already in your account, so a decision taken in another tool is applied in Web Data Forms without anyone switching windows. It targets one existing workflow; it does not create new ones.

When to use it
following Watch Workflows, to move or adjust the workflow the trigger just reported.
Watch out
the options it accepts are not documented, so test it on a throwaway workflow first.
Need help

Need help automating Web Data Forms with Make?

A person reads every message.

FAQ

Web Data Forms and Make: common questions

01Is the Web Data Forms Make integration free?
Yes, the app is a standard app, available from the Free plan. That plan allows 2 active scenarios, a shortest interval 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 interval to 1 minute, remove the cap on active scenarios and allow runs of up to 40 minutes. Usage is counted in operations, one per module per bundle.
02What do you need to connect Web Data Forms to Make?
A Web Data Forms account and a Make account. The documentation lists no prerequisite and no dedicated steps, so the connection follows Make's usual path: add any module of the app, click Create a connection, give it a name, authorize Make on the app's page or paste the key the app gives you, then click Save. The same connection then serves all 8 modules, triggers and actions alike. No extra setup is needed per module.
03Does the Web Data Forms trigger react in real time?
No. Both triggers, Watch New Submissions and Watch Workflows, are scheduled going by their names, and none of the 8 modules is marked instant. Make checks the app on the scenario's schedule, every 15 minutes by default. On the Free plan 15 minutes is the shortest interval; paid plans go down to 1 minute. Keep in mind that each check consumes operations, even when it finds nothing new. Pick the interval that matches how quickly you need the data.
04What if a Web Data Forms module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Web Data Forms API with the connection you already set up, so an action absent from the 6 listed modules can still run inside the scenario. Make's documentation for this app is marked as limited and describes no fields, so the Web Data Forms API reference is where you will find the request details. Test each call with Run once first.
05Should you use Make or n8n for Web Data Forms?
It depends on what you already run. On Make you get 8 ready modules, 2 scheduled triggers and 6 actions, plus Make an API Call for the rest, on a visual editor where you test with Run once. The same app may also have an n8n node. Compare the modules each tool offers for the actions you need, and pick the tool your team already uses day to day. Both editors let you test before switching anything on.
Same platform

Other docs you might need on this stack.

Browse all integrations