Resources · Zapier integration

MirooCRM Zapier integrationAutomate MirooCRM with Zapier.

The MirooCRM Zapier integration gives you 9 triggers and 15 actions, and every one of those triggers is instant. Contacts, customers and customer addresses can start a Zap, or be created, read, updated and deleted by one.

See the 24 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MirooCRM Zapier integration is for

The MirooCRM Zapier integration links your MirooCRM account to the other tools you use, without anyone copying records by hand. A change on a contact, a customer or a customer address in MirooCRM can start an automation, and that automation can also write back into MirooCRM: add, update, read or delete the same three kinds of records.

Three results you can actually build with it. First, a sales log that keeps itself: New Customer starts the Zap, and a row lands in your spreadsheet, so the list of new accounts fills itself without anyone opening the CRM. Second, a clean exit: Delete Customer fires when someone removes a customer, and the Zap tells your team in your chat tool, so nobody keeps calling a record that is gone. Third, a CRM fed from outside: a form or another tool starts the Zap, and Add Contact creates the person in MirooCRM, attached to an existing customer.

Now what Zapier does not do for MirooCRM. There is no search step on this app, so a Zap cannot look up a contact by name or email; the read actions (Get Contact, Get Customer, Get Customer Address) all want an ID you already hold. There are no polling triggers either: all nine report themselves, which is good news on a free plan. And no Zap ever goes back in time. Records that existed before you switched it on stay where they are (moving that backlog is a separate job).

If you are still weighing tools, open our n8n vs Zapier page before you build anything.

Vocabulary

Zapier words you will meet on this page

Seven terms, one line each. Once they are clear, the rest of the page reads fast.

Zap
Your automation 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. Once the Zap is on, Zapier waits for that event and nothing else.
Action
What the Zap does after it starts: the step that creates, updates, sends or deletes something for you.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is a count of those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it everywhere else.
Connection
Your MirooCRM account, linked to Zapier once, then reused by every step of every Zap that touches MirooCRM.
Cost

What a MirooCRM Zap really costs

Zapier bills actions, not triggers. MirooCRM is not a premium app, so it works from the free plan.

  • Trigger fired0 tasks
  • Successful action1 task each
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo, free plan works

A MirooCRM trigger firing costs nothing. Each action that goes through counts one task, and a Zap with three actions eats three times what a one-action Zap does. An action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger, one action. Add a second action, a filter or a search and it becomes a multi-step Zap, which needs a paid plan. The interval grid below is Zapier's for polling triggers; it does not apply to MirooCRM, whose nine triggers are all instant.

Connect

Connect MirooCRM to Zapier in 3 steps

  1. 01

    Open your Zapier apps

    In your Zapier account, go to the Apps page and click + Add connection. Type MirooCRM in the search box of the dialog and pick it from the list. You need a MirooCRM account before you start.

  2. 02

    Sign in to MirooCRM

    Click Add connection. A new tab opens on MirooCRM: sign in there. You also need read or write access on anything you do not own yourself and want the Zap to touch.

  3. 03

    Grant access

    Allow Zapier to reach the account. From then on, the connection is reused by every MirooCRM step you add, in this Zap and in the next ones, without signing in again for each one.

First Zap

Your first MirooCRM Zap: log every new contact

GoalEach new contact in MirooCRM becomes a row in your spreadsheet, and your team gets a heads-up in chat.

  1. 01

    Build the trigger

    Create a Zap, pick MirooCRM as the app that starts it and New Contact as the event. Choose the connection you made earlier.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent contacts of the connected account, so you map fields on a real one. Read what came back before going further.

  3. 03

    Add the spreadsheet step

    Add your spreadsheet app and its action that adds a row. Map each column to a field from the contact, as the trigger test showed it.

  4. 04

    Add the chat step

    Add your chat tool and its message action. Two actions make this a multi-step Zap, so it needs a paid plan; on the free plan, keep only the spreadsheet step.

  5. 05

    Test, then publish

    Test each action once and check the row and the message. Then publish the Zap to switch it on. Only contacts created after that point will start it.

Triggers

MirooCRM triggers: the 9 events that start a Zap

9 events start a Zap when something happens in MirooCRM, and 9 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Delete Contact

Instant trigger

In Zapier“Triggers when a contact is deleted.”

