FormCan Make integrationAutomate FormCan with Make.
Can Make read and fill your FormCan forms without a line of code? The FormCan Make integration gives you 6 action modules, from listing forms to submitting entries. This guide is for anyone who owns the forms and wants them talking to other tools, and it walks you through the connection and a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the FormCan Make integration do for you?
The FormCan Make integration links your FormCan account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick that does one job. FormCan brings six of those bricks, all of them actions, so your forms can feed other apps or receive data from them.
Keep a clear map of your forms. Get Forms returns the forms of your account and Get Form Fields reads what each one asks. That pair is the natural starting point before you connect anything else, and it is the first scenario on this page.
Push entries from another tool. Submit Form sends data into a FormCan form. The data can come from any app Make connects to, such as a sheet row or a CRM record, so a form stays the single entry point even when the information starts elsewhere.
Collect the files people attach. Download File retrieves a file so a following module can store or forward it. Submission Watch and Make API Call round out the set; their notes below say what their names suggest and what still needs a test.
Be aware of one limit: Make itself says it cannot publish full documentation for FormCan yet, because too little public information exists about the app. No module here starts a scenario on its own, so the start comes from Make's schedule or from another app. If you need a hand choosing, our Make review covers the editor, Make pricing explains how operations are counted, and the n8n vs Make comparison helps if the app also sits in n8n.
How do you connect FormCan to Make?
- 01
Add a FormCan module
Open your scenario, click the + and search for FormCan. Pick any of its modules, for example Get Forms, then click Create a connection. A connection is your FormCan account linked to Make once and reused by every FormCan module.
- 02
Name it and authorize
Give the connection a name if you like, which helps when you manage several accounts. Then authorize Make on the FormCan page that opens, or paste the key FormCan gives you, depending on what the window asks for.
- 03
Save and check
Click Save. Back in the module, Make can now list what it reads from your account. If Get Forms shows your forms after a test, the connection works and every other FormCan module can use it.
Build your first scenario with FormCan
GoalWhen the scenario runs, Make lists your FormCan forms and reads the fields of each one, so you know what every form expects.
- 01
Create the scenario
From the Scenarios page, create a new scenario and click the + in the middle of the editor. Search for FormCan and choose Get Forms as the first module.
- 02
Connect your account
Click Create a connection, authorize Make and save. Once the connection exists, fill the module fields; Make lists what it can read from your FormCan account.
- 03
Add Get Form Fields
Click the + on the right of Get Forms and add Get Form Fields. Map the form coming from the previous module, so each bundle (one form passing from one module to the next) gets its fields read.
- 04
Test with Run once
Click Run once. Make executes the scenario one time and shows the bundles each module received. Open them to see your forms and the fields each one holds.
- 05
Schedule and switch on
Set the schedule on the first module; a new scenario runs every 15 minutes by default. Switch the scenario on. Each module run on one bundle counts as one operation on your plan.
What each FormCan module does
FormCan gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Download File
ActionIn the docs onlyGoing by its name, Download File gets a file out of FormCan so the next module can store it, attach it to an email or pass it along. You end up with the file itself in your scenario, ready to use.
Get Form Fields
ActionIn the docs onlyAs its name says, Get Form Fields should show you what a form asks, field by field, so you can map answers correctly in later modules instead of guessing. It is the reference you look at before you build anything that writes to a form.
Get Forms
ActionIn the docs onlyGet Forms gives you the forms of your FormCan account as data inside Make, which is the easiest way to confirm the connection and pick the form you will work with. Other modules can then use what it returns.
Make API Call
ActionIn the docs onlyMake API Call is listed among the FormCan modules, and its name points to a free request to the FormCan API for what the other modules do not cover. Make publishes no description for it, so treat that reading as a lead, not a promise.
Submission Watch
ActionIn the docs onlySubmission Watch is typed as an action in Make, not as a trigger, so it does not start a scenario by itself. Its name suggests it deals with form submissions; run it once to see exactly what comes back before you rely on it.
Submit Form
ActionIn the docs onlyIts name says it: Submit Form sends an entry into one of your FormCan forms from data coming out of another module. The answer lands in FormCan as if someone had filled the form, which keeps all entries in one place.
Need help automating FormCan with Make?
A person reads every message.
