Resources · Make integration

VeriForms Make integrationAutomate VeriForms with Make.

What can Make do with your VeriForms forms and the answers they collect? The VeriForms Make integration gives you 9 modules: 1 scheduled trigger, 5 actions and 3 searches. This page walks you through the connection, a first scenario and what each module is for.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the VeriForms Make integration let you automate?

The VeriForms Make integration links your VeriForms account to Make, so form submissions and form structures can feed other tools without code. You build a scenario, the automation itself, out of modules, the bricks that each watch, fetch or change one thing in VeriForms.

React to new answers. Watch Submissions starts the scenario when VeriForms has fresh submissions, and Get Submission pulls the full record so the next module can file it, notify someone or update a spreadsheet.

Keep an inventory of your forms. List Forms and Form Details return what exists in the account and the details of one form, handy when an operations team has to document which forms exist.

Share and maintain forms. Create a FormShare and Update Form Structure to latest Version act on a form from inside a scenario, and Search Form Structure helps you find the structure to work on first.

Be aware of one limit: Make itself says its documentation for VeriForms is incomplete, because little public information exists about the app. Expect to discover the fields inside each module. For anything the listed modules miss, Make an API Call reuses the same connection. If you are weighing tools, read n8n vs Make; if you are new to the editor, Make training covers the basics, and Make troubleshooting helps when a run fails.

Connect

How do you connect VeriForms to Make?

  1. 01

    Add a VeriForms module

    In your scenario, add any VeriForms module and click Create a connection. A connection is your VeriForms account linked to Make once, then reused by every VeriForms module you add later.

  2. 02

    Name the connection

    Give it a name you will recognize, such as the workspace or client it belongs to. This step is optional, but it saves confusion once you manage several accounts in the same Make organization.

  3. 03

    Authorize and save

    Either approve Make on the VeriForms page that opens, or paste the key VeriForms gives you, depending on what the window asks for. Then click Save and the module is ready to configure.

First scenario

Your first scenario with VeriForms

GoalWhen a new submission lands in VeriForms, Make fetches the full answers and the form they belong to.

  1. 01

    Create the scenario

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

  2. 02

    Add Watch Submissions

    Search for VeriForms, pick Watch Submissions and click Create a connection to link your account. Then pick the form or options Make lists once it can read your account.

  3. 03

    Fetch the full submission

    Click the + to the right of the trigger, add Get Submission and map into it the submission data coming from Watch Submissions.

  4. 04

    Add the form details

    Add Form Details after it and map the form from the previous modules. Each submission now travels with the context of the form it came from.

  5. 05

    Test with Run once

    Send a test answer through your form, click Run once and open each module to read the bundles it received, one bundle per submission.

  6. 06

    Schedule and switch on

    Click the clock on the first module to set Scheduling, every 15 minutes by default, then switch the scenario on. Add another app after Form Details when you are ready.

Triggers

What starts a VeriForms scenario

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

VeriForms1Watch Submissions

Watch Submissions

triggerIn the docs only

You get every new VeriForms submission handed to your scenario as its own bundle, one item that moves from module to module, so each answer can be processed on its own.

How it fires
scheduled. Make checks VeriForms on the scenario's schedule, every 15 minutes by default, 1 minute at the shortest on paid plans, 15 minutes on the Free plan.
When to use it
any time a new answer should set something in motion, like alerting a manager or copying the data into another tool.
Watch out
since Make publishes no description of this module, run it once on a test form to see which submissions it picks up.
Modules

Everything the VeriForms modules can do

VeriForms gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

VeriForms1

Create a FormShare

ActionIn the docs only

Hands you a new FormShare for a form straight from a scenario, so sharing a form no longer means a manual trip into VeriForms. Make gives no description of what a FormShare contains, so check the output after a test.

When to use it
when another event, such as a new client record in your CRM, should result in a form being shared.
VeriForms2

Form Details

ActionIn the docs only

Returns the details of one VeriForms form, so later modules know which form they are dealing with. It reads a single form you point it to, rather than searching across the account.

