Resources · Zapier integration

Maidily Zapier integrationAutomate Maidily with Zapier.

The Maidily Zapier integration gives you 17 triggers, 0 actions and 0 searches. Maidily can start a Zap when a quote, a job, a customer or a tech changes, but every step that follows happens in another app. Here is what each trigger does and what it costs.

See the 17 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Maidily Zapier integration actually does

The Maidily Zapier integration lets events in Maidily, the scheduling software built for cleaning businesses, start an automation in another app. It works in one direction only: Maidily reports what happened (a quote accepted, a job canceled, a tech added), and the rest of the Zap runs elsewhere.

Three results people usually build first. A sales log that fills itself: Quote Accepted and Quote Rejected each push a line into a sheet, so you can see what converts without opening Maidily. A heads-up for the office when plans change: Job Cancelation and Subscription Cancelation send a message to whoever rebuilds the schedule. A clean record of money in: Paid Job hands each paid job to the tool your bookkeeper already reads.

What Zapier does not do for Maidily: it cannot write anything back. There is no action and no search on the Maidily side, so a Zap will never create a job, edit a quote or look up a customer in Maidily. If the plan is to feed Maidily from a form or a CRM, this integration does not cover it, and no setting changes that.

Every one of the 17 triggers works by polling, so nothing here is instant. If you are still weighing tools, the n8n vs Zapier comparison is a fair place to start.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are once, in plain English.

Zap
The automation you build on 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. With Maidily, that is a quote, job, customer, tech or time off event.
Action
What the Zap does once it has started: the step that writes, sends or moves something. With Maidily, it always lives in another app.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan is a count of those.
Polling vs instant
A polling trigger is checked on a timer by Zapier. An instant one is reported by the app the moment it happens. All Maidily triggers poll.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise.
Connection
Your Maidily account linked to Zapier once, then reused by every Zap and every step that uses Maidily.
Cost

What a Maidily Zap costs you

Maidily is not a premium app, so it works on the free plan. Watching Maidily is free: the trigger never costs a task, however often Zapier checks.

  • Maidily triggerFree, never counted
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo, works on the free plan
  • Filter or second actionMulti-step Zap, paid plan

You pay for actions that succeed in the other app. One Zap with two actions counts twice per run; an action that fails is not counted. The free plan gives 100 tasks a month but only two-step Zaps, one trigger and one action. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The grid below is how often Zapier checks a polling trigger on each plan, and it applies to every Maidily trigger.

Connect

Connect Maidily to Zapier in three steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. A dialog opens with a search box: type Maidily and pick it from the list of apps.

  2. 02

    Sign in to Maidily

    Click Add connection. A new tab opens on Maidily: sign in with the account whose quotes, jobs and team you want Zapier to watch. You need a Maidily account of your own before this step.

  3. 03

    Grant access

    Approve the access Zapier asks for. The connection then shows on the Apps page, and every Zap that uses Maidily reuses it. If some records belong to someone else, make sure your account can at least read them.

First Zap

Your first Maidily Zap

GoalEach quote a customer accepts in Maidily lands as a new row in a sheet, so the conversion log keeps itself up to date.

  1. 01

    Create the Zap

    Start a new Zap. For the first step, pick Maidily as the app and Quote Accepted as the event, then choose the Maidily connection you made earlier.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent accepted quotes of the account, so you map on a real one. No accepted quote yet? Accept a test quote in Maidily first.

  3. 03

    Add the action

    Add the second step in your spreadsheet app and choose the event that adds a row. Map the values from the Maidily quote into the columns you want to see.

  4. 04

    Test the action

    Run the action test once and open the sheet: the row should be there. That test row is a real write, so delete it if you do not want it in the log.

  5. 05

    Publish

    Click Publish to switch the Zap on. From then on, each newly accepted quote is picked up at the next check of your plan, never the ones accepted before.

Triggers

The 17 Maidily triggers

17 events start a Zap when something happens in Maidily. Zapier checks for them at the interval your plan allows.

1

Quote Accepted

Polling trigger

In Zapier“Triggers when the quote is accepted.”

Starts the Zap once a customer says yes to a quote you sent from Maidily. It is the cleanest signal you have that a lead turned into work.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to log each win in a sheet or tell the person who books the crew that a new client is on the way.
Watch out
only quotes accepted after you publish the Zap count; older wins stay where they are.
2

Job Cancelation

Polling trigger

In Zapier“Triggers when a job is getting canceled.”

