Live

ZenMaid logo

ZenMaid API and MCP server

zenmaid.com

ZenMaid has no public API: its help center says it does not support any kind of public API, including REST endpoints, webhooks or programmatic data access (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for ZenMaid with 13 endpoints (5 read, 8 write): your AI agent signs in as you and does the work.

Endpoints
13 5 read, 8 write
Updated
How Cotlet connects your agent to ZenMaid
  1. Your agent

    Claude Code, Codex, Cursor or a script

  2. Cotlet

    MCP server and REST API · 13 endpoints

    cotlet.dev/mcp/v1

  3. ZenMaid logo

    ZenMaid

    Signed in as you on zenmaid.com

You sign in once. We never store your password.

Official API

Does ZenMaid have an official API?

ZenMaid has no public API: its help center says it does not support any kind of public API, including REST endpoints, webhooks or programmatic data access (checked 11 Oct 2026). The only official route is Zapier, which has four triggers and no ZenMaid actions.

What ZenMaid's own tools do compared with Cotlet
Task ZenMaid official Cotlet
Read the schedule for a day or range No Yes
Look up a contact and their appointments No Yes
Book an appointment No Yes
Reschedule an appointment No Yes
Assign cleaners to an appointment No Yes
Cancel an appointment and notify people No Yes
Find unpaid appointments and mark them paid No Yes
React to new or changed bookings Partly Zapier triggers send new customers and booked, cancelled or updated appointments out Yes

Sources: ZenMaid help: How to create integrations and automations · ZenMaid: Zapier triggers · ZenMaid feedback board: request for a public API or MCP server · ZenMaid help: How to mark appointments as paid · ZenMaid help: How to cancel all appointments on a day in bulk · ZenMaid help: How to replace a cleaner on all appointments

Common use cases

What can an AI agent do in ZenMaid?

Cotlet is best for cleaning companies and their automation builders who need an agent to read the schedule, book, reschedule and cancel jobs without running or fixing a server.

  • Find appointments with no cleaner Runs: Daily

    What does tomorrow's schedule look like, and which appointments still have no cleaner? Suggest who is free. Your agent calls list_appointments and list_cleaners.

  • Book a cleaning appointment

    Book the Millers for a 3-hour deep clean next Friday at 9:00 with Ana. Your agent calls list_contacts, list_cleaners and create_appointment.

  • Reassign a sick cleaner's appointments

    Ana called in sick for Thursday. Find every ZenMaid appointment she has that day, suggest a free cleaner for each one, and after I approve, reassign them and text the customers who is coming instead. Your agent calls list_appointments, list_cleaners, get_appointment, assign_cleaners and send_message.

  • Reschedule or cancel a day of appointments

    An ice storm is coming Friday. Move every ZenMaid appointment on Friday to the same time next Monday where the cleaner is free, cancel the rest, keep the notes, and tell the customers. Your agent calls list_appointments, get_appointment, reschedule_appointment, add_note, cancel_appointment and send_message.

  • Reconcile offline payments and chase unpaid jobs Runs: Weekly

    Here are this week's Venmo and Zelle payments. Mark the matching ZenMaid appointments as paid, then list who still owes us and send them a friendly payment reminder after I check the list. Your agent calls list_appointments, get_contact, mark_appointment_paid and send_message.

  • Cancel appointments and notify clients

    Cancel everything on Friday because of the storm and notify the clients and cleaners. Your agent calls list_appointments and cancel_appointment.

Endpoints

What is the ZenMaid API?

Cotlet's ZenMaid API exposes 13 endpoints for your own ZenMaid account: list appointments, get appointment, list contacts, get contact, list cleaners, create contact, create appointment, reschedule appointment, assign cleaners, add note, cancel appointment, mark appointment paid and send message. The list_appointments endpoint returns appointments in a date range with customer, time, cleaners, price and paid flag. Each endpoint takes simple JSON inputs like appointment_id, contact_id or query and works both as an MCP tool for agents and as a REST call for scripts.

All endpoints · 13 total

missing one? request an endpoint

  • POST

    list_appointments

    read

    Returns appointments between two dates, in date and time order. An appointment with nobody assigned has an empty cleaners list. Filter by payment status to find unpaid jobs, or search by customer name, cleaner name, street address or a custom field, as ZenMaid's List View does. Cancelled appointments are included only when you ask for them.

    POST /api/v1/zenmaid/list_appointments

    Input

    Input: list_appointments
    Parameter Type Description
    from required date First day of the range.
    to required date Last day of the range.
    query string Customer name, cleaner name, street address or custom field value.
    paid enum all, paid or unpaid. Default: all.
    include_cancelled boolean Also return cancelled appointments. Default: false.
    limit integer 1 to 100. Default: 50.
    cursor string Next page cursor from the previous call.

    Example response

    {
      "appointments": [
        {
          "appointment_id": "a_993102",
          "contact": "Sample Customer",
          "date": "2026-10-16",
          "start_time": "09:00",
          "end_time": "12:00",
          "cleaners": [],
          "price": "180.00",
          "paid": false
        },
        {
          "appointment_id": "a_993140",
          "contact": "Sample Household",
          "date": "2026-10-16",
          "start_time": "13:00",
          "end_time": "15:00",
          "cleaners": [
            "Cleaner A"
          ],
          "price": "120.00",
          "paid": false
        }
      ],
      "next_cursor": null
    }
  • POST

    get_appointment

    read

    Returns one appointment with the service address, service type, whether it belongs to a recurring service, work items, billing (price before tax, tip, paid flag) and its appointment and customer notes. Use it before changing or cancelling an appointment.

    POST /api/v1/zenmaid/get_appointment

    Input

    Input: get_appointment
    Parameter Type Description
    appointment_id required string Appointment ID from list_appointments.

    Example response

    {
      "appointment_id": "a_993102",
      "contact": {
        "contact_id": "c_48213",
        "name": "Sample Customer"
      },
      "address": "12 Sample Street, Springfield",
      "date": "2026-10-16",
      "start_time": "09:00",
      "end_time": "12:00",
      "service_type": "Deep Clean",
      "recurring": false,
      "cleaners": [],
      "work_items": [
        "Kitchen",
        "Bathrooms"
      ],
      "billing": {
        "price": "180.00",
        "tip": "0.00",
        "paid": false
      },
      "notes": [
        {
          "visibility": "public",
          "body": "Gate code is on the contact."
        }
      ]
    }
  • POST

    list_contacts

    read

    Searches contacts by name, email, phone or address. Status is one of ZenMaid's four: lead, one_time_customer, recurring_customer or former_customer. ZenMaid sets it from the appointments on the calendar, so a new contact stays a lead until someone books them.

    POST /api/v1/zenmaid/list_contacts

    Input

    Input: list_contacts
    Parameter Type Description
    query string Name, email, phone or address to search.
    status enum lead, one_time_customer, recurring_customer or former_customer.
    limit integer 1 to 100. Default: 50.
    cursor string Next page cursor from the previous call.

    Example response

    {
      "contacts": [
        {
          "contact_id": "c_48213",
          "name": "Sample Customer",
          "email": "customer@example.com",
          "phone": "+1 555 0100",
          "address": "12 Sample Street, Springfield",
          "status": "lead"
        }
      ],
      "next_cursor": null
    }
  • POST

    get_contact

    read

    Returns one contact profile: addresses, customer notes (public and private), contact custom fields, revenue to date, unpaid balance and a list of their appointments, newest first. Private notes are returned only to owner and office manager accounts.

    POST /api/v1/zenmaid/get_contact

    Input

    Input: get_contact
    Parameter Type Description
    contact_id required string Contact ID from list_contacts.

    Example response

    {
      "contact_id": "c_48213",
      "name": "Sample Customer",
      "email": "customer@example.com",
      "phone": "+1 555 0100",
      "status": "one_time_customer",
      "revenue_to_date": "180.00",
      "unpaid_balance": "0.00",
      "notes": [
        {
          "visibility": "private",
          "body": "Prefers morning visits."
        }
      ],
      "appointments": [
        {
          "appointment_id": "a_993102",
          "date": "2026-10-16",
          "paid": false
        }
      ]
    }
  • POST

    list_cleaners

    read

    Returns the cleaners and teams in your account with their IDs, which assign_cleaners and create_appointment need. Inactive staff are left out unless you ask for them.

    POST /api/v1/zenmaid/list_cleaners

    Input

    Input: list_cleaners
    Parameter Type Description
    include_inactive boolean Also list inactive staff. Default: false.

    Example response

    {
      "cleaners": [
        {
          "cleaner_id": "cl_1207",
          "name": "Cleaner A",
          "type": "cleaner",
          "active": true
        },
        {
          "cleaner_id": "cl_1344",
          "name": "Cleaner B",
          "type": "cleaner",
          "active": true
        },
        {
          "cleaner_id": "tm_21",
          "name": "Team One",
          "type": "team",
          "active": true
        }
      ]
    }
  • POST

    create_contact

    write

    Adds a contact profile. ZenMaid starts a new contact as a Lead until an appointment is booked. It reaches no one and is undone in one call, so it does not ask for your OK.

    POST /api/v1/zenmaid/create_contact

    Input

    Input: create_contact
    Parameter Type Description
    first_name required string First name.
    last_name string Last name.
    email string Email address.
    phone string Phone number.
    address string Service address.
    notes string Customer note, public by default.

    Example response

    {
      "contact_id": "c_48290",
      "name": "Sample Lead",
      "email": "lead@example.com",
      "phone": "+1 555 0111",
      "status": "lead"
    }
  • POST

    create_appointment

    write

    Books an appointment for an existing contact with a start and end time. Leave cleaner_ids empty to keep it unassigned, and price empty to let ZenMaid calculate it if your account is set up for that. A recurring frequency creates a recurring service. The contact becomes a customer once the appointment is on the calendar. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/zenmaid/create_appointment

    Input

    Input: create_appointment
    Parameter Type Description
    contact_id required string Contact ID from list_contacts.
    date required date Day of the appointment.
    start_time required string Start time, HH:MM.
    end_time required string End time, HH:MM.
    service_type string Service type as set up in your account.
    frequency string one_time or a recurring frequency from your account. Default: one_time.
    cleaner_ids string[] Cleaner or team IDs from list_cleaners. Empty leaves it unassigned.
    price string Price before tax. Empty lets ZenMaid calculate it if configured.
    notes string Appointment note.

    Example response

    {
      "appointment_id": "a_993102",
      "contact": "Sample Customer",
      "date": "2026-10-16",
      "start_time": "09:00",
      "end_time": "12:00",
      "service_type": "Deep Clean",
      "cleaners": [
        "Cleaner A"
      ],
      "price": "180.00",
      "paid": false
    }
  • POST

    reschedule_appointment

    write

    Moves one appointment, as the Reschedule window does in ZenMaid. It keeps work items, price and status. The length stays the same unless you pass end_time. One-time appointment notes do not carry over, so add them again with add_note. For a recurring appointment, apply_to chooses this one or all future appointments. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/zenmaid/reschedule_appointment

    Input

    Input: reschedule_appointment
    Parameter Type Description
    appointment_id required string Appointment ID from list_appointments.
    date required date New day.
    start_time required string New start time, HH:MM.
    end_time string New end time, HH:MM. Default: keeps the length.
    recalculate_price boolean Recalculate the amount owed for the new length. Default: false.
    apply_to enum this_appointment or all_future, for recurring appointments. Default: this_appointment.

    Example response

    {
      "appointment_id": "a_993102",
      "date": "2026-10-19",
      "start_time": "10:00",
      "end_time": "13:00",
      "price": "180.00",
      "price_recalculated": false
    }
  • POST

    assign_cleaners

    write

    Replaces the cleaners on one appointment. It does not deactivate a cleaner and does not touch the default cleaner of a recurring service. One more call undoes it, so it does not ask for your OK.

    POST /api/v1/zenmaid/assign_cleaners

    Input

    Input: assign_cleaners
    Parameter Type Description
    appointment_id required string Appointment ID from list_appointments.
    cleaner_ids required string[] Cleaner or team IDs from list_cleaners.

    Example response

    {
      "appointment_id": "a_993102",
      "cleaners": [
        "Cleaner B"
      ]
    }
  • POST

    add_note

    write

    Adds an Appointment Note or a Customer Note, as in ZenMaid. A public note goes on the work orders sent to cleaners; a private note is visible only to owners and office managers. It reaches no one and is undone by editing the note, so it does not ask for your OK.

    POST /api/v1/zenmaid/add_note

    Input

    Input: add_note
    Parameter Type Description
    appointment_id string Appointment to note. Give this or contact_id.
    contact_id string Contact to note.
    body required string Note text.
    visibility enum public or private. Default: public.

    Example response

    {
      "note_id": "n_5521",
      "appointment_id": "a_993102",
      "visibility": "public",
      "body": "Moved one day because of rain."
    }
  • POST

    cancel_appointment

    write

    Sets the status to Cancelled and keeps the record; it never deletes. notify takes none, client, cleaner or both, the same choices ZenMaid offers when you cancel. A cancelled appointment may be hidden by the calendar filters. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/zenmaid/cancel_appointment

    Input

    Input: cancel_appointment
    Parameter Type Description
    appointment_id required string Appointment ID from list_appointments.
    notify enum none, client, cleaner or both. Default: none.

    Example response

    {
      "appointment_id": "a_993102",
      "status": "Cancelled",
      "notified": [
        "client",
        "cleaner"
      ]
    }
  • POST

    mark_appointment_paid

    write

    Marks one appointment as paid, like the Mark as paid button in its Billing section. It never charges the card on file. Appointments paid by card cannot be changed this way. The customer's Revenue To Date and Unpaid Balance update. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/zenmaid/mark_appointment_paid

    Input

    Input: mark_appointment_paid
    Parameter Type Description
    appointment_id required string Appointment ID from list_appointments.

    Example response

    {
      "appointment_id": "a_991870",
      "paid": true,
      "total": "120.00"
    }
  • POST

    send_message

    write

    Sends from a template under Type of communication, as the Send Text/Email action does. You can replace the template text with your own. ZenMaid only sends if the contact has an email address or phone number on file, and manual texts count toward your SMS usage. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/zenmaid/send_message

    Input

    Input: send_message
    Parameter Type Description
    appointment_id string Appointment the message is about. Give this or contact_id.
    contact_id string Contact to message.
    template required string Communication template name.
    channels enum email, sms or both. Default: email.
    body string Replace the template text with your own.

    Example response

    {
      "appointment_id": "a_993102",
      "template": "Appointment Reminder",
      "channels": [
        "email",
        "sms"
      ],
      "sent": true
    }

Setup

How do I connect ZenMaid to Claude Code, Codex or Cursor?

Connecting ZenMaid takes three steps: request access, sign in to ZenMaid once, then add one MCP server or call the REST API with the same key.

Connect ZenMaid over MCP

  1. 1

    Create an account

    Sign up and add ZenMaid in the console. Your API key is there too.

  2. 2

    Sign in to ZenMaid once

    Open the connect page from the console and sign in to ZenMaid the way you always do. We keep the session, never your password, and you can revoke it anytime.

  3. 3

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
      https://cotlet.dev/mcp/v1 \
      --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
      "mcpServers": {
        "cotlet": {
          "url": "https://cotlet.dev/mcp/v1",
          "headers": {
            "Authorization": "Bearer ${COTLET_API_KEY}"
          }
        }
      }
    }
    Codex
    # ~/.codex/config.toml
    [mcp_servers.cotlet]
    url = "https://cotlet.dev/mcp/v1"
    bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

  4. 4

    Ask your agent

    Prompt

    What does tomorrow's schedule look like, and which appointments still have no cleaner? Suggest who is free.

    Ask in plain words. Your agent finds the ZenMaid tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