Removing a person from MirooCRM becomes an event your other tools can react to. The Zap starts on the deletion itself, so other lists can be cleaned up instead of keeping a contact that no longer exists in the CRM.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your mailing list or spreadsheet keeps a copy of each contact, and you want that copy flagged or removed when the CRM record goes.
Watch out
once a record is deleted, check at test which details still come through before you map anything to them.
2

Delete Customer

Instant trigger

In Zapier“Triggers when a customer is deleted.”

This one watches the company or account level: a customer removed from MirooCRM starts the Zap. It is the event to hang any end-of-relationship housekeeping on, since a customer is what contacts and addresses hang from.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
another tool keeps its own list of accounts and should know when one leaves the CRM, so nobody keeps working on a customer that was removed.
Watch out
a deletion that happened before the Zap was published will never start it.
3

Delete Customer Address

Instant trigger

In Zapier“Triggers when a customer address is deleted.”

Addresses live on their own in MirooCRM, and this trigger catches the moment one is removed. The customer stays; only one of its addresses disappears, and the Zap starts on that.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a separate address book lives in another tool, and an address deleted in the CRM should not stay in use there.
Watch out
this is not the same event as Delete Customer; a Zap built on one will not start on the other.
4

New Contact

Instant trigger

In Zapier“Triggers when a new contact is created.”

Fires on each new person created in MirooCRM. It is the most natural starting point for a first Zap, because new contacts are what most other tools want to hear about.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
someone is added to the CRM, and you want that person in your newsletter tool or your follow-up spreadsheet without retyping.
Watch out
contacts that already existed before you publish the Zap will not start it; only new ones count.
5

New Customer

Instant trigger

In Zapier“Triggers when a new customer is created.”

Here the Zap starts when a customer record is created, not a person. In MirooCRM the customer is the account that contacts and addresses belong to, so this is the event for anything that happens once per account.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
opening a folder, a project or a billing record for each new account in another tool, so the account exists everywhere without a manual pass.
Watch out
check at test what the trigger brings back before you map it to another tool.
6

New Customers Address

Instant trigger

In Zapier“Triggers when a new customer address is created.”

Each new customer address created in MirooCRM starts the Zap. The event is the address, not the customer it belongs to.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your delivery or invoicing tool needs every new address of an account, not just the first, and you would rather not copy them by hand.
Watch out
the editor shows the name as New Customers Address; search for that exact wording when you pick the event.
7

Update Contact

Instant trigger

In Zapier“Triggers when a contact is updated.”

Any change saved on an existing contact starts the Zap. A corrected name or surname: the edit itself is the event, which keeps copies of that person in other tools from drifting.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your email tool or support desk holds the same people, and you want their details to follow when someone corrects them in the CRM.
Watch out
as with any trigger, a Zap that writes into the place its own trigger watches can set itself off again.
8

Update Customer

Instant trigger

In Zapier“Triggers when a customer is updated.”

Edits on a customer record start this Zap, at account level rather than person level. It is useful wherever another system mirrors your accounts and must stay in step with the CRM.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
someone archives a customer or marks it as treated as client, and your reporting sheet should reflect it without a manual pass.
Watch out
a filter (paid plan) can keep only the changes you care about; check at test which fields come through.
9

Update Customer Address

Instant trigger

In Zapier“Triggers when a customer address is updated.”

Fires when an existing customer address is edited. The address keeps its place on the customer; only its content changes, and the Zap takes that change elsewhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a customer moves offices, the address is corrected in MirooCRM, and your shipping list should carry the new one rather than the old.
Watch out
only edits made after the Zap is published start it; earlier corrections stay where they are.
Actions

MirooCRM actions: what a Zap can do in your CRM

MirooCRM gives you 15 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Contact

Action

In Zapier“Add new contact in Miroo CRM”

Creates a person in MirooCRM from what an earlier step carried. It asks for a Customer ID, a Name and a Surname, all three required.

When to use it
a form or event tool collects people, and each one should land in the CRM under the right account.
Watch out
without a Customer ID from an earlier step, the contact has no account to sit under.
2

Add Customer

Action

In Zapier“Add new customer in Miroo CRM”

Opens a new customer record, the account level of MirooCRM. Among its fields you will find Archive and Treated as client, neither of them required.

