- Home
- Resources
- Integrations
- MiniCRM
MiniCRM Zapier integrationAutomate MiniCRM with Zapier.
The MiniCRM Zapier integration gives you 4 triggers, 5 actions and 0 searches. New or updated cards and contacts can start a Zap, and Zapier can create cards and contacts or update them in MiniCRM. Below: what it costs, how to connect it, and the ID trap that breaks updates.
Verified Trustpilot reviews · AI, automation & growth agency
What the MiniCRM Zapier integration does
The MiniCRM Zapier integration links MiniCRM, a CRM that keeps leads, deals and customer data in modules such as Sales or Helpdesk, to Zapier, the tool that chains apps together. A change in MiniCRM can start work in another app, and another app can create or update cards and contacts in MiniCRM, with nobody retyping anything.
Three results people build with it. A Sales card from a form: a form tool starts the Zap, and Create Card opens a card in the module you choose with the contact's name on it. A contact list that stays in step: New Contact starts the Zap, and your email list tool adds the person. A team heads-up on status changes: Updated Card starts the Zap when a card's status or a supported field changes, and your team chat gets a short message.
What Zapier does not do for MiniCRM is the part to read twice. There is no search, so a Zap cannot look up a card or a contact by name. The three update actions need the numeric MiniCRM ID of the card or contact, which has to come from an earlier MiniCRM step. And the four triggers are polling triggers: Zapier checks MiniCRM on a timer, every 15 minutes on the free plan, so nothing reacts immediately when a card changes.
If you are still weighing tools before you build, see our n8n 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, such as New Card in MiniCRM. 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, like Create Contact.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The monthly count on your plan is a count of these.
- Polling trigger
- A trigger Zapier checks on a timer: it asks the app for new items and keeps only those it has not seen. All four MiniCRM triggers work this way.
- Instant trigger
- A trigger the app reports itself, calling Zapier when the event happens, so nothing waits for the next check. MiniCRM has none.
- 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 MiniCRM Zap really costs
Short version: watching MiniCRM is free, and each MiniCRM action that goes through costs one task.
- TriggersNever count as tasks
- Free plan100 tasks a month, unlimited Zaps, two steps each
- Premium appNo, MiniCRM works on the free plan
None of the four triggers costs a task, however often Zapier checks. Each action that succeeds counts as one, so a Zap that creates a card and then posts a message spends two per run, and a failed action is not counted. MiniCRM is not a premium app, so it works on the free plan, where each Zap stops at two steps. A filter or a second action makes it a multi-step Zap, which needs a paid plan. How often Zapier checks MiniCRM depends on your plan:
Connect MiniCRM 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 MiniCRM, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 02
Pick MiniCRM
In the dialog, search MiniCRM by name, pick it, then click Add connection. A new tab opens so you can sign in with the MiniCRM account whose modules the Zap should use.
- 03
Sign in and grant access
Sign in to MiniCRM 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, now serves all four triggers and five actions.
Your first MiniCRM Zap
GoalOpen a card in your Sales module for every new MiniCRM contact, then tell the team in your chat tool.
- 01
Set the trigger
Create a Zap, pick MiniCRM as the app and New Contact as the event that starts it. Choose your MiniCRM connection, or add it from there if you have not yet.
- 02
Test with real contacts
Run the trigger test. Zapier brings back the three most recent contacts of the account, so you map from a real one instead of guessing what comes through.
- 03
Add Create Card
Add MiniCRM as the action app and choose Create Card. Pick the module in Module and map Contact Name from the trigger, both required, then test the step.
- 04
Add the chat message
Add the chat action and write a short message built from the contact. Two actions make this a multi-step Zap, so it needs a paid plan, and each contact costs two tasks.
- 05
Publish
Click Publish to switch the Zap on. Zapier then checks MiniCRM on your plan's interval. For a guided start on Zaps like this one, see our Zapier training.
The MiniCRM triggers
4 events start a Zap when something happens in MiniCRM. Zapier checks for them at the interval your plan allows.
New Card
Polling triggerIn Zapier“Triggers when a new card (e.g. customer, invoice or project) is created in the selected module.”
A card created in the MiniCRM module you pick, a customer, an invoice or a project for instance, reaches Zapier through this trigger and starts the Zap.
New Contact
Polling triggerIn Zapier“Triggers when a new contact is created in MiniCRM.”
Every contact added to MiniCRM gets picked up at the next check and handed to the rest of the Zap, with no module to choose.
Updated Card
Polling triggerIn Zapier“Triggers when a card in the selected module is updated, including status changes and supported card field changes.”
When a card changes in the module you pick, including a status change or a supported field change, this trigger starts the Zap with the card as it now stands.
Updated Contact
Polling triggerIn Zapier“Triggers when a contact is updated.”
Editing a contact in MiniCRM lets Zapier pass the new version on at the next check, which keeps a copy of your contacts elsewhere in line.
The MiniCRM actions
MiniCRM gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Card
ActionIn Zapier“Creates a new card in the selected Module”
Opens a new card in the MiniCRM module you choose, filled from what the trigger brought.
Create Contact
ActionIn Zapier“Creates a new contact”
Adds a person or a company to your MiniCRM contacts without anyone typing them in.
Update Card Status
ActionIn Zapier“Updates a card's status in MiniCRM”
Moves an existing MiniCRM card to another status, so a stage change can come from outside MiniCRM.
Update Card Field
ActionIn Zapier“Updates a single data field in the selected card.”
Changes one data field on a chosen card, leaving the rest of the card as it is.
Update Contact
ActionIn Zapier“Updates a contact in MiniCRM”
Edits an existing MiniCRM contact with fresh details from another app.
When a MiniCRM Zap breaks
MiniCRM brings no documented error or limit of its own on Zapier.
What goes wrong comes from how Zapier works and from the IDs the update actions expect. Six cases to know before you publish. If a Zap still misbehaves, see our Zapier troubleshooting guide.
Nothing from before the Zap
A Zap only reacts to what happens after you switch it on. Cards and contacts already in MiniCRM are not picked up, and moving them is a separate job.An ID where you expected a name
Card and Contact ID want numeric MiniCRM IDs, not names. Map the ID from an earlier MiniCRM step of the same Zap and check at test which value carries it.No module to pick
Module is required on New Card, Updated Card and three actions. If the connected account lacks the module you need, there is nothing to choose.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 MiniCRM suddenly returns a huge batch, after a bulk import or a migration for instance, Zapier's flood protection can hold the Zap back.The same item never runs twice
On a polling trigger, Zapier keeps track of what it has already seen, so the same item does not start the Zap twice, however many checks go by.
Need help automating MiniCRM with Zapier?
A person reads every message.



