Resources · Zapier integration

Mavibot Zapier integrationAutomate Mavibot with Zapier.

1 trigger, 6 actions, 0 searches. The Mavibot Zapier integration starts a Zap when a customer writes to you on a connected channel, and lets Zapier create clients, send them messages, set their custom fields or look them up. Here is the real cost and what breaks.

Beta app Zapier still marks this integration as beta.

See the 7 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Mavibot Zapier integration does for your customer conversations

The Mavibot Zapier integration links Mavibot, a platform that builds websites, stores and chatbots from a written description and ships with its own CRM, to Zapier, a service that moves information between apps. Mavibot tells Zapier when a customer sends a message, and Zapier can act back on Mavibot clients in six ways.

A message log with the client attached. New Message starts the Zap, Find User by ID pulls the client's data, and a spreadsheet row keeps both side by side. Anyone on the team can read the history without opening Mavibot.

Clients created from somewhere else. Create Client adds a client to Mavibot, given a phone number or platform ID, a group and a messenger type. That is how contacts collected in another tool end up in the Mavibot CRM.

Clients tagged by what they do. Set Custom Field writes a value into a client's custom variable, and Send Message replies to them. A customer who writes in can be marked, followed up, or both.

What Zapier does not do here: there is one trigger only, so nothing else in Mavibot (a new client, a new order) can start a Zap. The three Find actions return data but cannot create what they do not find, and nothing deletes a client. Mavibot is also marked as a beta app on Zapier. Weighing your options? See our n8n vs Zapier guide.

Vocabulary

Zapier vocabulary in one minute

Eight words come back all over this page. Here they are in plain English, once.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that event happens.
Trigger
The event in an app that starts the Zap. With Mavibot, that event is a new message from a customer.
Action
What the Zap does after it starts: the step that writes, sends or looks something up for you in an app.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, so nothing waits.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise.
Search step
A step that looks up an existing item in an app for later steps. Mavibot has none: its Find steps are listed as actions.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it needs a paid plan.
Cost

What a Mavibot Zap really costs

Mavibot is not reserved for paid plans on Zapier: it works on the free plan. What you pay for is actions, not messages received.

  • Trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, two steps per Zap
  • Mavibot on the free planYes (beta app)

The trigger never costs a task, so a busy inbox costs nothing on its own. Each action that succeeds counts as one task, and one that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, two steps each: New Message plus Send Message fits, but adding Find User by ID before a spreadsheet row makes it multi-step and paid. The interval grid below is for polling triggers: it does not apply to New Message, which is instant.

Connect

Connect your Mavibot account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, open Apps and click + Add connection. A connection is your Mavibot account linked to Zapier once, then reused by every step that uses Mavibot.

  2. 02

    Find Mavibot

    Type Mavibot in the dialog's search box, pick it, then click Add connection. You need a Mavibot account already: Zapier only links to it, nothing more.

  3. 03

    Sign in and grant access

    Sign in to Mavibot in the tab that opens, then grant Zapier access to the account. Anything in Mavibot you do not own yourself needs read or write access for you before a Zap can touch it.

First Zap

Your first Zap: log every customer message with the client's data

GoalEach time a customer writes on a connected channel, fetch that client's data in Mavibot and add the message and the client details as a row in your spreadsheet.

  1. 01

    Create the Zap

    Start a new Zap, pick Mavibot as the app that starts it and New Message as the event, then select your Mavibot connection.

  2. 02

    Test the trigger

    Run the test: Zapier brings back the three most recent messages of the connected account so you map on a real one. Check whether a client ID comes through.

  3. 03

    Add Find User by ID

    Add Mavibot again as an action, choose Find User by ID, and map the client ID from the trigger into Client ID. Test the step and read what came back.

  4. 04

    Add the spreadsheet row

    Add your spreadsheet as the last action, pick the step that adds a row, and map the message and the client fields into columns. Test once more.

  5. 05

    Publish

    Publish the Zap to switch it on. With two actions it is a multi-step Zap, so it needs a paid plan. Want a guided build? Our Zapier training is there for that.

Triggers

The Mavibot trigger on Zapier

1 event starts a Zap when something happens in Mavibot, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

New Message

Instant trigger

In Zapier“Triggers when a new message is received from a customer in any connected channel.”

Starts your Zap whenever a customer sends a message on any channel connected to Mavibot. It is the only door into Zapier from Mavibot, so every Mavibot Zap that starts on Mavibot starts here.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when each incoming customer message should be logged, tagged on the client card or passed to your team outside Mavibot.
Watch out
it reacts to messages received from customers on every connected channel at once; add a filter if only some of them matter, and check at the test which fields arrive.
Actions

Mavibot actions on Zapier

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

1

Create Client

Action

In Zapier“Creates a new client.”

Adds a new client to the Mavibot CRM from a phone number or a platform-specific ID, attached to a group and a messenger type.

When to use it
when contacts gathered in another tool should exist as clients in Mavibot too.
Watch out
Platform ID, Group ID and Client Type are all required. The Platform ID shows on the client's card under Clients, and the Client Type value comes from the Mavibot documentation.
2

Find Order by ID

Action

In Zapier“Finds an order by ID and returns its variables.”

Fetches an order, which Mavibot also calls a deal, and returns its variables so the next step can quote them in a message or a sheet.

When to use it
when a Zap needs the details of a known order before writing to the customer or to your team.
Watch out
it needs both the Client ID and the Order ID; one without the other is not enough.
3

Find User by Custom Field

