Mav Zapier integrationAutomate Mav with Zapier.
The Mav Zapier integration gives you 2 triggers, 5 actions and 1 search. Your CRM can start a Mav texting playbook on a lead, stop it, or update the lead, and every event or outcome of a playbook can flow back to your other tools.
Verified Trustpilot reviews · AI, automation & growth agency
What the Mav Zapier integration does for you
Mav is an SMS agent driven by AI: it runs the text conversation with your leads and customers so your team does not have to. Connected to Zapier, it works both ways. Your other tools can start or stop that conversation, and what happens in it can travel back to them.
Three things this connection can do. A lead that gets a text without anyone lifting a finger: Run Playbook starts a Mav playbook on a lead from your CRM, creating the lead if Mav does not have it yet. A CRM that knows how the conversation ended: New Outcome starts a Zap when a playbook reaches an outcome, and the Zap updates the record. A clean stop: Stop Playbook halts every running playbook on a lead, for instance once the deal is closed elsewhere.
Both triggers are instant: Mav tells Zapier when the event happens, so the free plan's check interval never applies to them.
What Zapier does not do here matters too. The Mobile Phone field asks for a US mobile number with its area code, according to the field description, and Mav only works leads whose SMS Consent is true. Nothing on Zapier creates a playbook design or deletes a lead. And the Find Lead search adds a step, so any Zap that uses it needs a paid plan.
If Zapier is new to you, see our Zapier review. For help wiring Mav into a larger setup, see our Zapier agency page.
Zapier words, in plain English
Eight terms you will see in the editor and on this page.
- Zap
- The automation you build on Zapier: one trigger first, then one or more actions that run every time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it; Mav offers two.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something. Mav offers five, from Run Playbook to Update Lead.
- Task
- The unit Zapier bills: one action your Zap completed successfully. Your plan counts those and nothing else.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, which is the case for both Mav triggers.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
- Search step
- A step that looks up something that already exists in an app, so the steps after it can use what it found.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter, a search or a second action makes it one, and it then needs a paid plan.
What a Mav Zap really costs
Mav is not a premium app on Zapier, so it works on the free plan. You pay for actions that go through, never for the trigger.
- Premium appNo, available on the free plan
- Free plan100 tasks a month, two-step Zaps
- Mav triggers2, both instant, 0 tasks
- Search, filter or extra actionMulti-step Zap, paid plan
A Mav trigger never costs a task. Each action that succeeds counts as one, and one that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps. Find Lead before Update Lead, or a filter that keeps only some outcomes, makes the Zap multi-step: paid plan. The interval grid below is Zapier's general rule for polling triggers; it does not apply to Mav's two triggers, which are both instant.
Connect Mav 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 Mav account linked once, then reused by every Zap step that talks to Mav.
- 02
Pick Mav
Search for Mav in the dialog, select it, then click Add connection. You need an existing Mav account at this point; Zapier only links to it and does not open one.
- 03
Sign in and grant access
Sign in to Mav in the tab that opens and grant Zapier access. If the Mav account belongs to someone else, make sure yours can write to it, since actions such as Run Playbook and Update Lead change leads.
Your first Zap: send Mav outcomes back to your CRM
GoalWhen a Mav playbook reaches an outcome you care about, update the matching record in your CRM, so the sales team sees the result without opening Mav.
- 01
Create the Zap and pick the trigger
Start a new Zap, choose Mav as the app that starts it and New Outcome as the event, then select the Mav connection you set up earlier.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items of your Mav account, so you map the next steps on a real outcome. Note which fields come back.
- 03
Add the filter
Click the plus icon, add Filter and fill the three boxes: the field to look at, the rule, the value. Use a text rule on text and a number rule on numbers, or the filter never passes.
- 04
Add the CRM step
Add the update action of your CRM, find the record with a value from the trigger, and map the outcome into the right field. Test, then open the record to check it.
- 05
Publish
Click Publish to switch the Zap on. With the filter it is a multi-step Zap and needs a paid plan; without it, it fits the free one.
Mav triggers on Zapier
2 events start a Zap when something happens in Mav, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.
New Event
Instant triggerIn Zapier“Triggers when an event occurs during a play.”
Starts a Zap whenever something happens during a Mav play, so what happens during the play can be passed to your other tools as it goes.
New Outcome
Instant triggerIn Zapier“Triggers when a new outcome is obtained for a play.”
Fires when a play obtains a new outcome, the result Mav reaches with a lead, and hands that result to the steps that follow.
Mav actions on Zapier
Mav gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Conversion Event
ActionIn Zapier“Creates a conversion event on a lead.”
Records a conversion event on a lead in Mav. Both Conversion and Lead ID are required.
Run Playbook
ActionIn Zapier“Create and runs a new playbook on a lead. If lead already exist inside of Mav it will just run the specified playbook on that lead.”
Starts a playbook on a lead, and creates the lead first if Mav does not know it. Mobile Phone, SMS Consent and Use Business Hours are required.
Stop Playbook
ActionIn Zapier“Stops all running playbooks on a lead.”
Stops every playbook currently running on a lead, found by its mobile phone, the one required field.
Update Lead
ActionIn Zapier“Update information on a existing lead in Mav. This can be used to update additional information or a DID for a Party Line.”
Changes information on a lead that already exists in Mav, including details tied to a Party Line. Lead ID, the Mav identifier, is required.
Update Party Line Availability
ActionIn Zapier“Updates your party line availability.”
Sets your Party Line availability in Mav through its one required field, Party Line Availability.
The Mav search on Zapier
1 search step looks for data that already exists in Mav, so a later step can use it.
A search step finds something that already exists so later steps can use it. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Mav exposes no find-or-create variant. Three settings decide what happens when the result is not what you expected.
Find Lead
SearchIn Zapier“Find a lead inside of Mav.”
Looks up a lead inside Mav from its mobile phone, the one required field, and passes it to the following steps.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap and skips the steps that relied on it. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking this box turns a search into a find-or-create and asks for the fields to create the missing item. Mav does not offer that variant.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on.
When a Mav Zap breaks
Zapier attaches no help article to Mav and lists no limit specific to the app. The usual failures come from how Zapier works and from Mav's required fields.
Here are the general limits to know. For a method to unblock a stuck Zap, see our Zapier troubleshooting page.
The lead never gets a text
Run Playbook needs SMS Consent set to true for Mav to work the lead. If the mapped CRM field does not say true, Mav leaves that lead alone.Old leads are not picked up
A Zap only reacts to what happens after it is switched on. Leads already in your CRM do not get a playbook; starting them is a separate job.A loop between Mav and your CRM
As a general precaution, a Zap that writes where its own trigger looks can set itself off again. Check this when a Mav outcome updates a CRM that starts playbooks.A bulk import gets held back
If a trigger suddenly sends a huge batch, after an import or a migration, Zapier's flood protection can hold it back.
Need help automating Mav with Zapier?
A person reads every message.