When to use it
a deal is won in another tool and the account should exist in the CRM straight after, ready for its contacts.
Watch out
check at test how the two optional fields behave in your account before you map them.
3

Add Customer Address

Action

In Zapier“Add new customer address in Miroo CRM”

Attaches a new address to a customer. Two fields are required: the Customer ID it belongs to and a Typology for the address.

When to use it
a signup form or an order collected an address, and it should sit on the right account in the CRM.
Watch out
Typology is required, and nothing here says what it accepts; check at test what your account takes, and that an earlier step really carries the Customer ID.
4

Delete Contact

Action

In Zapier“Delete a contact from Miroo CRM”

Removes one person from MirooCRM. The Contact ID is required, so the Zap only deletes the contact it was pointed at.

When to use it
someone asks to be erased through another tool, and the CRM should drop them too.
Watch out
map the Contact ID carefully, since this step removes whatever contact it points at.
5

Delete Customer

Action

In Zapier“Delete a customer from Miroo CRM”

Deletes a customer record. Its one required field is the Customer ID of the account to remove.

When to use it
an account is closed in your billing or project tool and should not survive in the CRM.
Watch out
map the Customer ID carefully, since this step removes the account it points at.
6

Delete Customer Address

Action

In Zapier“Delete a customer address from Miroo CRM”

Removes one address from a customer, leaving the customer itself in place. The Customer address ID is required.

When to use it
an address is retired in your delivery tool and should vanish from the account in MirooCRM.
Watch out
map the address ID, not the customer's; the two are separate fields.
7

Get All Contacts

Action

In Zapier“Get all contacts from Miroo CRM”

Reads contacts from MirooCRM without asking for a Contact ID. What comes back, and in what form, is something to read at test, not to guess.

When to use it
a later step needs contacts that no earlier step pointed at by ID.
Watch out
run the test and look at what came back before you map anything from it.
8

Get All Customers

Action

In Zapier“Get all customers from Miroo CRM”

Reads customers from your MirooCRM account with no Customer ID to supply. It has no required field to fill in.

When to use it
a report or export step wants accounts without a single one picked by ID.
Watch out
one successful run is one task; check at test what it returns before building on it.
9

Get All Customer Addresses

Action

In Zapier“Get all customers addresses from Miroo CRM”

Reads customer addresses from MirooCRM without asking for an address ID first.

When to use it
a shipping or mapping tool needs addresses that no earlier step pointed at by ID.
Watch out
look at the test result to see how the addresses come through before mapping any field.
10

Get Contact

Action

In Zapier“Get a contact from Miroo CRM”

Fetches one contact from MirooCRM by its Contact ID, which is required, so later steps can use that person's details.

When to use it
an earlier step knows a contact's ID but not the rest, and the next step needs the full record.
Watch out
this is an action, not a search: it does not look anything up by name, and it counts a task when it succeeds.
11

Get Customer

Action

In Zapier“Get a customer from Miroo CRM”

Reads one customer record by its Customer ID, required, and hands the result to the steps after it.

When to use it
an earlier step holds a Customer ID, and your spreadsheet row needs the account's details next to it.
Watch out
check at test which customer fields come back before mapping them downstream.
12

Get Customer Address

Action

In Zapier“Get a customer address from Miroo CRM”

Pulls a single address by its Customer Address ID, which is required. The address can then feed a delivery or invoicing step.

When to use it
an earlier step carries an address ID only, and the next tool wants the full address.
Watch out
map the Customer Address ID, not the Customer ID; they are separate fields.
13

Update Contact

Action

In Zapier“Update a contact from Miroo CRM”

Edits an existing person in MirooCRM. The Contact ID is required, so the Zap must know which contact it is changing before it gets here.

When to use it
someone corrects their details through another tool, and the CRM record should follow.
Watch out
with no search step on this app, the Contact ID has to come from an earlier step, not from a name.
14

Update Customer

Action

In Zapier“Update a customer from Miroo CRM”

Changes a customer record from the Zap. Customer ID is required; Archived and Treated as client are among the fields you can set.

When to use it
a contract ends in your billing tool and the account should be archived in MirooCRM too.
Watch out
the Customer ID must come from an earlier step, since this app has no search step.
15

Update Customer Address

Action