Action

In Zapier“Finds a client by a custom variable name and value.”

Looks a client up by the name and value of a custom variable instead of by ID, handy when the only thing another tool knows is a value you stored on the client.

When to use it
when a record elsewhere carries a reference you also wrote into a Mavibot variable.
Watch out
Variable Name and Variable Value are both required; check at the test what comes back when several clients share the value.
4

Find User by ID

Action

In Zapier“Finds a client by their ID and returns their data.”

Returns the data Mavibot holds on a client when you hand it that client's ID, ready to be reused by the steps that come after.

When to use it
right after New Message, when a later step needs more about the client than the message itself carries.
Watch out
Client ID is required. Zapier lists this step as an action, so check at the test what it returns and how it is counted.
5

Send Message

Action

In Zapier“Sends a message to a client”

Sends a text you write in the Zap to one Mavibot client, so a reply or a follow-up goes out without anyone typing it in Mavibot.

When to use it
when a customer should hear back after something happens elsewhere, a status change in another tool for example.
Watch out
Client ID and Message are both required; a Zap that cannot supply the client ID has nobody to send to.
6

Set Custom Field

Action

In Zapier“Sets a custom variable value for a client.”

Writes a value into one custom variable of a client, which is how a Zap marks a client card with a status, a source or any label you track there.

When to use it
after New Message, to record on the client that they wrote in through a given path.
Watch out
Client ID, Variable Name and Variable Value are required, and the variable name must match the one used in Mavibot.
When it breaks

When the Mavibot Zap breaks

Zapier attaches no help article to Mavibot and records no Mavibot limit. What breaks is what breaks on any Zap, plus the required IDs of each action.

Here are the cases worth checking first. Read them before you publish, and if a Zap still misbehaves, our Zapier troubleshooting page is the next stop.

  • Old messages are not picked up

    A Zap only reacts to what happens after it is switched on. Messages received before stay out of the Zap; moving that history is a separate job.

  • A missing ID stops the action

    Every Mavibot action asks for at least one required ID or value. If the earlier step does not carry it, the action has nothing to work on: check the mapping at the test.

  • A Zap that sets itself off

    A Zap that writes into the place its own trigger watches can start itself again and again, and burn through your tasks. Keep an eye on that before publishing any reply flow.

  • A sudden batch held back

    When a trigger suddenly returns a very large batch, after a bulk import or a migration for instance, Zapier's flood protection can hold those runs back.
Need help

Need help automating Mavibot with Zapier?

A person reads every message.

FAQ

Mavibot Zapier integration: your questions

01Is the Mavibot Zapier integration free?
Yes, Mavibot works on the free Zapier plan, since Zapier does not reserve it for paid plans. The free plan gives 100 tasks a month and as many Zaps as you like, each limited to two steps: one trigger, one action. New Message followed by Send Message fits that shape. A Zap that runs Find User by ID before writing a spreadsheet row has two actions, so it is multi-step and needs a paid plan. Sketch the steps first, then decide on the plan.
02How many tasks does a Mavibot Zap use?
Nothing for the trigger and one task per action that succeeds. A flood of customer messages costs nothing unless actions run behind it. In the logging Zap, the spreadsheet row costs one task per message. Find User by ID is listed as an action on Zapier, so it likely adds a second one, as may the other Find steps: confirm it on the task counter. An action that fails is not billed, and a few apps take more than one task per action, so watch the counter on your first runs.
03Is the Mavibot integration real time?
Yes. New Message is an instant trigger: Mavibot tells Zapier itself when a customer writes, so the Zap does not wait for a timed check. The plan intervals, 15 minutes on Free down to 1 minute on Team and Enterprise, concern polling triggers only, and Mavibot has none. A free-plan Zap on New Message therefore starts as fast as a paid one. In the editor, a Zap built on an instant trigger shows a lightning bolt, which is an easy way to confirm it.
04What is needed to connect Mavibot to Zapier?
A Mavibot account you can sign in to, and access to whatever the Zap will touch. On the Apps page of Zapier, click + Add connection, search for Mavibot, click Add connection, sign in in the new tab and grant access. Anything you do not own yourself in Mavibot needs read or write access for you beforehand. The connection is set up once and reused by the trigger and by all six actions in every Zap you build.
05Which Client Type value does Create Client expect?
The messenger type identifier, such as WhatsApp or Telegram, and the exact value is the one listed in the Mavibot documentation under Client Type. Typing a label you made up is the classic reason this action fails. The two other required fields follow the same logic: Platform ID is the client's phone number or platform-specific ID, visible on the client's card under Clients, and Group ID is the group the client belongs to. Fill all three, then run the step test.
06What if the Mavibot operation you want is not there?
Then Zapier cannot do it with Mavibot today. The integration has one trigger, New Message, and six actions to create, message, tag and look up clients or orders. There is no trigger for a new client or a new order, and no step that deletes anything. Check whether your need can start from a customer message, or from another app that then calls one of the six actions. If not, the step is out of reach through Zapier, whatever the plan.
07Zapier, Make or n8n for Mavibot?
Pick on criteria, not on a winner. On Zapier, Mavibot gives you an instant trigger on customer messages and six actions, works on the free plan for two-step Zaps, and is flagged as a beta app. Make and n8n come with their own catalogues and their own way of counting runs, and whether they offer Mavibot is something to check on their side. Compare the Mavibot steps each tool exposes, how each one bills, and who will maintain the automation.
Same platform

Other docs you might need on this stack.

Browse all integrations