Resources · Zapier integration

Maroo Zapier integrationAutomate Maroo with Zapier.

Maroo Zapier integration: 2 triggers, 3 actions, 2 searches. Maroo handles payments for wedding and event vendors. Zapier links it to the rest of your tools, so a new client or a changed payment request moves on without anyone retyping it.

See the 7 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Maroo Zapier integration actually does

Maroo is a payments platform built for the weddings and events trade. Connecting it to Zapier means its clients and payment requests can feed your other tools, and those tools can create clients or payment requests in Maroo. Both Maroo triggers reach Zapier the moment the event happens.

Three outcomes worth building. A payment tracker that keeps itself current: Payment Request Status Updated fires when a request is created, updated or deleted, and your sheet gets the change. A client file in one place: New Client reports every client added from the vendor dashboard, ready to copy wherever you keep contacts, so planning and billing work from the same client list. A payment request without double entry: Create Client then Create/Update Payment Request turn an incoming enquiry into a Maroo client with a request attached, with the amount, the due date and the payment method filled from the data you already have.

What Zapier does not do here: the triggers only cover clients and payment requests, and no action deletes anything in Maroo. Lookups are limited to Get Clients and Get Payment Request, and neither can create the item when it is missing.

To weigh the tool itself before building, see our Zapier review.

Vocabulary

Zapier words, in plain English

Eight terms carry this whole page. Each one, once.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event that starts the Zap. With Maroo, a new client, or a payment request created, changed or removed.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you in an app.
Task
The unit Zapier bills. One task is one action your Zap completes successfully; your plan counts those.
Instant trigger
A trigger the app reports itself: it calls Zapier when the event happens, with no timed check. Both Maroo triggers work this way.
Polling trigger
The other kind: Zapier asks the app on a timer and keeps only what it has not seen. Maroo has none of them.
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 something already in an app, so the steps after it can use what it found.
Cost

What Maroo on Zapier costs you

Maroo is not a premium app, so the free plan can use it. Zapier counts tasks, and only successful actions are billed.

  • Trigger0 task, always
  • Each successful action1 task
  • Free plan100 tasks a month, Zaps of two steps
  • Premium appNo

The trigger costs nothing. Each action that goes through costs one task, so creating a client and then a payment request uses two. A failed action is not counted. The free plan gives 100 tasks a month and unlimited Zaps of two steps each; a second action, a filter or a search makes the Zap multi-step, which needs a paid plan. The interval grid below is for polling triggers only and does not apply to the two instant Maroo triggers.

Connect

Connect Maroo to Zapier in three steps

  1. 01

    Open your connections

    Have your Maroo account ready. In Zapier, open the Apps page of your account and click + Add connection. A connection is your Maroo account linked once, then reused by every Zap that uses Maroo.

  2. 02

    Pick Maroo

    Type Maroo in the search box of the dialog, select it, then click Add connection. A new tab opens on the Maroo side, where the rest of the setup happens.

  3. 03

    Sign in and allow access

    Log in to Maroo in that tab and grant Zapier access. If the clients or payment requests you want to touch belong to an account you do not own, get read or write rights on it first.

First Zap

Your first Zap: a payment tracker in a sheet

GoalEach Maroo payment request that changes, and passes your filter, is written as a row in your spreadsheet.

  1. 01

    Start with the status trigger

    Create a Zap, pick Maroo as the app that starts it and Payment Request Status Updated as the event, then select your Maroo connection.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of the account, so you set up the next steps on a real payment request.

  3. 03

    Add the filter

    Click the plus icon, choose Filter, and set the field to check, the rule and the value. Use a text rule on text and a number rule on numbers, or it never passes.

  4. 04

    Write the row

    Add your spreadsheet action and map the payment request data into its columns. Read the field names on the test result rather than guessing them.

  5. 05

    Test, then publish

    Test each step once and read what came back, then click Publish. With a filter inside, this Zap is multi-step and needs a paid plan.

Triggers

The 2 Maroo triggers

2 events start a Zap when something happens in Maroo, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Client

Instant trigger

In Zapier“Triggers when a new client is created by vendor dashboard.”

Starts your Zap each time a client is added from the Maroo vendor dashboard. Whatever you record there can then travel to the tools where you plan the event or follow up with that client.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you want each new Maroo client copied into a sheet or a contact list without opening two screens.
Watch out
the description speaks of clients created from the vendor dashboard; if you also add clients through Create Client, check on a test whether those start the Zap too.
2

Payment Request Status Updated

Instant trigger

In Zapier“Triggers when a payment request is created, updated or deleted”

Covers the whole life of a payment request: it fires when one is created, when it is changed and when it is deleted. That makes it the trigger for anything that tracks money owed.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you keep a running list of payment requests outside Maroo and want it to follow every change.
Watch out
three kinds of change start the same Zap, so add a filter if you only care about one of them, and check on the test which field tells them apart.
Actions

The 3 Maroo actions

Maroo gives you 3 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 Client”

Adds a client to your Maroo account from data that arrives elsewhere, a form answer or a new row for instance.

When to use it
enquiries reach you outside Maroo and you want each one on file before you bill it.
Watch out
First Name, Last Name, Email and Phone number are all required, so the step before must carry all four.
2

Create/Update Payment Request

