Resources · Make integration

Formify Make integrationAutomate Formify with Make.

Can a finished Formify document start the next step on its own? The Formify Make integration gives you 12 modules: 2 scheduled triggers, 8 actions and 2 searches. This page shows what each one is for, how to link your account and how to build a first scenario.

Try the Formify integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Formify Make integration let you automate?

The Formify Make integration links your Formify account to Make so that documents, their field values and their status can flow into other apps without code. You build a scenario, the automation itself, from modules: small bricks that each watch, read or act on one thing in Formify.

Pass the answers on once a document is finished. Watch Completed Documents picks up documents that reach the end of their flow, and Get Document Field Values reads what was filled in. A sales team can then push those values into its CRM or a spreadsheet without retyping them.

Send a file out for signature from another tool. Upload a File puts the file into Formify, then Send a Document to Sign starts the signing step. Handy for an HR team that prepares contracts elsewhere and wants the sending to happen by itself.

Keep track of what moves in your account. Watch Events and List Documents give a scenario a view of activity, which an office manager can turn into a simple log or an alert.

Be aware of one real limit. Make says its documentation for Formify is limited because there is not enough public information about the app, so no module comes with an official description. The notes below describe each module from its name, and the Run once test is the way to see what it actually returns. If you are weighing tools, the n8n vs Make comparison lays out the differences, and the Make training covers the editor from the ground up. When a scenario stops, Make troubleshooting is the place to start.

Connect

How do you connect your Formify account to Make?

  1. 01

    Add a Formify module

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

  2. 02

    Name the connection

    This part is optional but useful. Give the connection a name you will recognize, such as the workspace or the team it belongs to, so you pick the right account when you run more than one.

  3. 03

    Authorize Make and save

    Depending on what Formify offers, either approve Make on the Formify page that opens, or paste the key Formify gives you. Then click Save, and the module can read your account.

First scenario

Your first scenario with Formify in Make

GoalWhen a document is completed in Formify, Make reads the values that were filled in so the next module can use them.

  1. 01

    Create the scenario

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

  2. 02

    Add the trigger and connect

    Search for Formify, choose Watch Completed Documents and click Create a connection, or pick the connection you made earlier. Then fill in the module settings Make asks for.

  3. 03

    Read the filled-in values

    Click the + on the right of the trigger and add Get Document Field Values. Map the document from the trigger's bundle, the item passed along from the previous module, instead of typing it.

  4. 04

    Test with Run once

    Finish a test document in Formify, then click Run once. Open the bubble above each module to read the bundles it received and check the values look right.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default for a new scenario. Then switch the scenario on so it keeps running without you.

Triggers

What can start a Formify scenario?

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

Formify1Watch Completed Documents

Watch Completed Documents

triggerIn the docs only

This trigger hands your scenario each Formify document that has been completed, so the work that follows a finished form or contract can start without anyone checking the dashboard. Its name is the only guide, since Make gives it no description.

How it fires
scheduled. Make checks Formify on the scenario's schedule, every 15 minutes by default, and never more often than every 15 minutes on the Free plan.
When to use it
as the starting point whenever the finished document, not the draft, is what the rest of the process needs.
Watch out
a document finished just after a check waits for the next one, so plan for that delay.
Formify2Watch Events

Watch Events

triggerIn the docs only

Watch Events gives you a wider net than the completed-documents trigger: it picks up activity in your Formify account as it builds up. Make does not list which events it covers, so treat it as something to explore before you build on it.

How it fires
scheduled. Make checks the app on the scenario's schedule, and paid plans can shorten the interval to 1 minute.
When to use it
for a log or an alert that should react to more than finished documents.
Watch out
click Run once and read the bundles before adding filters, because the event types are not documented.
Modules

What can Make do in Formify?

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

Formify1

Get Account Settings

ActionIn the docs only

Pulls the settings of the connected Formify account into your scenario, which helps you confirm Make is talking to the account you expect. Make documents none of the returned values, so read them in a test first.

When to use it
at the top of a scenario shared by several teams, to check which account a connection points to.
Formify2

Get Document Details

ActionIn the docs only

Returns information about one document you already know, the kind of summary you would read before deciding what to do with it. It works on one item, where List Documents returns many.

When to use it
right after a trigger, when the next module needs more about the document than the trigger supplied.
Watch out
map the document from an earlier bundle rather than typing it by hand.
Formify3

Get Document Field Values

ActionIn the docs only

Gives you what people actually wrote in a document, ready to send into a CRM, a sheet or an email. This is usually the module that turns a filled form into data another app can use.

