Resources · Zapier integration

Maidpad Zapier integrationAutomate Maidpad with Zapier.

The Maidpad Zapier integration gives you 8 triggers, 4 actions and 0 searches. Every trigger is instant, so Maidpad reports a new client, invoice or job change to Zapier straight away, and Zapier can create clients and jobs or send messages back.

See the 12 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Maidpad Zapier integration is good for

The Maidpad Zapier integration connects Maidpad, the platform cleaning companies use to run their day-to-day operations, with the other apps you work in. It goes both ways: Maidpad events can start an automation elsewhere, and other apps can create clients, create or update jobs and send messages in Maidpad.

Three results that are worth building early. Leads that become clients without retyping: a form entry runs Create Client, so the booking request is already in Maidpad, phone number included, when you call back. Books that follow the work: Invoice Created and Invoice Paid hand each invoice and each payment to the tool your bookkeeper uses. A team that hears about changes: Job Changed and Job Canceled post a heads-up where the crew already talks.

The best news for a free plan: all 8 Maidpad triggers are instant. The polling interval of your plan never slows them down, so a free account gets the same speed as a paid one on the Maidpad side.

What Zapier does not do with Maidpad: it cannot look anything up there. There is no search, so a Zap cannot find an existing client or job by name before acting on it. To compare this setup with other platforms, the Make vs Zapier page is a good place to start.

Vocabulary

Zapier vocabulary in one minute

Seven words come back everywhere below. Here they are once.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event that starts the Zap. In Maidpad: a client, an invoice or a job that is created, changed, finished or paid.
Action
What the Zap does once it has started. In Maidpad, that means creating a client, creating or updating a job, or sending a message.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is counted in tasks.
Instant vs polling
An instant trigger is reported by the app as it happens. A polling one is checked by Zapier on a timer. Every Maidpad trigger is instant.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise.
Connection
Your Maidpad account linked to Zapier once, then reused by every step and every Zap that touches Maidpad.
Cost

What a Maidpad Zap costs you

Maidpad is not a premium app, so it works on the free plan. Its triggers cost nothing: only an action that succeeds is counted as a task.

  • Maidpad triggers8, all instant, never counted
  • Maidpad actions1 task each time one succeeds
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

A Zap that runs Create Client once uses one task; a Zap with three actions uses three per run. A failed action is not counted. The free plan gives 100 tasks a month and Zaps of two steps only: one trigger, one action. A filter, a second action or a search makes the Zap multi-step, which needs a paid plan. The interval grid below is how often Zapier checks polling triggers; it does not apply to the instant triggers of Maidpad.

Connect

Connect Maidpad to Zapier in three steps

  1. 01

    Find Maidpad

    Open the Apps page of your Zapier account and click + Add connection. In the dialog, search for Maidpad by name and pick it from the results that appear.

  2. 02

    Sign in

    Click Add connection. Maidpad opens in a new tab: sign in with the account whose clients, jobs and invoices the Zap should use. You need your own Maidpad account to get through this step.

  3. 03

    Allow access

    Grant Zapier access to the account. The connection now appears on the Apps page and every Maidpad step reuses it. For records you do not own, make sure your account can read them, and write to them if a Zap changes them.

First Zap

Your first Maidpad Zap

GoalEach client added in Maidpad joins your mailing list straight away, so the welcome email never depends on someone remembering it.

  1. 01

    Create the Zap

    Start a new Zap. Pick Maidpad as the first app and Client Created as the event, then choose the Maidpad connection you made above.

  2. 02

    Test the trigger

    Run the trigger test. Zapier brings back the three most recent clients of the account, so you map on a real one. No client yet? Add a test client in Maidpad first.

  3. 03

    Add the action

    Add the second step in your mailing tool and choose the event that adds a contact. Map the client's name and contact details from Maidpad into its fields.

  4. 04

    Test the action

    Run the action test and check the mailing list: the contact should be there. It is a real write, so remove it afterwards if it was only a test.

  5. 05

    Publish

    Click Publish to switch the Zap on. Because Client Created is instant, each new client is sent over as soon as Maidpad reports it; older clients are not.

