Mateo Zapier integrationAutomate Mateo with Zapier.
The Mateo Zapier integration offers 0 triggers, 5 actions and 1 search. Another app always starts the Zap; Mateo then creates or updates a contact, sends a message from a template, launches a sendout or cleans up a phone number for you.
Verified Trustpilot reviews · AI, automation & growth agency
What the Mateo Zapier integration does for you
Mateo is a platform for GDPR-compliant conversations between a business and its customers. Plugged into Zapier, it becomes the receiving end: something happens in another app, and Mateo stores the contact or sends the message. Nothing in Mateo can start a Zap, because Zapier offers no Mateo trigger.
Three results come up again and again. A contact base that fills itself: Create Contact adds each new person from your form or spreadsheet, after Format Phone Number has put the number in E.164 shape. A message that goes out on its own: Send Message uses one of your Mateo templates to reach a person by email address, phone number or social channel ID. A record that stays current: Get Contact finds the person by one exact identifier, then Update Contact writes the change.
What Zapier does not do here matters as much. It cannot react to anything in Mateo: no incoming message, no new contact, no reply can start a Zap. It cannot delete a contact either, since no Mateo action does that on Zapier. And because a search adds a step to the Zap, the find-then-update pattern needs a paid plan.
If Zapier itself is new to you, see our Zapier review. For a hand with a bigger setup, see our Zapier agency page.
Zapier words, in plain English
Eight terms you will see in the editor. One line each.
- 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 a Zap. Mateo has none on Zapier, so the trigger always comes from another app you use.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you. Mateo offers five.
- Task
- The unit Zapier bills. One task is one action your Zap completed successfully, and your plan counts nothing else.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app the moment the event happens.
- Filter
- A step that lets the Zap go on only when what arrived meets your condition, 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 second action, a filter or a search makes it one, and then it needs a paid plan.
What a Mateo Zap really costs
Mateo is not a premium app on Zapier, so it is available on the free plan. What you pay for is each Mateo action that goes through.
- Premium appNo, works on the free plan
- Free plan100 tasks a month, two-step Zaps
- Mateo action1 task each time it succeeds
- Search or extra actionMulti-step Zap, paid plan
The trigger in the other app never costs a task. Every Mateo action that succeeds counts as one, and one that fails is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, each limited to two steps. Formatting a number before creating the contact, or searching before an update, already makes three steps: that is a multi-step Zap, on a paid plan. The interval grid below applies to the other app's trigger only if it is a polling one.
Connect Mateo to Zapier in three steps
- 01
Open the Apps page
In Zapier, open the Apps page of your account and click + Add connection. A connection is your Mateo account linked once, then reused by every Zap step that talks to Mateo.
- 02
Pick Mateo
Search for Mateo in the dialog, select it, then click Add connection. You need a Mateo account already; Zapier only links to it, it does not open one.
- 03
Sign in and grant access
Sign in to Mateo in the tab that opens and grant Zapier access. Use an account with write access to the contacts and templates your Zaps will touch, if they are not your own.
Your first Zap: new form answers become clean Mateo contacts
GoalEach time someone fills in your form, add that person to Mateo with a phone number already in E.164 format, so later messages reach the right line.
- 01
Create the Zap and set the trigger
Start a new Zap and pick your form tool as the app that starts it, with its new-response event. Mateo cannot start a Zap, so the trigger always lives in another app.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent responses of the connected form account, so you map the next steps on a real answer rather than a guess.
- 03
Add Format Phone Number
Add Mateo with Format Phone Number and put the phone answer from the form in the required Phone Number field. Test it and read the formatted number that comes back.
- 04
Add Create Contact
Add Mateo again with Create Contact and map the formatted number plus the other answers into the contact fields. Test, then check the contact in Mateo.
- 05
Publish
Click Publish to switch the Zap on. With two Mateo actions, this is a multi-step Zap and needs a paid plan; on the free plan, keep only Create Contact.
Mateo actions on Zapier
Mateo gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Contact
ActionIn Zapier“Creates a contact in hellomateo.”
Adds a new person to your Mateo contacts, using whatever details the earlier steps carried.
Update Contact
ActionIn Zapier“Updates a contact in hellomateo.”
Changes an existing Mateo contact. Its one required field is Contact ID, so the Zap must know which record it is editing.
Format Phone Number
ActionIn Zapier“Formats a phone number as E.164.”
Takes the required Phone Number field and returns it formatted as E.164, ready for the next step to use.
Create Sendout
ActionIn Zapier“Creates an immediate sendout for segments or recipients.”
Launches an immediate sendout to segments or to a set of recipients, rather than to one person.
Send Message
ActionIn Zapier“Sends a message using a hellomateo template.”
Sends one person a message built from a Mateo template. The required Recipient Handle takes an email address, a phone number or a social channel user ID.
The Mateo search on Zapier
1 search step looks for data that already exists in Mateo, 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. Mateo exposes no find-or-create variant on Zapier. Three settings decide what happens when the result is not what you expected.
Get Contact
SearchIn Zapier“Gets a contact by one exact identifier.”
Looks up one Mateo contact from a single exact identifier and hands what it found to the next steps. Check in the test that the Contact ID comes back.
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. Switch it on and 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 needed to create the missing item. Mateo offers no such variant.
- If multiple search results are found?Three ways out when several items match: keep the first, which is the default, stop the Zap, or hand all of them on.
When a Mateo Zap breaks
Zapier attaches no help article to Mateo and lists no limit specific to the app. The usual failures come from how Zapier works and from Mateo's required fields.
These cases cover the general limits worth knowing. For a method to unblock a Zap, see our Zapier troubleshooting page.
Past records are ignored
A Zap only reacts to what happens after it is switched on. Contacts already in your form or sheet are not sent to Mateo; moving that backlog is a separate job.The search finds nothing
Get Contact needs an exact identifier. With the default setting, no match stops the Zap and Update Contact never runs, so check how the value is written.A loop on your own data
As a general precaution, a Zap that writes where its trigger looks can set itself off again. Mateo has no trigger, but watch the other app's side.A burst gets held back
If the trigger app suddenly returns a huge batch, after a bulk import for example, Zapier's flood protection can hold it back.
Need help automating Mateo with Zapier?
A person reads every message.