In Zapier“Update a customer address from Miroo CRM”

Rewrites an existing address on a customer. It needs the Customer address ID of the one to change, and that ID must reach the Zap from an earlier step.

When to use it
your delivery tool learns of a corrected address and the CRM copy should match.
Watch out
the ID identifies the address, not the customer; do not map one for the other.
When it breaks

When a MirooCRM Zap breaks

Zapier attaches no help article to MirooCRM, and no limit specific to the app is documented. What can go wrong is what goes wrong on any Zap.

Three general cases are worth knowing. Read them before you publish, then keep our Zapier troubleshooting page at hand for the day a run fails.

  • The old records never show up

    A Zap only reacts to what happens after you switch it on. Contacts and customers already in MirooCRM are not picked up; moving them is a separate job.

  • The Zap keeps starting itself

    A Zap that writes into the place its own trigger watches can set itself off again and again, and the task count goes with it. Point writes elsewhere.

  • A bulk import goes quiet

    When a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold the batch back.
Need help

Need help automating MirooCRM with Zapier?

A person reads every message.

FAQ

MirooCRM Zapier integration: questions people ask

01Is the MirooCRM Zapier integration free?
Yes, it works on Zapier's free plan, because MirooCRM is not a premium app. The free plan gives 100 tasks a month and lets you build as many Zaps as you like. The catch is the shape of each Zap: two steps only, one trigger and one action. So New Contact feeding a spreadsheet row is fine for free. New Contact feeding a row and then a chat message is a multi-step Zap, and that needs a paid plan. Start with the two-step version and see whether it covers the job.
02How many tasks does a MirooCRM Zap use?
One task per action that succeeds, and nothing for the trigger. A New Customer trigger followed by Add Customer Address costs one task each time a customer is created. Add a Get Customer step before it and the same run costs two. Zapier does not count an action that fails. The read actions, such as Get All Contacts, are actions too, so they cost a task when they run, even if all you wanted was to look at data for the next step.
03Does MirooCRM trigger Zaps in real time?
Yes. All nine MirooCRM triggers are instant: the app tells Zapier the moment a contact, customer or address is created, updated or deleted, and the Zap starts right away. The interval grid of Zapier's plans, which sets how often polling triggers are checked, does not apply to any of them. That is worth knowing on the free plan: a Zap built on MirooCRM does not wait for a timer, and in the editor it shows a lightning bolt.
04What does it take to connect MirooCRM to Zapier?
A MirooCRM account, plus read or write access on anything you do not own yourself and want the Zap to touch. On Zapier, open the Apps page, click + Add connection, pick MirooCRM, then click Add connection, sign in on the tab that opens and grant Zapier access. The connection is then reused by every MirooCRM step. If a Zap will create contacts, make sure the customers they belong to already exist, since Add Contact requires a Customer ID.
05Why can't a Zap find a MirooCRM contact by email?
Because the MirooCRM integration has no search step. The actions that read a record, Get Contact, Get Customer and Get Customer Address, each require the record's ID, not a name or an email. So the ID has to travel through the Zap, from an earlier step that holds it; check at test which IDs a MirooCRM trigger really brings back. If your Zap starts in another tool that only knows an email address, it cannot point at the right MirooCRM contact on its own. Plan the Zap so the ID is available before any update or delete step.
06What if a MirooCRM operation is missing from Zapier?
Check MirooCRM's app page on Zapier, which shows the current list of triggers and actions. If what you are after is not there, the integration does not offer it today. Look at whether one of the existing actions, such as Update Customer, already does the job with its own fields. Otherwise that step stays a manual one in MirooCRM, and the Zap handles the rest around it. Each trigger and action listed there is one you can pick in the editor today.
07Zapier, Make or n8n for MirooCRM?
Decide on criteria, not on a ranking. First, the catalog: on Zapier, MirooCRM offers 9 instant triggers and 15 actions; check whether the other tool lists MirooCRM at all before comparing anything else. Second, how you are billed: Zapier counts one task per successful action, so a Zap with several MirooCRM reads and writes adds up per run. Third, who will maintain it: a tool the team already knows wins on the day something breaks. Since every MirooCRM trigger is instant, the polling interval is not a criterion here.
Same platform

Other docs you might need on this stack.

Browse all integrations