Triggers

The 8 Maidpad triggers

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

1

Client Created

Instant trigger

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

Starts the Zap as soon as a new client is added in Maidpad, whether your office typed it in or another Zap created it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to add the new client to your mailing list or contact book while the first booking is still being arranged.
Watch out
a Zap that also runs Create Client from this trigger would feed itself; keep those two in separate, unrelated flows.
2

Invoice Created

Instant trigger

In Zapier“Triggers when a new invoice is created.”

Picks up every invoice Maidpad generates, before it is paid. It tells you what has been billed, not what has come in.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to log each invoice in the sheet your bookkeeper keeps, so the open amounts are visible outside Maidpad.
Watch out
pair it with Invoice Paid in a second Zap if you want to close the loop; one Zap only has one trigger.
3

Invoice Paid

Instant trigger

In Zapier“Triggers when a invoice is paid.”

Reacts when an invoice is settled in Maidpad. This is the signal that money has actually arrived for that piece of work.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to mark the matching line as paid in your accounting sheet or to thank the client by email.
Watch out
Job Paid exists too; check which one your office actually uses, or you may count the same payment twice.
4

Job Canceled

Instant trigger

In Zapier“Triggers when a job is canceled.”

Fires the moment a job is canceled in Maidpad, so the free slot is known to the team before anyone drives over.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to warn the cleaner who had the job, through the chat app they actually read.
Watch out
the Zap only hears about cancellations the office actually records in Maidpad; a job dropped by phone and never canceled there stays silent.
5

Job Changed

Instant trigger

In Zapier“Triggers when a job changes.”

Responds to any change on an existing job, from a moved date to a new frequency. It is the widest of the job triggers.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to keep an outside calendar or job sheet in step with what the office edits.
Watch out
never pair it with Update Job on the same jobs: the update counts as a change, and the Zap restarts itself in a loop.
6

Job Created

Instant trigger

In Zapier“Triggers when a new job is created.”

Catches every new job booked in Maidpad. Think of it as your order book, readable from any other app.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to add the job to a shared team calendar the moment it is booked.
Watch out
jobs booked by another Zap through Create Job start it too; never point the two back at each other, or the Zap feeds itself.
7

Job Finished

Instant trigger

In Zapier“Triggers when a job is finished.”

Goes off when a job is marked as finished in Maidpad. The work is done, even if it is not paid yet.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to send the client a thank-you or a request for feedback from your email tool.
Watch out
it only fires if the team really closes jobs in Maidpad; jobs left open never reach the Zap.
8

Job Paid

Instant trigger

In Zapier“Triggers when a job is paid.”

Runs when a job itself is marked as paid in Maidpad, which is how some teams track payment instead of through invoices.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to update a revenue sheet job by job when you do not issue an invoice each time.
Watch out
do not watch it alongside Invoice Paid in the same sheet unless you are sure they never cover the same job.
Actions

The 4 Maidpad actions

Maidpad gives you 4 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 in MaidPad”

Adds a client to Maidpad from data arriving in another app, such as a booking form.

When to use it
when requests come in through your website and you want them in Maidpad before you call back.
Watch out
first name, last name, phone, Charge by and Charge Amount are all required; a source without a phone stops the step.
2

Create Job

Action

In Zapier“Creates a Job in MaidPad”

Books a new job in Maidpad from another app, with its date and how often it repeats.

When to use it
when an accepted quote or a calendar slot elsewhere should become a job without retyping.
Watch out
Date and Frequency are both required, so the source must say when the job starts and whether it repeats.
3

Send Message

Action

In Zapier“Sends a message in MaidPad.”

Sends a message through Maidpad to a client, with the text you build from the earlier steps.

When to use it
to confirm a booking or say thanks after a job, from inside the tool your clients already know.
Watch out
Client, Message and Send to are required; the client has to exist in Maidpad already.
4

Update Job

Action

In Zapier“Updates a Job in MaidPad”

