Formlets Zapier integrationAutomate Formlets with Zapier.
The Formlets Zapier integration gives you 1 trigger, 0 actions and 0 searches. One event, a new form submission, and it reaches Zapier instantly. Everything else happens in the apps you send that answer to, which is where the real setup work sits.
Verified Trustpilot reviews · AI, automation & growth agency
What the Formlets Zapier integration actually does
The Formlets Zapier integration watches one form you choose and passes each new submission to another app, the moment it arrives. Formlets is the starting point only: it cannot receive data from Zapier, so every Zap built with it begins on Formlets and ends somewhere else.
Three results come up again and again, all built on the single New Submission trigger. A sales inbox that fills itself: each contact form lands as a record in your CRM, typed by nobody. A team ping: a booking request posts a message where your staff already talk, so the first reply goes out sooner. A running log: every answer becomes a spreadsheet row, which turns a scattered pile of emails into a table you can sort.
Now the part the app page skips. Zapier does nothing inside Formlets. It does not create a form, edit one, or update an answer, and it cannot look up an older submission either. There are no actions and no searches for this app. If you need to change something in Formlets itself, that stays a manual job.
One more limit is on the form side: the trigger watches one form at a time (you pick it when you set up the step). Three forms means three Zaps, each with its own test.
Comparing tools? The same app has a Formlets Make integration page, and the Make vs Zapier comparison lays out how the two platforms differ in general.
Zapier words, in one minute
Seven terms, each explained once. The rest of the page uses them as is.
- Zap
- The automation you build: one starting event, then one or more steps that run every time that event happens.
- Trigger
- The event that starts the Zap. Here it is a new Formlets submission, and Zapier waits for it once the Zap is on.
- Action
- What the Zap does after it starts: the step that writes a row, sends a message or creates a record in another app.
- Task
- The unit Zapier bills. One action that completes successfully is one task, and your plan counts those.
- Polling vs instant
- A polling trigger is checked on a timer. An instant trigger is reported by the app itself the moment it happens. Formlets is instant.
- Filter
- A step that lets the Zap continue only when what arrived matches a condition you set, and stops it otherwise.
- Connection
- Your Formlets account, linked to Zapier a single time and then reused by every Zap that needs to read from it.
What a Formlets Zap really costs
Formlets is not a premium app, so it works on the free plan. The bill only grows on the other side of the Zap.
- TriggerFree, never counted
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo
The trigger never costs a task. Each submission that reaches Zapier is free; what counts is every action that then succeeds. A Zap with one action uses one task per submission, a Zap with three actions uses three. An action that fails is not counted. The free plan gives you 100 tasks a month and Zaps of two steps only: one trigger, one action. Add a filter or a second action and the Zap becomes a multi-step Zap, which needs a paid plan. The polling grid (15 minutes on Free) does not apply here, because this trigger is instant.
Connect Formlets to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need a Formlets account first, plus access to the forms you want to watch if someone else owns them.
- 02
Pick Formlets
Type Formlets in the search box of the dialog, select it, then click Add connection at the bottom of that same dialog. A new tab opens on the Formlets side for the login.
- 03
Sign in and allow access
Log in to Formlets in that tab and grant Zapier access to the account. The connection is saved once, and every Formlets Zap you build later picks it from a list.
Your first Zap: club memberships into Google Sheets
GoalA cycling club collects membership forms on Formlets and keeps only the youth category in a shared sheet.
- 01
Create the Zap
Start a new Zap in the editor. Choose Formlets as the trigger app and New Submission as the event that starts everything.
- 02
Choose the form
Select your connection, then the membership form in Formlet Name. One Zap watches one form, so pick the exact one new members fill in.
- 03
Test with a real answer
Send one test membership first, then run the test. Zapier brings back up to three recent submissions so you can map from a real one.
- 04
Add the filter
Click the plus icon, pick Filter, and set the rule on the category answer you spotted in the test. Use a text rule for text. This step makes the Zap multi-step.
- 05
Add the sheet row
Add Google Sheets as the action, choose the club roster, and map each column to the matching answer from the test membership.
- 06
Test and publish
Run the action test once, check the new row, then click Publish. From now on each youth membership lands in the roster on its own.
The Formlets trigger
1 event starts a Zap when something happens in Formlets, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Submission
Instant triggerIn Zapier“Triggers when a new submission is created.”
Each time someone completes the form you picked, this trigger hands the full answer to Zapier and the next step can use every field of it. It is the only way into the integration, so every Formlets Zap starts here.
When a Formlets Zap breaks
Zapier links no help article to Formlets and documents no app-specific limit. What breaks comes from Zapier itself.
Four cases cover almost every support question. If yours is not here, the Zapier troubleshooting page goes further.
Old submissions never show up
A Zap only reacts to what happens after you switch it on. Answers collected before that stay in Formlets, and moving them is a separate job.Two forms cannot share one Zap
Formlet Name takes a single form. Pointing a second form at the same Zap is not an option: build another Zap for it and test that one on its own.A burst of answers is held back
When a trigger suddenly returns a huge batch, Zapier's flood protection can hold it back instead of running every Zap at once.The filter never passes
Filter rules are typed. A number rule on a text answer fails every time, so match the rule type to what the test showed.
Need help automating Formlets with Zapier?
A person reads every message.