When to use it
after Watch Completed Documents, when the answers matter more than the file itself.
Watch out
compare it with Get Document Fields, which by its name describes the fields rather than their content.
Formify4

Get Document Fields

ActionIn the docs only

Shows how a document is built: the fields it contains, as opposed to the answers inside them. That map helps you plan your mapping before real values start flowing through the scenario.

When to use it
while designing a scenario, to see which fields a template holds before wiring the next app.
Watch out
for the filled-in content, reach for Get Document Field Values instead.
Formify5

List Documents

SearchIn the docs only

Brings back a set of documents from your Formify account in one go. As a search module, it can return zero, one or several bundles, and each bundle then runs through the rest of the scenario separately.

When to use it
to review or sort existing documents instead of waiting for new ones to arrive.
Watch out
every bundle it returns costs operations in the following modules, so narrow the search where Make lets you.
Formify6

Make an API Call

ActionIn the docs only

Opens the whole Formify API to your scenario, reusing the connection you already set up. It covers what the ten other ready-made modules leave out, without a second login.

When to use it
when a task has no dedicated module, or when the named modules do not return the detail you need.
Watch out
you write the request yourself, so you need Formify's own API documentation next to the editor.
Formify7

Merge a PDF-file

ActionIn the docs only

Combines PDF content into a single file so the person receiving it opens one document instead of several. Make gives no detail on how the merge works, so check the output on a test before relying on it.

When to use it
when a contract and its annexes should leave as one file, just before sending or archiving.
Watch out
the Free plan caps files at 5 MB, which a merged PDF can reach.
Formify8

Search User Info

SearchIn the docs only

Judging by its name, it looks up users in your Formify account and returns what it finds, which saves you from keeping a separate list of who is who. A search can find nobody, one person or several.

When to use it
before assigning or notifying someone, to fetch the right person from Formify rather than hard-coding a name.
Watch out
add a filter after it so an empty result does not break the next step.
Formify9

Send a Document to Sign

ActionIn the docs only

Starts the signing step for a document straight from the scenario, so nobody has to open Formify to press send. It fits best at the end of a flow where the file has already been prepared.

When to use it
once a contract is uploaded and checked, to put it in front of the signer.
Watch out
test it on your own address first, since the whole point of the module is to ask someone for a signature.
Formify10

Upload a File

ActionIn the docs only

Places a file coming from another app into your Formify account, ready for the modules that follow. Most flows that begin outside Formify need this step before anything else can happen there.

When to use it
when a contract is generated in another tool and has to reach Formify before being sent for signature.
Watch out
map the file from the previous module's bundle, and remember the 5 MB file cap on the Free plan.
Need help

Need help automating Formify with Make?

A person reads every message.

FAQ

Questions about Formify and Make

01Is the Formify Make integration free?
Yes, Formify is a standard app in Make, so its modules are available from the Free plan. That plan has 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) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Make counts usage in operations, one per module run on one bundle. This page says nothing about the price of Formify itself.
02What do you need to connect Formify to Make?
A Formify account and a Make account are enough to begin. Make's documentation lists no specific prerequisite for Formify and does not detail its connection screen. The generic steps apply: add a Formify module, click Create a connection, optionally name it, then either authorize Make on the Formify page or paste the key Formify provides, and click Save. The same connection then serves every Formify module in your scenarios, so this setup happens only once per account.
03Do Formify triggers in Make fire instantly?
No. Both Formify triggers, Watch Completed Documents and Watch Events, are scheduled triggers: Make checks Formify on the scenario's schedule rather than being alerted by the app. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval, while paid plans can go down to 1 minute. A document completed just after a check is picked up at the next one, so plan the steps that follow with that gap in mind.
04What if a Formify module you need is missing in Make?
Use Make an API Call. It is part of the Formify app in Make and lets a scenario call any endpoint of the Formify API with the connection you already have. Keep in mind that Make describes its Formify documentation as limited, because too little public information exists about the app, so none of the 12 modules comes with an official description. Test each module with Run once and read the bundles it returns, and keep Formify's own API reference close when you build a custom call.
05Should you use Make or n8n with Formify?
It depends on the tool your other automations already run on, since there is no universal winner between the two. On the Make side, Formify brings 12 modules, including 2 scheduled triggers and a Make an API Call module for anything else. Apps listed in Make often have an n8n node as well, but check the n8n side for Formify before choosing it. A useful test is to build the same small flow in both and keep the one your team maintains most easily.
Same platform

Other docs you might need on this stack.

Browse all integrations