Claude Planday connectorWhat Claude can do in your Planday account.
The Claude Planday connector exposes 12 tools. 6 read your schedule and team data, 3 change the rota, 3 are undocumented. Below: what Claude can check, what it can draft and publish, and how you decide when it must ask first.
Verified Trustpilot reviews · AI, automation & growth agency
The rota, answered like a colleague would
Running a restaurant, a shop or a care home on Planday means constant small questions: who's on Saturday, which rest rule applies, what absence policies exist. With the connector, you ask Claude in plain words, it reads the answer from your Planday workspace, and it can draft and publish shifts when you tell it to.
See who's working. Ask for next week's shifts in the Kitchen department and list_shifts returns them by department, employee or date, so Claude can tell you where the gaps are.
Cover a no-show. David can't come in on Friday. assign_shift hands that shift to Anna, and Claude walks you through it rather than changing the schedule without asking.
Build next week, safely. create_draft_shift sets up new shifts as drafts, invisible to the team, and publish_draft_shifts only makes them visible when you say so. Before booking someone, list_working_time_rules shows which rules apply in your portal.
Now the part the directory sheet leaves out. Three listed tools have no description anywhere, so this page says nothing about what they do. Planday states that Claude won't delete a shift or an employee. Long lists come back cut short. And nothing runs by itself when someone calls in sick. For that kind of background job, an automation tool fits, which is a different trade; the Integrations hub gathers that side.
The vocabulary in one minute
Five words you'll meet while plugging Planday in.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work on it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs on its own; the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Given once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it finishes something that changes your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Planday.
Plug Planday into Claude in three steps
- 01
Find Planday in Claude
In Claude's settings, open Customize, then Connectors, and look for Planday in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first, then each member signs in.
- 02
Start the connection
Click Connect on the Planday row, then sign in to Planday in the window Planday opens itself. If that link ever breaks later on, use Disconnect and plug it back in.
- 03
Read the authorization screen
Read the authorization screen before you accept. It belongs to Planday, not to Claude, so Planday decides what the access covers. You can withdraw that access later on the Planday side too.
The 12 tools, sorted by what they do
Planday gives Claude 12 tools: 6 that read your account, 3 that change something in it, and 3 no official source describes.
Three groups: what Claude reads, what it changes on the rota, and what no official source describes. The names stay exactly as Claude shows them.
- 6 read
- 3 write
- 3 not documented
What Claude reads (6)
6 toolsSix tools that look into your schedule, team and rules without changing them.
get_working_time_rule
Opens a single working-time rule from your Planday portal, so Claude can explain who it covers. Planday's own example asks which employee groups the daily rest rule applies to.
list_absence_policies
Lists the absence policies your organization uses in Planday. Claude can then explain them in plain words to someone who asks.
list_departments
Returns the department structure of your Planday workspace. It gives Claude the map it needs before looking for people or shifts in a given area.
list_employees
Looks up your staff, with their employee groups and roles. Claude can answer "who works where, doing what" without you opening every profile.
list_shifts
Pulls shifts by department, by employee or by date. This is the tool behind "what's on the schedule today" and "who's on the bar Saturday night".
list_working_time_rules
Lists every working-time rule set up in your portal. It is the overview, before drilling into a single rule with the other tool.
What Claude changes (3)
3 toolsThree tools that change your rota. No source gives them their own confirmation rule: the general rule below applies.
assign_shift
Approval: see the ruleGives an existing shift to a specific employee. Planday's example is David dropping out on Friday and the shift going to Anna instead.
create_draft_shift
Approval: see the ruleCreates a new shift as a draft, with a time, a department and possibly an employee. Planday says drafts stay invisible to your team until publication.
publish_draft_shifts
Approval: see the ruleMakes draft shifts visible to your team. According to Planday, this only happens when you ask Claude to publish, never behind your back.
Undocumented (3)
3 toolsThe directory publishes these three names and nothing else. No official text says what they do, and a name is not enough to guess.
approve_shift_swap
This name sits in the directory's tool list, and nothing more is published about it. Neither Planday's help article nor any Claude page describes it, so this page stops there.
list_absence_accounts
Listed by name on the directory sheet, without a single sentence from Planday or Anthropic explaining it. No help article and no directory text mentions it, so there is nothing more to report.
profile
One more name the directory shows with no official description attached. No source says whether it reads or changes anything, and this page won't guess from a single word.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before each action it carries out on an account for you. The request shows up in the chat, at the moment it matters.
Planday adds a practical layer: after connecting, its tools appear under Tool permissions, split into read-only and write, and for each one you choose whether Claude uses it freely, asks first, or is not allowed. Planday's suggested start is to let reads run and ask before anything that changes the schedule. On Team or Enterprise, owners can also restrict what the connector may do for everyone, above any personal setting.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. The connector-by-connector answer is published nowhere: it is a real gap in the catalogue, not a miss in our research.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before each member can sign in. For the current state of this one, check the Planday sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when someone calls in sick, a swap is requested or a rule is breached.
Only Planday documents this connector, and the directory describes it as early access; no Claude help page covers it. The directory badge is not a security audit, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as announced. Three of the twelve tools remain undocumented. For another connector that touches team data, see the Claude bamboohr connector.
Need help connecting Planday to Claude?
A person reads every message.
