- Home
- Resources
- Integrations
- Minform
Minform Zapier integrationAutomate Minform with Zapier.
The Minform Zapier integration gives you 1 trigger, 0 actions and 0 searches. In plain terms: each answer to one of your Minform forms can start a Zap straight away, and the rest of the work happens in your other apps. Below: what it costs, how to connect it, and where it breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the Minform Zapier integration does
The Minform Zapier integration connects Minform, a minimal builder for forms and calculators, to Zapier, the tool that chains apps together. Each time someone sends one of your forms, the answer can travel into another app with nobody copying it. Minform has one role here: it starts the automation, and it receives nothing back.
Three results people build from the single New Submission trigger. A spreadsheet row per answer: the trigger hands each submission to Zapier, and a spreadsheet action files it in a sheet your team already reads. A message in your team chat: same start, but the action posts a short note so someone looks at the answer. A contact in your CRM: the submission feeds an action of the CRM you use, so nobody retypes what the person filled in.
What Zapier does not do for Minform matters too. There is no action and no search: a Zap cannot create a form, edit an answer or look up an earlier submission in Minform. Data only ever leaves Minform. The good news is speed. New Submission is an instant trigger, reported by Minform itself, so the plan you pick does not slow it down: on this trigger, the free plan reacts as fast as the paid ones.
If you are still comparing tools before you build, see our Make vs Zapier comparison.
Zapier vocabulary in one minute
Eight words you will meet in the editor, 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. Here it is New Submission in Minform; once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, in another app here.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The monthly count on your plan is a count of these.
- Instant trigger
- A trigger the app reports itself: it calls Zapier when the event happens, so nothing waits for a check. New Submission works this way.
- Polling trigger
- A trigger Zapier checks on a timer, asking the app for new items and keeping only the unseen ones. Minform has none on Zapier.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it then needs a paid plan.
What a Minform Zap really costs
Short version: receiving the answers is free, and you only pay in tasks for what the Zap does with them.
- TriggerNever counts as a task
- Free plan100 tasks a month, unlimited Zaps, two steps each
- Premium appNo, Minform works on the free plan
The New Submission trigger never costs a task. Each action that succeeds counts as one, so an answer sent to two apps costs two, and a failed action is not counted. Minform is not a premium app, so it runs on the free plan, where each Zap stops at two steps. A filter or a search turns it into a multi-step Zap, which needs a paid plan. Zapier's check interval grid is below for reference: it does not apply to New Submission, which is instant on every plan.
Connect Minform to Zapier in three steps
- 01
Open your connections
Go to the Apps page of your Zapier account and click + Add connection. What you need first: an account on Minform, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 02
Pick Minform
In the dialog, search Minform by name, pick it, then click Add connection. A new tab opens so you can sign in with the Minform account that holds your forms.
- 03
Sign in and grant access
Sign in to Minform in that tab and grant Zapier access to the account. The connection, your account linked once and then reused by every step that needs it, is ready for every Zap you build.
Your first Minform Zap
GoalKeep only the Minform answers that meet a condition you set, and add each one as a row in a shared spreadsheet.
- 01
Set the trigger
Create a Zap, pick Minform as the app and New Submission as the event that starts it. Choose your Minform connection, then the form to watch in Select a form.
- 02
Test with real answers
Run the trigger test. Zapier brings back the three most recent submissions of that form, so you map from a real answer instead of guessing what comes through.
- 03
Add the filter
Add a Filter step from the plus icon and fill its three boxes: the field to look at, the rule, and the value. A filter makes this a multi-step Zap, so it needs a paid plan.
- 04
Map the row
Add the spreadsheet action and map the answer from the trigger into its columns. Test that step once and read what came back. For a guided start, see our Zapier training.
- 05
Publish
Click Publish to switch the Zap on. From then on, each new answer to that form reaches Zapier right away, whatever your plan, and goes through the filter.
The Minform trigger
1 event starts a Zap when something happens in Minform, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Submission
Instant triggerIn Zapier“Triggers when a new form submission is received.”
Each answer sent through the Minform form you pick reaches Zapier with this trigger, so the rest of the Zap can store it, share it or route it to the right person.
When a Minform Zap breaks
Minform brings no documented error or limit of its own on Zapier.
What goes wrong comes from how Zapier itself works. Three cases to know before you publish. If a Zap still misbehaves after that, see our Zapier troubleshooting guide.
Answers from before the Zap are ignored
A Zap only reacts to what happens after you switch it on. Submissions already stored in Minform are not picked up, and moving that backlog is a separate job.A Zap that sets itself off
As a general precaution: a Zap that writes into the very place its own trigger watches can set itself off again and again, and burn through your task count fast.A huge batch gets held back
If a trigger suddenly sends a huge batch at once, after a bulk import or a migration for instance, Zapier's flood protection can hold the Zap back.
Need help automating Minform with Zapier?
A person reads every message.



