- Home
- Resources
- Integrations
- FormCan
FormCan Zapier integrationAutomate FormCan with Zapier.
FormCan Zapier integration: 1 trigger, 1 action, 0 searches. Zapier can start a Zap the moment someone sends one of your FormCan forms, or push answers into a form from another app. Below: what it costs, how to connect it, and where it breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the FormCan Zapier integration actually does
It links your FormCan account to the rest of your tools without code. Each time a form is sent, Zapier hears about it right away and passes the answers to the next app. It also works the other way: another app can fill in a FormCan form for you. Two operations, nothing hidden behind them.
Three results people build with it. First, an inbox that sorts itself: New Submission fires, and the answers go out as an email or a message to the right person. Second, a log you never type by hand: the same trigger writes each submission into a sheet or a CRM, one line per form sent. Third, one intake point for several sources: Submit Form takes data arriving from another app and files it as a FormCan submission, so all requests end up in the same place.
Now the honest part. The editor offers a single trigger, so a Zap can react to a new submission and to nothing else. There is no search step either: a Zap cannot look up a submission that already exists. And nothing sent before the Zap was switched on gets picked up later (moving that backlog is a separate job).
Weighing other tools? The FormCan Make integration has its own page, and the Make vs Zapier comparison sets the two side by side.
Zapier words in one minute
Eight terms come back on every line of this page. Here they are in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event that starts the Zap. Once the Zap is on, Zapier waits for it; here, a FormCan form being sent.
- Action
- The step that does the work once the Zap runs. On the FormCan side there is exactly one: Submit Form, which files a submission.
- Task
- What Zapier counts against your plan: one action that went through. A form sent to a one-action Zap means one task.
- Polling vs instant
- A polling trigger is checked on a timer. An instant trigger is reported by the app itself, the moment the event happens.
- Filter
- A checkpoint between steps: the Zap goes on only if the answers meet your rule, such as one course picked over another.
- Connection
- Your FormCan account linked to Zapier once, then reused by every step that talks to FormCan in any of your Zaps.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
What a FormCan Zap really costs
FormCan is not a premium app, so it runs on the free plan. The trigger never costs a task, and neither does Zapier listening for new submissions.
- TriggerFree, never counted
- Each successful action1 task
- Free plan100 tasks a month, 2-step Zaps
- Premium appNo
Only a completed action is billed, one task each, and a failed action is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap: add a filter or a second action and you need a paid plan. The interval grid below concerns polling triggers; New Submission is instant, so it ignores it. One more thing: a Zap with three actions eats three times more than a one-action Zap, so count your actions before adding them.
Connect FormCan to Zapier in three steps
- 01
Open your connections
In your Zapier account, go to the Apps page and click + Add connection. A dialog opens with a search box; type FormCan and pick it from the list that appears.
- 02
Sign in to FormCan
Click Add connection. A new tab asks you to log in to FormCan with the account that owns your forms. Use that one, not a colleague's, or your forms will be missing later.
- 03
Grant access
Approve the access Zapier asks for. The connection is saved once and every FormCan step of every Zap reuses it. If a form belongs to someone else, you need read or write rights on it first.
Your first Zap: route trial-lesson requests to the right teacher
GoalA language school takes trial-lesson requests through a FormCan form. Only the Business English requests should reach the Business English teacher by email.
- 01
Pick the trigger
Create a Zap, choose FormCan as the app and New Submission as the event. Select your FormCan connection, then pick the trial-lesson form in the Form field.
- 02
Test with a real request
Send the form once yourself, then run the test. Zapier brings back the three most recent submissions so you can pick a real one and see which answer holds the course name.
- 03
Add the filter
Click the plus icon and add a Filter. Point it at the course answer you spotted in the test, choose a text rule, and type Business English as the value.
- 04
Add the email
Add Gmail and its Send Email action. Map the student's answers from the submission into the subject and body, and set the teacher's address as recipient.
- 05
Test, then publish
Run each step once and read what came back. When the email looks right, click Publish. Keep in mind the filter makes this a multi-step Zap, so it needs a paid plan.
The FormCan trigger
1 event starts a Zap when something happens in FormCan, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Submission
Instant triggerIn Zapier“Triggers when a form is submitted.”
Starts your Zap each time somebody sends the FormCan form you picked, and hands every answer of that submission to the next step. One form per trigger: to watch three forms, you build three Zaps, each set on its own form.
The FormCan action
FormCan gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Submit Form
ActionIn Zapier“Submit a Form.”
Sends a submission to the FormCan form you choose, built from data that an earlier step carried. Nobody has to retype a request that arrived somewhere else.
When a FormCan Zap breaks
Zapier attaches no help article to FormCan, so the traps below are the general ones, applied to this app.
Most failures come from the setup, not from FormCan. Check these four first; for the rest, the Zapier troubleshooting page is the next stop.
Old submissions never show up
A Zap only reacts to forms sent after it is switched on. Submissions already sitting in FormCan stay where they are; moving them is a separate job.The Zap keeps firing on its own
Submit Form pointed at the form New Submission watches creates a loop: each new submission fires the Zap, which sends another one, and the task count drains fast.A bulk import gets held back
When a huge batch arrives at once, after an import or a migration, Zapier's flood protection can hold those runs back instead of letting them all through.The filter stops the free Zap
On the free plan a Zap has two steps: one trigger, one action. Adding a filter between them makes it multi-step, which only a paid plan accepts.
Need help automating FormCan with Zapier?
A person reads every message.



