Mayar Zapier integrationAutomate Mayar with Zapier.
The Mayar Zapier integration gives you 3 triggers, 0 actions and 0 searches. New customers, one-off transactions and recurring subscription payments can each start a Zap, and everything that follows happens in your other apps, never back in Mayar.
Verified Trustpilot reviews · AI, automation & growth agency
What the Mayar Zapier integration does for you
The Mayar Zapier integration links your Mayar account, a checkout, payment and billing tool, to the rest of your apps through Zapier. It reads three things from Mayar: new customers, completed one-off transactions and completed subscription payments. Each one can start a Zap that writes somewhere else.
Three results worth building. A sales ledger that fills itself: New Transaction (Non-Recurring) adds a row to a spreadsheet for each completed one-off payment, ready for your bookkeeping. A welcome sequence that starts on its own: New Customer sends each new buyer to your email marketing tool. A subscriptions view your team can read: New Recurring Transaction (Subscription) posts each renewal, repayments included, to a chat channel or a tracking sheet.
Now the limits. Zapier offers no action and no search for Mayar, so a Zap can read from Mayar but never write back: no creating a product, no issuing a refund, no looking up a past payment. All three triggers are polling ones, so nothing arrives the instant it happens. And the payments are split in two: one-off sales and subscription payments come through different triggers, so a Zap on one never sees the other.
If you are still weighing Zapier itself, see our Zapier review before you build.
Zapier words in one minute
Eight words come back on this page. Here they are in plain English, once.
- Zap
- The automation you build in 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. Mayar has three: a new customer, a one-off transaction and a subscription payment.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you in another app.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan is a count of them.
- Polling vs instant trigger
- A polling trigger is checked by Zapier on a timer set by your plan. An instant one is reported by the app. All Mayar triggers are polling.
- Filter
- A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
- Connection
- Your Mayar account linked to Zapier once, then reused by every Zap and every step that needs Mayar.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes one, and it needs a paid plan.
What a Mayar Zap really costs
The Mayar side is free: none of the three triggers ever uses a task, and Zapier's regular checks of Mayar cost nothing either.
- Any Mayar trigger0 tasks
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo, works on the free plan
You pay in tasks for the steps after the trigger. Each action that completes counts once, so a Zap with two actions uses twice what a one-action Zap uses, and a failed action is not counted. Mayar is not a premium app: it works on the free plan, which gives 100 tasks a month and as many Zaps as you like, each limited to one trigger and one action. A filter or a second action makes the Zap multi-step, and that takes a paid plan. The grid below matters here: it is how often Zapier checks Mayar's three polling triggers on each plan.
Connect Mayar to Zapier
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. Before you start, you need a Mayar account of your own, plus access to anything owned by someone else that the Zap should read.
- 02
Pick Mayar
Type Mayar in the search box of the dialog, select it in the results, then click Add connection. A new browser tab opens on the Mayar side, where the sign-in happens.
- 03
Sign in and grant access
Log in to Mayar in that tab and allow Zapier to reach your account. The connection then shows on the Apps page, and each of the three Mayar triggers can reuse it.
Your first Zap: a sales ledger for one-off payments
GoalEach completed one-off transaction in Mayar that passes your filter becomes a row in your sales spreadsheet.
- 01
Create the Zap
Start a new Zap and choose Mayar as the app that starts it. Pick New Transaction (Non-Recurring) as the event and select the connection you made earlier.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent one-off transactions of your account, so you map the next steps on a real sale.
- 03
Add the filter
Click the plus icon, add Filter and fill its three boxes: the field to look at, the rule, the value to compare with. Use a number rule on amounts. This makes the Zap multi-step.
- 04
Add the spreadsheet step
Add your spreadsheet app, choose the event that adds a row, and map the transaction's details into the columns. Test it once and read the row it created.
- 05
Publish
Click Publish to switch the Zap on. It runs on a paid plan because of the filter, and Zapier then checks Mayar at your plan's interval.
Mayar triggers
3 events start a Zap when something happens in Mayar. Zapier checks for them at the interval your plan allows.
New Customer
Polling triggerIn Zapier“Triggers when a new Customer is created.”
Starts your Zap for each customer newly created in Mayar, and hands that customer's details to the steps that follow.
New Recurring Transaction (Subscription)
Polling triggerIn Zapier“Triggers when a new recurring transaction completed (include repayment).”
Picks up each completed payment on a recurring or subscription product, repayments included, and sends it down your Zap.
New Transaction (Non-Recurring)
Polling triggerIn Zapier“Triggers when a new transaction completed (not included transaction from recurring/subscription product).”
Fires on every completed transaction that is not part of a recurring or subscription product, so single purchases get their own flow.
When a Mayar Zap breaks
Zapier attaches no help article to Mayar, so the cases below are the general Zapier limits that apply to its three polling triggers.
Here are the general limits to know: several are things the Zap does not do rather than errors. If something looks off, start with our Zapier troubleshooting guide.
Past payments never arrive
A Zap only reacts to what happens after it is switched on. Customers and transactions already in Mayar are not picked up; moving them is a separate job.Subscription payments missing
New Transaction (Non-Recurring) leaves out recurring and subscription payments. They come through New Recurring Transaction (Subscription), in a Zap of their own.A big batch gets held back
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back.No duplicates from one trigger
On a polling trigger, Zapier keeps track of what it has already seen, so the same customer or payment does not start the Zap twice.
Need help automating Mayar with Zapier?
A person reads every message.