Reacts when a single job is being canceled in Maidily, so the gap in the schedule does not go unnoticed by the rest of the team.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to warn the office by message, so someone can offer the free slot to another customer.
Watch out
this covers one job; a recurring plan that stops is a different trigger, Subscription Cancelation.
3

Subscription Cancelation

Polling trigger

In Zapier“Triggers when a job subscription is canceled.”

Fires when a customer ends a job subscription, the recurring arrangement behind repeat visits. That is often the moment a regular account is about to be lost.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to open a follow-up for whoever handles retention, while the reason is still fresh.
Watch out
it tells you a subscription ended, not why; the reason still has to be asked of the customer.
4

Customer Deleted

Polling trigger

In Zapier“Triggers when a customer is deleted.”

Picks up the removal of a customer record from Maidily. Useful when another tool keeps a copy of your client list and should not keep someone you dropped.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to flag the matching contact in your mailing tool or sheet, so nobody keeps writing to them.
Watch out
Maidily cannot be searched from Zapier, so the other app has to find the contact on its own side.
5

Job Deleted

Polling trigger

In Zapier“Triggers when the job is deleted.”

Catches a job erased from Maidily altogether, which is not the same thing as a cancelation. The record is gone, not just stopped.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to keep an outside calendar or job sheet tidy when someone clears out a duplicate or a mistake.
Watch out
if your team deletes jobs instead of canceling them, Job Cancelation will stay silent; check which habit your office has.
6

Tech Deleted

Polling trigger

In Zapier“Triggers when the technician is removed/deleted.”

Lets you know when a technician is removed from your Maidily account, whether they left or the profile was a duplicate.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to remind whoever manages access to close that person's accounts in your other tools.
Watch out
the Zap only tells; any clean-up in another app is a step you still have to add and test.
7

Job Assigment

Polling trigger

In Zapier“Triggers when a job is assigned to a technician or team.”

Goes off when a job is handed to a technician or to a team. The spelling is Maidily's own, and it is what you will see in the event list.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to send the assigned person a message in the chat tool they actually read.
Watch out
the label keeps Maidily's spelling, Assigment, so look for that exact word in the event list.
8

Job Updated

Polling trigger

In Zapier“Triggers when a job is getting updated.”

Responds to a change on an existing job in Maidily, from a new date to edited details. It is the broadest of the job triggers.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to keep an outside job sheet in step with what the office edits during the day.
Watch out
several edits can mean several runs and several tasks; on a paid plan a filter can keep only the changes that matter.
9

New Customer

Polling trigger

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

Fires each time a customer record is created in Maidily, whoever created it. This is the starting point for most onboarding Zaps.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to add the new client to your mailing list or contact book without typing them in twice.
Watch out
if the other app also feeds Maidily by hand, agree on one place where customers are first entered.
10

New Job

Polling trigger

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

Triggers on every job created in Maidily, one-off or not. Think of it as the order book of your business, read from outside.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to copy each booking into a shared calendar or a planning sheet the whole team can see.
Watch out
a big batch of jobs created at once can be slowed down by Zapier's flood protection.
11

New Quote

Polling trigger

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

Kicks in when a quote is drafted in Maidily, before the customer has answered. It tracks what goes out, not what comes back.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to build a pipeline sheet where every quote sent sits next to its later result.
Watch out
combine it with Quote Accepted and Quote Rejected in separate Zaps; one Zap can only have one trigger.
12

New Tech

Polling trigger

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

A new technician profile added to Maidily is what starts this one. A hire on the field side often means accounts to open elsewhere.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to notify the person who prepares the welcome pack, or to add a line to the staff sheet.
Watch out
test it with a real profile; Zapier needs at least one recent tech to show you what the trigger carries.
13

Paid Job

Polling trigger

In Zapier“Triggers when a job is paid through an invoice/gets charged through the job details.”

Money actually in: this one runs when a job is paid, either through an invoice or by a charge made from the job details in Maidily.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to hand each payment to the sheet or tool your bookkeeper works from.
Watch out
it covers both ways of paying, invoice or charge from the job details, so one Zap is enough to see every payment.
14

Quote Expired

Polling trigger

In Zapier“Triggers when a quote has expired.”

Spots quotes that ran past their expiry date without an answer. Those are the leads that went quiet.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to give the salesperson a last nudge to call the prospect back before they book a competitor.
Watch out
Maidily decides when a quote expires; the Zap only reports it, it does not change the deadline.
15

Quote Rejected

Polling trigger

In Zapier“Triggers when the quote is rejected.”