Call ZenMaid over REST

  1. 1

    Export your API key

    Shell

    export COTLET_API_KEY="cotlet_..."

    Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

  2. 2

    Call a tool

    curl

    curl https://cotlet.dev/api/v1/zenmaid/create_appointment \
      -H "Authorization: Bearer $COTLET_API_KEY" \
      -H "Content-Type: application/json" \
      -d '{"contact_id":"c_48213","date":"2026-10-16","start_time":"09:00","end_time":"12:00","service_type":"Deep Clean","frequency":"one_time","cleaner_ids":["cl_1207"]}'

    Every tool is a POST endpoint at /api/v1/zenmaid/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

  3. 3

    Read the result

    Example response · create_appointment

    {
      "appointment_id": "a_993102",
      "contact": "Sample Customer",
      "date": "2026-10-16",
      "start_time": "09:00",
      "end_time": "12:00",
      "service_type": "Deep Clean",
      "cleaners": [
        "Cleaner A"
      ],
      "price": "180.00",
      "paid": false
    }

    You get plain JSON back, ready for your script. A failed call costs nothing.

Why Cotlet

Why use Cotlet for ZenMaid? Hosted, safe and kept working.

  • Built for agents

    • One MCP server for every app you connect.
    • The same tools as a REST API for scripts and cron jobs.
    • Works with Claude Code, Codex and Cursor.
  • Your login stays yours

    • You sign in to ZenMaid yourself. We keep only the session, encrypted with AES-256.
    • The model never sees a login.
    • No stored passwords, no CAPTCHA solving, no MFA bypass.
  • You stay in control

    • Pick read only, or read and write.
    • Anything that reaches other people waits for your OK, unless you switch it off per tool.
    • Revoke access in one click.
  • Kept working for you

    • We test every integration daily.
    • When ZenMaid changes, the tool pauses until we fix it.
    • Failed calls cost nothing.