Action

In Zapier“Creates or updates a payment request”

Opens a payment request for a client, or updates an existing one, straight from your Zap.

When to use it
right after Create Client, or after a search that found the client, to bill without re-entering anything.
Watch out
Client, Contract amount, Payment due and Payment method are required, and the amount goes in dollars without cents.
3

Get Payment Request

Action

In Zapier“Receive all Payment requests or one that complies the search parameters”

Pulls payment requests from Maroo as an action step: all of them, or the one that matches what you ask for.

When to use it
a later step needs the details of a request that the trigger did not bring.
Watch out
the same name also exists as a search; check on the test which one returns what your next step expects.
Searches

The 2 Maroo searches

2 search steps look for data that already exists in Maroo, so a later step can use it.

A search step finds something already in Maroo and passes it to the steps after it. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Any search makes the Zap multi-step.

1

Get Clients

Search

In Zapier“Provide a list of all your clients”

Looks through your Maroo clients so a later step can use the one it finds.

When to use it
before Create/Update Payment Request, when the client already exists and you only need to point at it.
Watch out
whether it wants the exact value or something close is decided by Maroo, so test with a real client first.
2

Get Payment Request

Search

In Zapier“Receive all Payment requests or one that complies the search parameters”

Finds an existing payment request, or all of them, and hands the result to the following steps.

When to use it
you need the state of a request before updating it with Create/Update Payment Request.
Watch out
if several requests match, the setting above decides which one goes on, so pick it on purpose.

The three settings every search exposes

  1. Successful if no search results are found?
    Left as is, a search that finds nothing stops the Zap there and skips the steps that depend on it. Switched on, the Zap continues with nothing in hand.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Maroo exposes no find-or-create variant, so neither of its two searches can create the missing item.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When it breaks

When the Maroo Zap breaks

Zapier attaches no help article to Maroo and no Maroo-specific limit is on record, so the known traps are the general ones.

  • Past clients are never picked up

    A Zap only reacts to what happens after you switch it on. Clients and payment requests created before stay put; moving them is a separate job.

  • A Zap that sets itself off

    A Zap that writes into the very place its trigger watches can start itself again and again. A payment-request Zap that also creates requests deserves a check.

  • A sudden flood held back

    If a trigger suddenly sends a huge batch, after a bulk import for instance, Zapier's flood protection can hold those runs back.

  • A search that finds nothing

    By default an empty search stops the Zap and skips the steps after it. If that is not what you want, change the setting before you publish.
Need help

Need help automating Maroo with Zapier?

A person reads every message.

FAQ

Maroo Zapier integration: questions people ask

01Is the Maroo Zapier integration free?
Yes, on Zapier's side. Maroo is not a premium app, so the free plan can use it, with 100 tasks a month and an unlimited number of Zaps. The catch is the size of each Zap: two steps, one trigger and one action. Copying each new Maroo client into a sheet fits. Creating a client and then a payment request for it takes two actions, so it needs a paid plan or the free trial. The same goes for any Zap with a filter or a search.
02How many tasks does a Maroo Zap use?
One for each action that succeeds, nothing for the trigger. A payment request that changes and starts your Zap costs nothing by itself. If the Zap then writes one row, that change costs one task. A Zap that creates a client and then a payment request costs two per run. An action that fails is not counted. A few apps and actions take more than one task when they complete, so read the count on your first test runs.
03Do Maroo Zaps run in real time?
Yes. Both Maroo triggers are instant: Maroo tells Zapier itself when a client is added or a payment request changes, and the Zap starts right away on every plan, the free one included. The interval grid of the plans only concerns polling triggers, which Maroo does not have. In the editor, a Zap built on an instant trigger shows a lightning bolt, which is a quick way to check. Nothing to tune on that side.
04What does it take to connect Maroo to Zapier?
A Maroo account, and access to the clients and payment requests you want the Zap to touch. From the Apps page of Zapier, click + Add connection, search Maroo, sign in to Maroo in the tab that opens and grant access. The connection is made once and reused by every Zap. If the account belongs to someone else on your team, get read or write rights first, since Zapier sees only what your login sees.
05Why does the Maroo payment request step fail?
Check the required values first. Create/Update Payment Request needs four of them: a client chosen from your Maroo list, a contract amount, a due date and a payment method picked from the proposed ones. The amount is entered in dollars, without cents. And the client must already exist in Maroo, so put Create Client or the Get Clients search before it. Check each value on the test before you publish.
06What if the Maroo operation you need is missing?
Then Zapier does not offer it for Maroo today. The visible list is two triggers, three actions and two searches: clients and payment requests, and nothing that deletes. One workaround is to start from Payment Request Status Updated or New Client and send the data to another app that has the operation, then act there. Check on a test that the data Maroo sends is enough for that, before you build the rest.
07Zapier, Make or n8n for Maroo?
Compare on criteria, not on a ranking. Coverage first: on Zapier, Maroo offers the seven operations on this page; check that another tool lists Maroo at all before comparing further. Speed next: both Maroo triggers are instant here, so a plan's polling interval does not apply. Billing last: Zapier counts one task per successful action, so a client plus a payment request is two tasks. Set that against the volume of bookings you expect.
Same platform

Other docs you might need on this stack.

Browse all integrations