When to use it
right after a submission arrives, to attach the form's information to the answers before sending them on.
Watch out
map the form from a previous module instead of hardcoding it.
VeriForms3

Get Submission

ActionIn the docs only

Gives you one complete submission, the one you point it to, ready to map into the next app. Pick it when you already know which answer you need; List Submissions is the choice when you need several.

When to use it
after Watch Submissions, when you want the whole record before writing it to a spreadsheet or a ticket.
VeriForms4

List Forms

SearchIn the docs only

Brings back the forms of your VeriForms account, each one as a separate bundle. As a search, it can return zero, one or many results, and every result can cost an operation, one run of one module, in the modules that follow.

When to use it
to build an inventory of your forms in a sheet or to loop over all of them.
VeriForms5

List Submissions

SearchIn the docs only

Pulls a batch of submissions instead of one, each landing as its own bundle for the rest of the scenario. It suits catching up on past answers rather than reacting to new ones.

When to use it
for a first import of existing answers into another tool.
Watch out
a search can return zero bundles, so test on a form that already has answers.
VeriForms6

Make an API Call

ActionIn the docs only

Lets you reach any endpoint of the VeriForms API with the connection you already set up, which covers whatever the 8 other modules leave out. You need the VeriForms API documentation at hand to know the path and parameters.

When to use it
only once you have checked that no listed module does the job.
VeriForms7

Search Form Structure

SearchIn the docs only

Finds the structure of a form so you can see how it is built before acting on it. Like every search, it may return nothing, one match or several, and each match travels as its own bundle.

When to use it
before updating a structure, to confirm you target the right form.
Watch out
add a filter after it if you only want one result to go through.
VeriForms8

Update Form Structure to latest Version

ActionIn the docs only

Brings a form's structure up to its latest version from inside a scenario, with no need to open VeriForms and do it by hand. You stay in the scenario from start to finish.

When to use it
after Search Form Structure has identified the form to refresh.
Watch out
run it on a test form first, since Make does not say what the update changes.
Need help

Need help automating VeriForms with Make?

A person reads every message.

FAQ

VeriForms and Make: common questions

01Is the VeriForms Make integration free?
Yes. VeriForms is a standard app, so you can use it on the Make Free plan, which includes more than 3,000 standard apps. The Free plan keeps you to 2 active scenarios, a minimum of 15 minutes between 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) lower the interval to 1 minute and count usage in credits each month. This answer covers Make only, not any VeriForms subscription you may need.
02What do you need to connect VeriForms to Make?
A VeriForms account and a Make account. Make lists no specific prerequisite and no dedicated connection guide for VeriForms, so the generic flow applies: add a VeriForms module, click Create a connection, optionally name it, then either authorize Make on the VeriForms page or paste the key the app provides, and click Save. The connection is then shared by every VeriForms module in your scenarios, so you only do this once per account.
03Does the VeriForms trigger react in real time?
No. Watch Submissions is listed as a scheduled trigger, not an instant one, so Make checks VeriForms on the scenario's schedule instead of being notified by the app. A new scenario runs every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans go down to 1 minute. Note that this type comes from the module name, because the VeriForms documentation on Make is incomplete, so confirm the behavior with Run once.
04What if a VeriForms module is missing in Make?
Use Make an API Call. It calls any endpoint of the VeriForms API with the connection you already have, so a missing action does not force you to build a new connection or leave Make. You will need the VeriForms API documentation to know which path to call. Keep in mind that Make itself flags its VeriForms documentation as limited, because there is not enough public information about the app, so testing each module on sample data is the safest habit.
05Should you use Make or n8n for VeriForms?
It depends on the tool your team already works in. On the Make side, VeriForms offers 9 modules, including a scheduled trigger for submissions and a generic API module for everything else. Many apps also have an n8n node, so check whether VeriForms has one before choosing. The honest criterion is coverage: compare the modules each tool lists for VeriForms against the steps your process actually needs, then test the most important one before committing.