7shifts AI: The Auto-Scheduler, the Gates, and the Webhooks
If you searched “7shifts AI,” you’re probably deciding whether the scheduling assistant your rep mentioned is worth the plan bump, or whether it’s the usual sprinkle of “AI-powered” on a feature that already existed.
The honest answer for 7shifts is better than most vertical software: the AI is real machine learning doing a job you’d otherwise do by hand. The catch isn’t quality. It’s that the good stuff has prerequisites nobody mentions on the sales call.
The Auto-Scheduler is the real one, and it has a 10-week entry fee
7shifts describes the Auto-Scheduler as using “state-of-the-art machine learning to create Schedules for you on demand.” That’s not marketing dressing on a template. Per 7shifts’ own Auto-Scheduler documentation, the scheduler “learns by studying your past schedules and shifts” — analyzing roughly 8 to 10 previous schedules to find your staffing patterns, then matching people to shifts against availability, overtime, skill level, and preferred hours, inside your labor budget.
It also gets better the longer you use it. Scheduling habits, which team members you tend to pair, typical shift lengths — all of it feeds back in.
Now the part that decides whether you can use it this month. To run the Auto-Scheduler you need a POS integration supplying actual sales data, plus 10 weeks of 7shifts-created sales projections. If you onboarded three weeks ago, or you never wired your POS in, the feature is sitting in your account doing nothing. That’s not a bug — the model is forecasting demand, and it can’t forecast from a blank history.
So the practical sequence is: connect the POS first, let projections accumulate for a full quarter, then evaluate the AI. Most operators who conclude “the auto-scheduler is useless” tried it at week two.
The AI schedule importer is the quiet time-saver
In April 2026, 7shifts added an AI Schedule Importer to the mobile app: admins and managers can upload a photo or file of an existing schedule and have it automatically extract shifts, employees, departments, and roles into the account. There’s a companion tool that pulls staff details out of existing documents to build your roster.
Unglamorous, and it removes the single worst hour of switching scheduling software — retyping a spreadsheet or a photographed wall schedule into a new system. If you’re migrating from paper, from Excel, or from a competitor, this is the AI feature that actually pays for itself, and it needs no POS history at all.
Alongside these sits the demand forecasting that predates the AI branding: sales-driven labor forecasting, real-time projected labor cost as you build the week, and 7shifts’ claim of “95% accurate sales forecasts when integrated with your POS.” Same prerequisite as the Auto-Scheduler — it all runs on the POS connection.
What 7shifts’ AI does not do: react to today
Everything above is planning AI. It builds a better schedule before the week starts and forecasts what the week should cost.
None of it is the thing that ruins your Friday. A line cook doesn’t answer the 4pm text. Someone clocks in 40 minutes late and nobody tells you until you read the punch report Monday. Two servers drift toward overtime on Saturday afternoon and you find out in payroll. A shift stays uncovered because the request went out in the app and nobody opened it.
Those are event problems, not planning problems, and 7shifts’ AI is not aimed at them. That’s the gap worth automating around — and unlike most vertical software, 7shifts actually gives you the plumbing to do it.
No, ChatGPT and Claude do not connect to 7shifts
There is no native ChatGPT connector, no Claude connector, and no official 7shifts MCP server. Neither AI vendor lists 7shifts, and 7shifts hasn’t published one. Anyone telling you otherwise is describing something they built themselves.
The unattended-work gap closed in 2026: ChatGPT Scheduled Tasks and Claude Cowork both run on their own. The remaining gap is what starts them. These run on a timer, not in response to an event in your apps, so "when this happens, do that" is still outside what they do.
For a restaurant that limit is the whole ballgame. “Every morning at 9, summarize yesterday’s labor variance” is achievable with a scheduled task. “The moment someone clocks in 30 minutes late, text the manager on duty” is not — unless you’re on the webhook path below.
7shifts’ API is genuinely self-serve, which is rare in restaurant tech
This is where 7shifts beats most of its category. Toast and Olo make you apply to a partner program. Some practice-management platforms lock individual businesses out entirely. 7shifts does neither.
Per 7shifts’ authentication documentation, the split is clean: “All partners using 7shifts API resources should use OAuth Clients for authentication. Access Tokens are intended for personal usage.” And explicitly: “If you are using 7shifts API resources for internal usage and are not looking to be a technology partner of 7shifts, you should use access tokens for authentication.”
That’s you. The path is Company Settings → Developer Tools → Access Token → Create Access Token, where you name the token and pick an Admin as the technical contact. Only Admins can create them. The resulting token has admin-level access, is long-lived, and — 7shifts’ words — is “simple to implement.” No application, no five-day review, no sales call. The old API-key style was retired back in 2022; access tokens are the current mechanism.
Once you have that token, you paste it into Carly at carlyassistant.com/integrations as a bring-your-own-key connection. Carly doesn’t ship 7shifts as a prebuilt connector, and BYO-key is the supported path for exactly this case.
The webhooks are the actual prize, and they’re on the top plan
7shifts exposes real webhooks, documented at developers.7shifts.com, configured under Company Settings → Developer Tools → Webhooks. 7shifts calls them “the preferred method to stay in sync or respond to changes, as compared with continuously polling.”
Read the event list carefully, because what’s missing shapes what you can build:
time_punch.created,time_punch.edited,time_punch.deleted— the good ones. A punch event fires the moment someone clocks in, out, or gets edited.schedule.published— fires when a schedule goes live.user.created,user.modified,user.deactivated,user.reactivated— onboarding and offboarding.department,location,rolecreated/modified/deleted, pluspayroll_period.closedandauthorization.revoked.
There is no webhook for a shift trade request, a time-off request, or an unclaimed open shift. If your hoped-for automation was “ping me when nobody picks up the Saturday open shift,” that one has to be polled on a schedule, not triggered. Say that out loud before you plan around it.
One more gate: the Create Webhook endpoint carries a “Minimum Plan Required: Gourmet.” Access tokens work on lower tiers, but real-time events are a top-plan feature. If you’re on a cheaper tier, you’re polling the API on a timer — workable, just not instant.
Four things to build on time_punch.created
Punch events are the highest-value trigger in the list, because clock-in behavior is where labor cost actually leaks:
- Late clock-in alert. Punch lands more than 10 minutes after scheduled start, manager on duty gets a text while there’s still time to shuffle the floor — not Monday in a report.
- No-show detection by absence. Scheduled start passes with no matching punch, an alert fires and the workflow pulls the roster of people not on today who are under their hours, ranked by who’s picked up before.
- Overtime interception. Punch-in on someone already near 40 for the week triggers a warning to the GM before the hours are spent, rather than a line item in payroll.
- Early-in creep. People clocking in 15 minutes early across a week is a real, invisible cost. Punch events make the pattern visible weekly instead of never.
In Carly, that trigger-and-branch scaffolding is the free, unlimited Zapier-style workflow layer; the AI agents that read the context and decide what’s worth interrupting a manager for start at $35/month. The restaurant AI tools roundup covers what else is worth wiring, and Claude + 7shifts goes deeper on the chat-assistant side specifically.
What to set up before you touch the API
None of this needs a 7shifts token, and it works on any plan:
- Morning brief pulling today’s roster and yesterday’s sales into one message before you unlock the doors.
- Inbox triage on the address that catches call-out emails, vendor confirmations, and health-inspection notices, so the ones needing a human reply surface first.
- Supplier reorder reminders driven off par dates rather than off running out mid-service on a Saturday.
- A standing weekly labor-variance summary drafted from your exports, ready to read instead of ready to build.
That covers calendar, email, and tasks — the surfaces that work regardless of what your POS or your 7shifts tier exposes. The token and webhooks go on top.
FAQ
Does 7shifts have AI? Yes. The Auto-Scheduler uses machine learning to generate schedules from your past 8–10 schedules plus availability, overtime, skill level, and labor budget. 7shifts also shipped an AI Schedule Importer in April 2026 that extracts shifts, employees, departments, and roles from an uploaded photo or file, and AI-assisted roster building from existing documents.
Why isn’t my 7shifts Auto-Scheduler working? It has prerequisites: a POS integration supplying actual sales data, plus 10 weeks of 7shifts-created sales projections. Without that history the model has nothing to forecast from. Connect the POS and wait out the quarter before judging it.
Does 7shifts have a public API? Yes, and it’s self-serve — unusual in restaurant software. An Admin creates one under Company Settings → Developer Tools → Create Access Token. The token gives admin-level, long-lived access. Outside software companies use OAuth clients instead; access tokens are explicitly “intended for personal usage.”
Does 7shifts support webhooks? Yes, under Company Settings → Developer Tools → Webhooks, covering time punches, schedule publishes, users, departments, locations, roles, payroll period close, and authorization revocation. The Create Webhook endpoint lists a minimum plan of Gourmet. There is no webhook for shift trades, time-off requests, or unclaimed open shifts.
Can ChatGPT or Claude connect to 7shifts directly? No. Neither ships a native 7shifts connector and there’s no official 7shifts MCP server. Any AI access runs through a 7shifts access token and a tool that accepts it.
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."