Alternatives

Is there a ZenMaid MCP server on GitHub?

Zapier is the only official way to connect ZenMaid. It has four triggers that send new customers and appointment changes into other apps, and no action that changes anything in ZenMaid.

Cotlet compared with a Zapier
Zapier Cotlet
Setup Connect ZenMaid in Zapier and build a Zap per workflow Request access, sign in to ZenMaid once, add one MCP server or API key
Reading data Only events as they happen; no schedule or contact lookup Schedule, contacts, cleaners and unpaid jobs on demand
Write actions None in ZenMaid Book, reschedule, assign, cancel, mark paid, message; each step that reaches a customer asks for your OK
When ZenMaid changes ZenMaid keeps its triggers working Our team tests daily and fixes the tools; failed calls are free
Your ZenMaid session Zapier connection Encrypted in an EU vault, limited to the actions you allow, revoked in one click
When the session expires Reconnect the app in Zapier Your agent gets a link to sign in again
Price Zapier plan; paid Zapier plan for some apps Free 7-day trial with 5,000 credits, then credits per call

Which one fits you

Pick Cotlet if

  • you are not a developer, or you do not want to maintain a server
  • you need it to keep working when ZenMaid changes, without checking it yourself
  • your agent or a script should run it on a schedule, also while your computer is off

