Claude + Homebase: What the Integration Can (and Can't) Do in 2026
Short answer: there’s no ready-made way to connect Claude to Homebase. Anthropic doesn’t offer a Homebase connector, and Homebase (the employee-scheduling app for shift-based businesses — not the UK home-improvement chain) hasn’t built one. Homebase does publish API documentation, so a connection is technically possible — but access isn’t a self-serve toggle in your settings the way it is with some tools. You request API access from Homebase, and even once you have it, Claude only does something while you’re in the chat asking. It can’t watch your schedule and act on its own.
Here’s the plain-English version: what’s possible, what it takes, where it stops, and what to use if you want Homebase work to happen without you.
Homebase has an API — but it’s request-based, not a settings toggle
This is the part worth getting right, because it sits in the middle of the pack. Some scheduling tools (Deputy, 7shifts) let any admin mint their own API token from a settings page. Homebase is a step more gated: it publishes developer docs, but you have to request access from Homebase rather than flip a switch yourself. In practice that means it’s oriented toward approved integrations, and getting a key is a conversation with Homebase, not a self-serve click.
So even before Claude enters the picture, there are two walls:
- Getting access is a request, not a self-serve step. You ask Homebase for API access; you don’t generate a key on your own the way you would with a fully open platform.
- A key is not a Claude connection. Even once you have access, someone technical still has to build and run a small connector — an “MCP server,” in the jargon — that bridges Claude and Homebase. Anthropic doesn’t provide one, Homebase doesn’t publish one, and there’s no polished free version to install. Because it uses a key you paste in, any such setup lives on Claude Desktop or Claude Code, not on claude.ai in your browser.
What a Claude + Homebase connection would actually do
Say you get access and a developer builds that connector. What you get is a smart assistant inside a chat window: you ask, it answers. You could say “pull this week’s Homebase schedule and tell me who’s approaching overtime,” or “summarize last week’s timesheets and flag the late clock-ins,” and it would. That’s genuinely useful for reading your labor data and drafting from it.
What you would not get is anything that runs by itself — and for a business built on shift coverage, that’s the part that counts.
The limit that matters: Claude only acts when you ask
Everything Claude does happens inside a conversation you start. Three consequences worth being blunt about:
- It never notices anything. Claude can’t see that a shift just opened up, or that someone’s about to tip into overtime, and act on it. Nothing happens unless you open a chat and ask.
- Close the chat and it stops. Claude reads a schedule when you ask. It doesn’t sit on your roster watching for gaps. The moment you’re done, it’s done.
- “Scheduled” isn’t really automatic. The closest Claude gets to running on its own is a scheduled task — but it fires on a fixed clock you set, not when a shift changes or someone clocks in, and it has no inbox to receive work. That’s not an event-driven manager.
What about email — can’t Claude just message the team? Out of the box, no: Claude’s built-in email (both Gmail and Outlook) only drafts, it doesn’t send — you still hit send yourself. A developer could build sending in too, but that’s one more thing to maintain, and it still only happens while you’re in the chat.
Worth knowing: Homebase already has its own AI built in — a Scheduling Assistant that drafts schedules from availability and shift history, now used by tens of thousands of small businesses. Claude doesn’t replace that; it’s a general assistant you’d point at your data.
Bottom line: Claude with a custom build is great for “help me pull and read this,” and simply not built for “cover every open shift and warn me on overtime automatically.”
If you want Homebase work to happen on its own: Carly
The moment you want something to happen around Homebase without you in the chat — a manager pinged when a shift goes unfilled, a reminder when someone misses a clock-out, a weekly labor recap — you’ve walked past what Claude is for.
Here’s where the honesty ladder matters. Claude dead-ends at Homebase’s request-based gate: no self-serve key, no ready connector, no acting on events. Carly clears it two ways. If you’ve been granted Homebase API access, you paste that key on carlyassistant.com/integrations and Carly works against it directly. If you haven’t, Carly runs the flows around Homebase honestly — through email, calendar, and exported reports — so the automation still happens:
- When a shift goes unfilled, Carly emails eligible staff to offer it and escalates to the manager if it stays open.
- When someone misses a clock-out, Carly nudges them and flags the timesheet before payroll runs.
- When a team member crosses into overtime, Carly emails the manager the names and hours so it’s caught early.
- Every Monday, Carly rolls the week’s hours and labor cost into one recap and sends it to owners on schedule.
Carly drafts and sends across Gmail and Outlook, updates records, and manages tasks — through 200+ native integrations or your own API key (see integrations). AI agents start at $35/month.
Claude vs Carly for Homebase
| Claude (with a custom build) | Carly | |
|---|---|---|
| Look up schedules & summarize timesheets | Yes (once granted access) | Yes |
| Acts the moment something happens (unfilled shift, missed clock-out) | No | Yes |
| Chases open shifts on its own | No | Yes |
| Keeps working when your laptop is closed | No | Yes (cloud) |
| Sends the emails itself, not just drafts | No — drafts only | Yes |
| Works from email/exports when there’s no key | Manual paste | Yes (automated) |
| What it takes to set up | Request Homebase API access + build & run a connector | Paste your key, or use the email/calendar flows |
| Pricing | Claude Pro $20 / Max $100–$200, plus the build | AI agents from $35/mo |
Claude is a Homebase lookup inside a chat window, if you’re granted access. Carly is a teammate that acts on open shifts, clock-outs, and overtime — and stays honest when the API access isn’t there.
Frequently Asked Questions
Does Claude work with Homebase?
Not out of the box. Anthropic doesn’t offer a Homebase connector and Homebase hasn’t built one. Homebase publishes API documentation, so a developer could build a custom connection — but you have to request API access from Homebase first, and even then it only works inside a conversation you start.
Can I self-provision a Homebase API key for Claude?
Not the way you can with some tools. Homebase’s API access is request-based — you ask Homebase for access rather than generating a key on your own from a settings page. Once you have it, you still need someone technical to build the connector that lets Claude use it.
Can Claude message my staff about open shifts automatically?
No. Claude’s built-in email drafts messages (in both Gmail and Outlook) but doesn’t send them, and it only works while you’re in the chat — so it can’t offer an open shift the moment it appears. That automatic, on-its-own work is what Carly is built for.
What if I want Homebase to act on its own — chase cover, flag missed clock-outs?
That’s beyond what Claude does; it responds inside a chat and doesn’t act on events. Carly works against your Homebase key if you have one, or through the email and calendar flows around it if you don’t — running on triggers and schedules 24/7 in the cloud. AI agents start at $35/month.
More: Claude connectors · Claude + Deputy · Claude + 7shifts · Best AI tools for restaurants · Can Claude send emails · Claude vs Carly
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
