MiniCRM Zapier Integration

With the Zapier integration, you can connect MiniCRM with 8,000+ applications — no custom development required.

Zapier helps you automate repetitive work between MiniCRM and the other tools you already use. For example, you can send new MiniCRM leads to a spreadsheet, notify your team in Slack when a deal changes, or create new opportunities in MiniCRM from form submissions, webshop orders, or bookings.

Requirements

To use the integration, you need:

  • REST API / XML add-on active in your MiniCRM subscription
  • A MiniCRM API key
  • A Zapier account

How the integration works

Zapier automations can run in two directions:

From MiniCRM → another app
When something happens in MiniCRM, Zapier can send that data to another app.

Examples:

  • send new contacts to Google Sheets
  • notify your team in Slack about new opportunities
  • create follow-up tasks in Trello or Asana
  • add leads to your email marketing tool

From another app → MiniCRM
When something happens in another app, Zapier can create or update data in MiniCRM.

Examples:

  • create a contact from a form submission
  • create a new opportunity from a webshop order or booking
  • update contact details from another system
  • keep your customer data aligned across tools

Available MiniCRM triggers

Use these triggers when something happens in MiniCRM and you want another app to respond.

Contact created

This trigger runs when a new contact is created in MiniCRM.

Typical use cases:

  • add new contacts to Mailchimp or another email platform
  • log new leads in Google Sheets
  • notify your team in Slack
  • send new contact data to another internal system

Contact updated

This trigger runs when an existing contact is updated in MiniCRM.

Typical use cases:

  • keep customer records in sync across systems
  • update a spreadsheet or dashboard automatically
  • notify a team when key contact details change
  • trigger follow-up workflows in connected tools

Card created

This trigger runs when a new card (opportunity) is created in MiniCRM.

Typical use cases:

  • notify a sales rep in Slack when a new lead or opportunity comes in
  • create a task in Asana, Trello, or ClickUp
  • send opportunity data to a reporting tool
  • start an onboarding or follow-up workflow in another app

Card updated

This trigger runs when an existing card is updated in MiniCRM.

Typical use cases:

  • notify the team when a deal changes stage
  • update a dashboard or spreadsheet
  • trigger the next step in a project workflow
  • inform another app when ownership or status changes

Sending data into MiniCRM with Zapier

Use these workflows when something happens in another app and you want Zapier to create or update data in MiniCRM automatically.

For example, when a customer fills in a form, sends an email, places an order, books a call, or is added to a spreadsheet, Zapier can pass that information into MiniCRM without manual data entry.

Available MiniCRM actions

Create Contact

Use this action when a new person or company should be added to MiniCRM.

Typical use cases:

  • create a contact from a website form
  • create contacts from incoming emails

Update Contact

Use this action when an existing contact in MiniCRM should be updated.

Typical use cases:

  • update phone numbers or email addresses from another platform
  • keep contact records in sync with another system
  • enrich existing contact data automatically

Create Card

Use this action when a new sales opportunity or process item should be created in MiniCRM.

When a Card (Opportunity) is created through Zapier, the relevant contact is also created in MiniCRM.

Typical use cases:

  • create a new opportunity from a quote request
  • create a card from a booking or consultation request
  • create a card from a webshop order
  • import new leads from marketing tools
  • create a card from a support or service request
  • add leads from Google Sheets

Update Card

Use this action when an existing card in MiniCRM should be updated.

Typical use cases:

  • update an opportunity after payment
  • move a card forward in the pipeline when another tool changes status
  • reflect external workflow progress inside MiniCRM

Common automation examples

The table below shows common events in other apps and the MiniCRM action that is usually the best fit.