Pick an open-source server if

  • you are comfortable installing, updating and fixing it yourself
  • you want the session to stay on your own computer
  • you only need it now and then, from one MCP client

For AI agents

Cotlet for ZenMaid in plain text The facts on this page in one block: status, endpoints, access, pricing, contact.

Endpoint health

verified 2h ago

  • list_appointments passing
  • get_appointment passing
  • list_contacts passing
  • get_contact passing
  • list_cleaners passing

+ 8 more endpoints

13/13 passing latest check self-healing

zenmaid.txt

ZenMaid has no public API: its help center says it does not support any kind of public API, including REST endpoints, webhooks or programmatic data access (checked 11 Oct 2026). The only official route is Zapier, which has four triggers and no ZenMaid actions.
Cotlet provides a hosted MCP server and REST API for ZenMaid: 13 tools (5 read, 8 write).
Access       Request access at https://cotlet.dev/app/signup?app=zenmaid; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/zenmaid
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_appointments, get_appointment, list_contacts, get_contact, list_cleaners, create_contact, create_appointment, reschedule_appointment, assign_cleaners, add_note, cancel_appointment, mark_appointment_paid, send_message
Confirm      create_appointment, reschedule_appointment, cancel_appointment, mark_appointment_paid, send_message (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/zenmaid-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=zenmaid (ZenMaid is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to ZenMaid once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted ZenMaid server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to ZenMaid in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following ZenMaid's terms; Cotlet is not affiliated with ZenMaid.
Full page as Markdown

Automations

Can ZenMaid automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a ZenMaid connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to find appointments with no cleaner, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

Where to run ZenMaid automations through Cotlet, and how to schedule them
Where How to connect How to schedule
Your AI agent Add https://cotlet.dev/mcp/v1 with your API key. A scheduled agent run, for example a Claude Code routine.
n8n MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/zenmaid/{tool}. Schedule Trigger node.
Make HTTP module: POST https://cotlet.dev/api/v1/zenmaid/{tool} with an Authorization: Bearer header and a JSON body. Scenario schedule.
Zapier Webhooks by Zapier: POST https://cotlet.dev/api/v1/zenmaid/{tool} with the same header and body. Schedule by Zapier trigger.
Your own script POST https://cotlet.dev/api/v1/zenmaid/{tool} with your API key. cron or GitHub Actions.

Pricing & limits

How much does the ZenMaid API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the ZenMaid API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

Cotlet plan sizes: price, monthly credits and price per credit
Size Price Credits / month Per credit
Solo $29/mo 3,000 about $0.0097
Pro $99/mo 12,000 about $0.0083
Agency $299/mo 40,000 $0.0075

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the Authorization: Bearer header.

About Cotlet

How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own ZenMaid account.

Company details
The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. Terms
Your session
You sign in to ZenMaid yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a ZenMaid tool you allowed. When it expires, your agent gives you a link to sign in again. Security
Revoking access
Disconnect ZenMaid in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
What we never do
Store passwords, solve CAPTCHAs or bypass MFA.
ZenMaid's terms
You use your own ZenMaid account and stay responsible for following ZenMaid's terms. Cotlet is independent and not affiliated with ZenMaid. Terms
Contact
Questions about the company, security or an app: contact@cotlet.dev
About Cotlet

Frequently asked questions

How do I get access?

Request access and pick ZenMaid. Cotlet reviews each request and emails you your API key.

Do I need to be technical?

No. You sign in to ZenMaid once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

Is a hosted server safe? My ZenMaid session would leave my computer.

Cotlet keeps your ZenMaid session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

Which ZenMaid account does it need?

An owner or office manager login. Cleaners cannot mark appointments as paid in ZenMaid, and private notes are visible only to owners and office managers.

Does it work with the Booking Form?

No. The Booking Form is how your customers book themselves; Cotlet works with the schedule in your own account. ZenMaid's Zapier trigger for booking form submissions stays available for that.

Can my agent post or send messages in ZenMaid without asking me?

No. Every call to create_appointment, reschedule_appointment, cancel_appointment, mark_appointment_paid or send_message waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_contact, assign_cleaners, add_note runs without asking, because it sends nothing to anyone and one call undoes it.

Can I use the ZenMaid API in n8n?

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/zenmaid/{tool} from the HTTP Request node.

Give your agent access to ZenMaid.

Request access and pick it. We review each request and email you your API key. Free 7-day trial with 5,000 credits, no card needed.