[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Weekly Planity booking report

> Get last week's Planity bookings, online share, new clients and no-shows against the week before, ready in your inbox or Slack on Monday.

Source: https://cotlet.dev/integrations/planity-api-mcp-server/weekly-booking-report

Each Monday the owner opens the statistics, switches tabs for services and staff, and copies the numbers into a message for the team.

Cotlet does it in your own Planity account with get\_appointment\_stats and list\_no\_shows, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=planity) [All Planity tools](https://cotlet.dev/integrations/planity-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Planity do this on its own?

Planity shows these statistics on screen and sends or prints a copy by hand (checked 23 Oct 2026). Appointment export is a separate feature that Planity support switches on after an email, and it has no API. Nothing sends the statistics on a schedule.

## How you do it in Planity today

1. The owner opens the Admin tab, then "Statistiques RDV", then "Indicateurs clés".
2. The owner picks the period from the menu at the top right: day, week, month, year or a custom range.
3. The tabs "Prestations", "Collaborateurs", "RDV" and "RDV pas venus" each show one cut of the same period, and the compare option sets it against a previous one.
4. The "Exporter" and "Imprimer" buttons give an email or paper copy of the statistics.
5. Every Monday the owner repeats these clicks and types the figures into a message, tab by tab.

## How to weekly Planity booking report

Prompt

```
Every Monday, report last week's Planity bookings against the week before: total, online share, new clients, no-shows, per service and per staff member.
```

1. 01  
### Pull both weeks at once  
get\_appointment\_stats runs with last week's dates and compare\_previous true, so one call returns the week and the week before. Totals, online and in-salon bookings, new clients and the no-show count come from the tabs Indicateurs clés, RDV and RDV pas venus.
2. 02  
### Name the busiest service and staff member  
The agent reads by\_service and by\_staff and reports the top two of each. It leaves out a service with no appointments instead of listing zeros.
3. 03  
### Explain the no-shows  
When no\_shows is above zero, list\_no\_shows returns the appointments behind the count, with client and staff member, so the report says who and not only how many.
4. 04  
### Keep the revenue honest  
estimated\_revenue is Planity's estimate from bookings in the agenda. The agent labels it as an estimate and does not present it as takings; the cash register is not read.
5. 05  
### Deliver it  
The agent writes the report in this chat, or to Slack or email through your n8n or script, and nothing in Planity changes. It runs every Monday on a schedule.

### What you get back

Example data

```
12 to 18 Oct: 154 appointments (141 the week before, +13)
Online 96 (62.3%), in salon 58
New clients 21, no-shows 3 (Léa Martin twice)
Top services: Coupe homme 55, Coupe femme 41
Staff: Amélie 62, Lucas 51, Inès 41
Estimated revenue 6120 (booking estimate)
```

### Other ways to ask

- On the first of each month, report the whole past month against the month before.
- Report only online bookings per service for the last 30 days.
- Tell me on Friday if this week is running below last week by more than 10 appointments.

## What Planity allows, and what to know first

- All Statistiques RDV figures come from the appointments recorded in the agenda for the chosen period.
- The Prestations and Collaborateurs tabs show an estimated revenue based on bookings in the agenda, and Planity also shows a forecast revenue.
- The tab "RDV" shows online and in-salon bookings and the online booking rate as a percentage.
- Since 4 June 2026 you can create your own tags, attach them to services and get custom statistics; this report does not read them.
- Appointment export, added on 22 July 2026, is off by default; the admin asks for it by email from the account's admin address to contact@planity.com.

Every tool here only reads, so it can run weekly from n8n, Make, Zapier or cron without waiting for your OK.

Sources: [Planity Help: Where to find my appointment statistics](https://support.planity.com/hc/fr/articles/27962473121682-O%C3%B9-retrouver-les-statistiques-de-mes-rendez-vous) · [Planity Help: All new features](https://support.planity.com/hc/fr/articles/29418472937234-Toutes-les-nouveaut%C3%A9s)

## Call get\_appointment\_stats from a script

curl

```
curl "https://cotlet.dev/api/v1/planity/appointment-stats?date_from=2026-10-12&date_to=2026-10-18&compare_previous=true" \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

Example response

```
{
"date_from": "2026-10-12",
"date_to": "2026-10-18",
"appointments": 154,
"online": 96,
"in_salon": 58,
"online_rate_percent": 62.3,
"new_clients": 21,
"no_shows": 3,
"estimated_revenue": 6120,
"by_service": [
{
"service": "Coupe homme",
"appointments": 55
},
{
"service": "Coupe femme",
"appointments": 41
},
{
"service": "Brushing",
"appointments": 35
},
{
"service": "Couleur",
"appointments": 23
}
],
"by_staff": [
{
"staff": "Amélie",
"appointments": 62
},
{
"staff": "Lucas",
"appointments": 51
},
{
"staff": "Inès",
"appointments": 41
}
],
"previous": {
"date_from": "2026-10-05",
"date_to": "2026-10-11",
"appointments": 141,
"online": 83,
"in_salon": 58
}
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is planity\_read → get\_appointment\_stats. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/planity-api-mcp-server.md#automations)

## Planity tools this automation uses

__Cotlet Planity tools used to weekly Planity booking report__
| Tool | Parameters |
| ----------------------- | --------------------------------------- |
| get\_appointment\_stats | date\_from, date\_to, compare\_previous |
| list\_no\_shows | date\_from, date\_to, staff\_id |

[All 14 Planity tools with descriptions](https://cotlet.dev/integrations/planity-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Planity to Cotlet?

Yes. You sign in to Planity yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Planity once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Planity automations

- [Follow up Planity no-shows and block repeat offenders](https://cotlet.dev/integrations/planity-api-mcp-server/follow-up-no-shows.md)
- [Block staff time off in the Planity agenda](https://cotlet.dev/integrations/planity-api-mcp-server/block-staff-time-off.md)
- [Planity API and MCP server: every tool](https://cotlet.dev/integrations/planity-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Planity.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Planity.

[Sign up free](https://cotlet.dev/app/signup?app=planity)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