Changes an existing job in Maidpad, for instance its frequency, from information arriving elsewhere.

When to use it
when a client changes their plan in another tool and Maidpad should follow.
Watch out
you must point at a specific Job, and with no search on Maidpad the earlier step has to carry which job it is.
When it breaks

When a Maidpad Zap breaks

Zapier links no help article to Maidpad, so the cases below are the general ones, applied to this app.

Two things cause most of the trouble here: a required field that the source app does not fill, and a Zap that writes back into the jobs its own trigger is watching. If a Zap still misbehaves after that, the Zapier troubleshooting page is the next stop.

  • Job Changed plus Update Job

    A Zap that updates the very jobs its trigger watches sets itself off again and again, and burns through your task count fast.

  • Nothing from before the Zap

    A Zap only reacts to what happens after it is switched on. Clients, jobs and invoices already in Maidpad are never picked up.

  • A sudden flood of items

    After a bulk import or a migration, a trigger that returns a huge batch at once can be held back by Zapier's flood protection.

  • A required field left empty

    Every Maidpad action has required fields. If the earlier step leaves one of them empty, the action does not go through for that run.
Need help

Need help automating Maidpad with Zapier?

A person reads every message.

FAQ

Maidpad Zapier integration FAQ

01Is the Maidpad Zapier integration free?
Yes, within the limits of the free plan. Maidpad is not a premium app, so it works without paying: 100 tasks a month and Zaps made of one trigger and one action. A Zap such as Job Finished followed by Send Message fits. The moment you add a filter, a second action or a search, for example to notify the team and also log the job in a sheet, the Zap becomes multi-step and needs a paid plan.
02How many tasks does a Maidpad Zap use?
One per successful action, nothing for the trigger. Maidpad telling Zapier that a job changed costs nothing; Create Client, Create Job, Update Job or Send Message each cost one task when they work. A Zap with two actions uses two tasks per run. An action that fails is not counted. The real risk is a Zap that restarts itself, such as Job Changed feeding Update Job, because each loop eats another task.
03Are Maidpad triggers real time?
Yes. All 8 Maidpad triggers are instant: Maidpad tells Zapier as soon as the client, invoice or job event happens, and the Zap starts right away. The polling grid of the plans, 15 minutes on Free, does not apply to them, so a free account gets the same speed as a paid one. In the editor, a Zap built on an instant trigger shows a lightning bolt, which is a quick way to check.
04What does it take to connect Maidpad to Zapier?
A Maidpad account you can sign in to and a Zapier account. On the Apps page of Zapier, click + Add connection, search for Maidpad, click Add connection, sign in to Maidpad in the tab that opens and grant access. Every Maidpad step then reuses that connection. If a Zap must touch clients or jobs you do not own, your account needs read access to them, and write access if the Zap changes them.
05Why does a Maidpad Zap keep running on its own?
Because it probably writes into what its own trigger watches. The classic case is Job Changed as the trigger and Update Job as the action on the same jobs: the update is itself a change, so Maidpad reports it, and the Zap runs again. Each run costs a task, so the count drops fast. Split the flow, or on a paid plan add a filter that only lets through the changes you really want to act on.
06What if the Maidpad action you need is not there?
Then Zapier cannot offer it: the list of operations comes from the Maidpad integration and cannot be extended from the editor. Today that list is 8 triggers and 4 actions, with no search and nothing to delete records. Check whether Update Job covers the change you have in mind. If not, that step stays manual in Maidpad, or it has to happen in another tool that does offer it. Either way, nothing on the Zapier side will change that list for you.
07Zapier, Make or n8n for Maidpad?
Choose on what you need from Maidpad. On Zapier you get 8 instant triggers and 4 actions, enough to feed Maidpad from forms and to push its events to other apps, but no way to look up a client or job first. If lookups matter, check whether the other platform offers Maidpad at all and with which operations. Then weigh the number of runs you expect and who will look after the automation over time.
Same platform

Other docs you might need on this stack.

Browse all integrations