When this happens in another app Recommended MiniCRM action Example use case
A new form is submitted Create Contact A website visitor fills out your contact form and is automatically added to MiniCRM as a new contact.
A new form is submitted Create Card A lead requests a quote through a form and a new opportunity is created in MiniCRM. The related contact is created automatically as part of the card creation.
A contact is updated in another system Update Contact A customer updates their phone number in another platform, and the contact record in MiniCRM is updated automatically.
A new email is received Create Contact A new inquiry arrives in your shared mailbox, and the sender is added to MiniCRM as a contact.
A new order or purchase is created Create Card A customer places an order in an ecommerce system, and Zapier creates a new opportunity in MiniCRM together with the related contact.
A new row is added in Google Sheets Create Contact A lead collected in a spreadsheet is automatically added to MiniCRM.
A new booking or appointment is created Create Card A booked consultation creates a new opportunity in MiniCRM for follow-up, including the related contact.
A payment is completed Update Card When a payment is received, the related card in MiniCRM is updated to reflect the new status.
A lead is added in a marketing tool Create Contact A new lead from a campaign is sent directly into MiniCRM.
A support request is submitted Create Card A help request creates a new card in MiniCRM so your team can track the case, and the related contact is also created automatically.

Typical ways to use these automations

Some common examples:

  • capture leads from forms, landing pages, and popups
  • add new contacts from spreadsheets or databases
  • create opportunities from quote requests, appointments, webshop orders, or service requests
  • update contact details when data changes in another tool
  • keep MiniCRM aligned with the apps your team already uses

How to choose the right MiniCRM action

  • Use Create Contact when you only want to add a new person or company to MiniCRM.
  • Use Update Contact when you want to change data for an existing contact.
  • Use Create Card when you want to create a new opportunity or process item in MiniCRM.
    The related contact will also be created automatically.
  • Use Update Card when you want to change an existing opportunity in MiniCRM.

Example: Create a MiniCRM contact from a Gmail email

This example shows how to create a simple Zap that adds a contact to MiniCRM when a new email arrives in Gmail.

Step 1 — Create a Zap

Log in to Zapier, then click Create and choose Zap.

Step 2 — Set Gmail as the trigger app

Search for and select Gmail, then choose New Email as the trigger event.

Connect your Gmail account and run a test to confirm Zapier can access sample data.

Step 3 — Add MiniCRM as the action app

Click + Add Step, search for MiniCRM, and select Create Contact.

Step 4 — Connect MiniCRM

If MiniCRM is not connected yet, click Sign in to MiniCRM, paste your API key, and click Continue.

Step 5 — Map the fields

Match the Gmail fields to the MiniCRM fields.

Example:

  • From Email → Email
  • From Name → First Name

Depending on the structure of the incoming email data, you may want to review how names are mapped before publishing the Zap.

Step 6 — Test and publish

Click Test Step to verify that a contact is created in MiniCRM.

If the test is successful, click Publish and turn the Zap on.

Example: Create a MiniCRM opportunity from a form submission

This is one of the most common automations.

For example, when someone submits a quote request form on your website, Zapier can create a new card (opportunity) in MiniCRM automatically.

Because Create Card also creates the related contact, this is often the best option when the form submission represents a real sales opportunity.

Typical flow:

  1. Trigger app: website form tool
  2. Trigger event: new form submission
  3. Action app: MiniCRM
  4. Action event: Create Card
  5. Map the form fields to the opportunity and contact fields in MiniCRM
  6. Test the Zap and publish it

This setup helps your team react faster and avoids manual lead entry.

Limitations

Please keep the following in mind:

  • The MiniCRM REST API / XML add-on must be active in your subscription
  • Only API key authentication is supported
  • The currently available trigger and action events depend on the Zapier integration setup
  • Custom objects are not supported

Troubleshooting: Authentication errors

Symptoms:
The connection fails when linking MiniCRM to Zapier.

Common causes:

  • the REST API / XML add-on is not active in your subscription
  • the API key is outdated or was regenerated after the integration was set up
  • the connected account was not fully authorized during setup

How to fix:

  1. In MiniCRM, go to Subscription and confirm that the REST API / XML add-on is enabled.
  2. Go to Settings → System → API/Integrations and check whether your API key is valid.
  3. In Zapier, reconnect the MiniCRM account if needed.

⚠️ Before regenerating your API key: Generating a new key will immediately break any existing integrations using the old key. Coordinate with your team first, and update the key in every connected integration right away to avoid downtime.

Need help?

If your Zap is not working as expected, first check:

  • whether the correct trigger and action were selected
  • whether the required fields are mapped properly
  • whether your API key is still valid
  • whether the test step returns real sample data

If the setup still fails, contact support and include:

  • the trigger app and trigger event
  • the MiniCRM action you selected
  • the exact step where the error appears
  • a screenshot of the Zap setup, if possible