MSP Formbuilder Zapier integrationAutomate MSP Formbuilder with Zapier.
The MSP Formbuilder Zapier integration gives you 1 trigger and no action. New Form Submission picks up each new entry of a form and hands it to the apps you choose. It is a polling trigger that works on the free plan, so timing depends on your plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the MSP Formbuilder Zapier integration does for you
The MSP Formbuilder Zapier integration takes the entries of your MSP Formbuilder forms and passes them to your other apps. MSP Formbuilder is a drag-and-drop builder for contact forms; Zapier watches the form you pick and, for each new submission, runs the steps you set up elsewhere.
Three results people build. A CRM that gets every lead: New Form Submission starts the Zap and your CRM creates a contact from the fields of the entry. A team alert for the entries that matter: a filter checks one field of the entry, and only the matching ones post a message to your team chat. A log of every entry: each submission adds a row to your spreadsheet, so the whole team reads the answers without opening the form tool.
What Zapier does not do here: MSP Formbuilder offers one trigger and nothing else. No action writes into MSP Formbuilder, and no search looks up an older entry. The trigger is a polling one, so Zapier checks for new entries at your plan's interval rather than hearing about them at once. On the free plan that interval is 15 minutes. And entries received before the Zap was switched on never go through it.
Still weighing the tool itself? See our Zapier review, or our n8n vs Zapier comparison.
Zapier words in one minute
Seven words come back all over 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 in an app that starts the Zap, here a new MSP Formbuilder submission. 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 count on your plan is a count of those.
- Polling vs instant
- Zapier checks a polling trigger on a timer; an instant trigger is reported by the app itself. New Form Submission is polling.
- 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 filter or a second action makes one, and it then needs a paid plan.
What an MSP Formbuilder Zap really costs on Zapier
MSP Formbuilder is not reserved for paid plans: it works on Zapier's free plan. You pay in tasks, and only actions use them.
- Free plan100 tasks a month, unlimited two-step Zaps
- MSP Formbuilder on the free planYes, not reserved for paid plans
- Trigger costNone, only successful actions count
- Filter or second actionMulti-step Zap, paid plan
The trigger never costs a task, however often Zapier checks the form. Each action that succeeds in the other app counts on its own; an action that fails is not counted. The free plan gives 100 tasks a month and builds two-step Zaps only, so New Form Submission plus one action fits. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The grid below sets how often Zapier checks a polling trigger, and New Form Submission is one.
Connect your MSP Formbuilder account in three steps
- 01
Open the Apps page
In your Zapier account, open Apps and click + Add connection. A connection is your MSP Formbuilder account linked to Zapier once, then reused by every step that reads from it.
- 02
Pick MSP Formbuilder
Type MSP Formbuilder in the search box of the dialog and select it in the results. Then click Add connection; a new tab opens where MSP Formbuilder asks you to sign in.
- 03
Sign in and grant access
Sign in to MSP Formbuilder in that tab and grant Zapier access to the account. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.
Your first Zap: alert the team about the entries that matter
GoalWhen a new entry arrives on your MSP Formbuilder form and one of its fields meets your rule, post a message to your team chat.
- 01
Create the Zap and pick the trigger
Create a new Zap, choose MSP Formbuilder as the app and
New Form Submissionas the event. Select your connection, then pick your form in Form Id. - 02
Test the trigger on real entries
Run the trigger test. Zapier brings back the three most recent entries of the form, so you pick a real one and see which fields it carries before mapping.
- 03
Add the filter
Add a Filter step from the plus icon and fill the three boxes: the field, the rule, the value. A filter makes the Zap multi-step, so this Zap needs a paid plan.
- 04
Add the message
Add your team chat and its send-message action. Put the answers you want the team to read into the text, mapped from the entry, then test the step and read the result.
- 05
Publish
Click Publish to switch the Zap on. From then on Zapier checks the form at your plan's interval; entries received before publishing are left out.
The MSP Formbuilder trigger: one event that starts a Zap
1 event starts a Zap when something happens in MSP Formbuilder. Zapier checks for them at the interval your plan allows.
New Form Submission
Polling triggerIn Zapier“Triggers when a new MSP Formbuilder submission is received.”
Watches the MSP Formbuilder form you pick in Form Id and starts the Zap for each entry it has not seen before, with the answers ready to map into the next steps.
When an MSP Formbuilder Zap breaks
Zapier attaches no help article to MSP Formbuilder, so the cases below are the general limits of any Zap, read for this app.
Each card names a case and what to check. For anything else, open our Zapier troubleshooting guide.
Older entries never show up
A Zap reacts only to what arrives after it is published. Entries already stored in MSP Formbuilder stay out of reach; moving them is a separate job.A Zap that keeps restarting
A Zap that writes into the place its own trigger watches can set itself off again and again, and burn through tasks. Keep the Zap's output away from the watched form.A big batch held back
When a bulk import or a migration makes the trigger return a huge batch at once, Zapier's flood protection can hold it back rather than run it all.The same entry seen twice
On a polling trigger like this one, Zapier keeps track of what it has already seen, so the same entry does not start the Zap twice.
Need help automating MSP Formbuilder with Zapier?
A person reads every message.