Starts a run when a customer turns a quote down. Losses are worth logging as carefully as wins.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to add a line to a lost-deals sheet, then review it with the team at your own pace.
Watch out
it reports the refusal, not the reason behind it; add a column for the reason and fill it after the call.
16

New Time Off Request

Polling trigger

In Zapier“Triggers when a new time off request is created.”

A technician filing a new time off request in Maidily sets this one off. It is the only trigger aimed at the team's availability.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to put the request in front of the manager in the chat app they check most.
Watch out
the trigger reports a new request, not its approval; the decision still happens in Maidily.
17

Quote Update

Polling trigger

In Zapier“Triggers when the quote details of a quote are updated.”

Watches for edits to the details of an existing quote, whatever part of it was reworked. The label reads Quote Update in the event list.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
to keep the pipeline sheet right when a quote is reworked after a site visit.
Watch out
each saved edit can be a separate run, and each run with an action is a task.
When it breaks

When a Maidily Zap breaks

Zapier links no help article to Maidily, so the traps below are the general ones. They still bite.

Most of the trouble comes from two habits: expecting a polling trigger to be immediate, and forgetting that a Zap starts from a blank slate the day you publish it. If you are stuck on a Zap that misbehaves, our Zapier troubleshooting page is the next stop.

  • Nothing from before the Zap

    A Zap only reacts to events that happen after it is switched on. Jobs, quotes and customers already in Maidily are never picked up.

  • The Zap that sets itself off

    If a Zap writes into the very place its own trigger watches, it fires again and again and burns through the task count fast.

  • 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.

  • No double runs on old items

    Zapier remembers what it has already seen on a polling trigger, so the same quote or job does not start the Zap twice.
Need help

Need help automating Maidily with Zapier?

A person reads every message.

FAQ

Maidily Zapier integration FAQ

01Is the Maidily Zapier integration free?
Yes, as long as your Zap stays at two steps. Maidily is not a premium app, so it works on the free plan, which gives 100 tasks a month and Zaps made of one trigger and one action. The catch is that Maidily only brings triggers, so your single action will always be in another app. The moment you want a filter or a second action, for example to keep only some quotes or to post a message and log a row, the Zap becomes multi-step and needs a paid plan.
02How many tasks does a Maidily Zap use?
None for Maidily itself. The trigger never costs a task, and neither does Zapier checking Maidily for new items, however often it looks. You pay for each action that succeeds in the other app: one Zap with one action uses one task per quote, job or customer it handles, and a Zap with three actions uses three. An action that fails is not counted. Keep an eye on broad triggers like Job Updated, since every edit can be a new run.
03Does Maidily send events to Zapier in real time?
No. All 17 Maidily triggers are polling triggers: Zapier goes and asks Maidily for new items on a timer, and keeps what it has not seen yet. On the free plan that check happens every 15 minutes, on Professional every 2, on Team and Enterprise every minute. The type is set by the app, not something you can switch in the editor. On a paid plan you can also run a check by hand from the editor when you are testing.
04What does it take to connect Maidily to Zapier?
A Maidily account you can sign in to, and a Zapier account. From the Apps page in Zapier you click + Add connection, search for Maidily, click Add connection, sign in to Maidily in the tab that opens and grant Zapier access. The connection is then reused by every Zap. If some of the records you want to watch belong to another user, your account needs at least read access to them, or the trigger will not see them.
05Can Zapier create jobs or quotes in Maidily?
No. On Zapier, Maidily has 17 triggers and nothing else: no action and no search. A Zap can react to a quote, a job, a customer, a tech or a time off request, but it cannot create, edit or look up anything inside Maidily. That rules out any Zap that tries to feed Maidily from a form, a CRM or a calendar. Everything the Zap does after the trigger has to happen in another app you connect.
06What if the Maidily trigger or action you need is not listed?
Then Zapier cannot offer it, because the list of operations comes from the Maidily integration itself and cannot be extended from the editor. Check first whether a nearby trigger does the job: Job Updated covers a wide range of job changes, and on a paid plan a filter can narrow it down to the cases that matter. For anything that has to write into Maidily, the step has to be done in Maidily or in a tool that offers it.
07Zapier, Make or n8n for Maidily?
Decide on what you need from Maidily, not on the brand. On Zapier you get 17 polling triggers and no way to write back, which suits Zaps that report Maidily events to other tools. If writing into Maidily matters, check whether the other platform offers Maidily at all before you compare anything else. Then weigh the volume of runs you expect and who will maintain the automation day to day.
Same platform

Other docs you might need on this stack.

Browse all integrations