Micole Zapier integrationAutomate Micole with Zapier.
Micole Zapier integration: 2 triggers, 0 actions and 0 searches. Micole tells Zapier when a lead is created or updated, and the rest of the Zap happens in your other apps. Here is what both triggers do, what a Zap costs and what can break.
Verified Trustpilot reviews · AI, automation & growth agency
What the Micole Zapier integration does for you
The integration links Micole, a platform that puts schools in touch with interested families, to the other apps you use through Zapier. Micole can start a Zap in two cases: a new lead, or an update to an existing lead. It cannot be written to from a Zap, so every action lands in another app.
A new lead your team sees. New Lead starts a Zap that posts a message in your team chat, so nobody has to keep Micole open to spot a new family's interest.
A lead list you do not retype. The same trigger can add a row to your spreadsheet or a contact to your CRM, with whatever the lead carries.
A record that follows changes. Lead Updated starts a Zap when an existing lead changes, which can update the matching contact elsewhere or warn the person who follows it.
The detail that matters most on a free plan: both Micole triggers are instant. Micole tells Zapier itself, so the plan's polling interval never applies to them.
Micole is not a premium app: a Zap of one Micole trigger and one action runs on the free plan, and only that action counts as a task.
What Zapier does not do here: Micole has no action and no search, so a Zap cannot create, change or look up a lead in Micole. To weigh Zapier against other tools, open our n8n vs Zapier comparison or see our Zapier review.
Zapier words, in plain English
Eight terms carry this page. One line each.
- Zap
- Your automation on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event that starts the Zap, such as a new lead in Micole. Once the Zap is switched on, Zapier waits for it.
- Action
- What the Zap does once started: the step that writes, sends or moves something. Here it always lives in another app.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan counts those.
- Polling trigger
- A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. Micole has none of these.
- Instant trigger
- A trigger the app reports itself: it calls Zapier the moment the event happens. Both Micole triggers are instant.
- 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 a Micole Zap really costs
The Micole trigger never costs a task. Only the actions in your other apps are billed: each one that succeeds counts one task, and one that fails costs nothing.
- Micole triggersNever counted
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Trigger type2 instant, interval not applied
Micole is not a premium app, so it works on the free plan: 100 tasks a month and unlimited Zaps, each limited to one trigger and one action. New Lead followed by a message in your team chat fits exactly. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. A few apps and actions take more than one task when they complete. The grid below is Zapier's polling interval per plan; it does not apply to the Micole triggers, which are both instant.
Connect Micole to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, open the Apps page and click + Add connection. A connection is your Micole account linked once, then reused by every Zap that starts from Micole.
- 02
Pick Micole
Search for Micole in the dialog, pick it and click Add connection. 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.
- 03
Sign in and grant access
Sign in to Micole in the tab that opens, then grant Zapier access to the account. Back in the editor, that connection is the one you pick on New Lead or Lead Updated.
Your first Zap: tell the team about the leads that matter
GoalEach new Micole lead starts the Zap, a filter keeps only the ones that meet your rule, and your team chat gets a message.
- 01
Set the trigger
Create a new Zap, pick Micole as the app that starts it and New Lead as the event, then choose the Micole connection you added above.
- 02
Test it on a real lead
Run the trigger test. Zapier brings back the three most recent items of the connected account, so you map the next steps on a real lead. Read what came back before going further.
- 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. Pick a text rule for text. The filter makes the Zap multi-step, so it needs a paid plan.
- 04
Add the message
Add your team chat with its send-message action and drop in the lead details the trigger brought. Each message sent counts one task.
- 05
Test, then publish
Test the action once and read what came back. Then click Publish to switch the Zap on. For guided practice, see our Zapier training.
The Micole triggers
2 events start a Zap when something happens in Micole, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.
Lead Updated
Instant triggerIn Zapier“Triggers when a lead is updated.”
Fires when an existing lead changes in Micole and hands the updated lead to your Zap. It is the way to keep another app in step after the first contact, rather than copying a lead once and letting it go stale.
New Lead
Instant triggerIn Zapier“Triggers when a new lead is created.”
Starts a Zap each time a new lead is created in Micole, carrying that lead into the next steps. It is the natural first Zap with this app: the moment a family shows interest is the moment your team wants to know.
When a Micole Zap breaks
Zapier links no help article to Micole, so the cases below are Zapier's general limits. They apply to every Zap that starts in Micole.
These are the general limits worth knowing before you switch the Zap on. When a run fails and the reason is not obvious, see our Zapier troubleshooting guide.
Earlier leads are not sent
A Zap reacts only to what happens after you switch it on. Leads already in Micole never start it; moving that backlog is a separate job.A Zap that sets itself off
A general precaution: a Zap that writes into the place its own trigger watches can start itself again and again and burn through your tasks. Keep the output elsewhere.A sudden batch is held back
After a bulk import or a migration, a trigger that returns a huge batch at once can be held back by Zapier's flood protection.
Need help automating Micole with Zapier?
A person reads every message.



