Claude + HoneyBook: What the Integration Can (and Can't) Do in 2026
No — there’s no real Claude HoneyBook integration, and the reason is HoneyBook, not Claude. There’s no official Claude HoneyBook connector in Anthropic’s directory, no HoneyBook-built MCP server, and no public API to build one against. HoneyBook has famously stayed closed, and that hasn’t changed in 2026: no developer portal, no documented endpoints, no self-serve API keys. So any “Claude + HoneyBook integration” that promises to read your projects or push invoices is either wishful or built on a reverse-engineered workaround. What is real is a narrower set of around-the-edges workflows — and a way to run those on their own.
Here’s what’s actually true, why, and what to use if you want the adjacent work to run without you.
Why there’s no integration to build
Most “connect Claude to X” stories depend on X exposing an API. HoneyBook doesn’t:
- No public API, no developer portal. There’s no programmatic way for a photographer, planner, or coach to read clients, projects, invoices, or payments out of HoneyBook — or write them back. Community forum threads still ask for an open API; there’s no vendor commitment.
- The official integration path is Zapier. HoneyBook connects to the outside world through Zapier (and a handful of prebuilt connections). That’s a real seam — new inquiries, projects, and payments can fire Zapier events — but it’s not a direct API you can hand Claude.
- “Unofficial API” adapters exist, and they’re risky. A few vendors advertise access built against HoneyBook’s private internal endpoints. That’s reverse-engineered, against HoneyBook’s terms, and can break without notice. Don’t route client and payment data through something like that.
So there’s simply no supported surface for a Claude MCP server to talk to. This isn’t a “you need the right plan” gate — there’s no door at all.
What Claude actually can — and can’t — do
Because there’s no API, Claude can’t read your HoneyBook pipeline, pull a client’s project, or send an invoice. What’s left is Claude as a standalone assistant you paste into:
- Draft the client-facing words — a proposal blurb, an inquiry reply, a rebooking note, a package description — that you then copy into HoneyBook yourself.
- Shape and summarize — paste a messy set of notes from a discovery call and have Claude turn it into a tidy scope you drop into a HoneyBook project.
None of that is an integration — it’s copy-paste. And the usual Claude limit applies on top: MCP or not, Claude only works inside a conversation you start. Nothing watches your HoneyBook inbox, nothing fires when an inquiry lands, and nothing runs while you’re away.
The one automation-adjacent hook: email, calendar, and Zapier
The pieces of a HoneyBook business that do talk to the outside world are the ones around the record, not inside it: the inquiry emails that hit your inbox, the bookings that land on your calendar, and the Zapier events HoneyBook can fire. Those are things an agent can act on — an inquiry email can trigger a first reply, a booked date can trigger a prep task, a Zapier “new project” event can push into a tool you control. That’s exactly where the next section comes in.
If you want the around-HoneyBook work to run on its own: Carly
You can’t make Claude reach into HoneyBook’s database — nobody can, there’s no API. But most of what a solo business wants automated lives around the project, not inside HoneyBook’s record: replying to inquiries fast, sending the follow-up, prepping for a shoot or a call, chasing a quiet lead. That work can run on its own if you anchor it to the inbox, the calendar, and Zapier rather than the HoneyBook record.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers, working the honest seams HoneyBook leaves open:
- Acts on your inbox and calendar, 24/7, in the cloud — when an inquiry email arrives, Carly can draft and send a fast first reply; when a booking lands on your calendar, it can prep the day and nudge you the evening before. Your laptop doesn’t need to be awake.
- Catches HoneyBook’s Zapier events — route a “new inquiry” or “new project” event from HoneyBook (via Zapier) into a workflow Carly runs, so the follow-up, the reminder, and the task all happen automatically.
- Actually sends and updates — drafts and sends email (Gmail and Outlook) with attachments, files and labels, manages tasks, and records meetings.
- Builds the workflow for you — tell it “I’d like every new inquiry to get a friendly reply within the hour, then a reminder to follow up in two days” in plain English; it interviews you, then builds it with you. No prompt engineering.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. Carly connects to 200+ tools across 40+ categories, and can reach anything else through your own API key — so the inbox, calendar, CRM, and docs around HoneyBook all live in one workflow. See integrations.
Claude vs Carly
| Claude | Carly | |
|---|---|---|
| Reads HoneyBook records | No (no API) | No (no API — nobody can) |
| Drafts client-facing copy to paste in | Yes (out of band) | — |
| Acts on inquiry email and calendar | No | Yes |
| Catches HoneyBook’s Zapier events | No | Yes |
| Sends follow-ups on its own | No | Yes |
| Works while laptop is closed | No | Yes (cloud) |
| Sends email as part of the flow | No (Gmail draft-only) | Yes (Gmail + Outlook) |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude is a chat you paste into. Carly is a teammate that runs the replies and follow-ups around your bookings — using the inbox, calendar, and Zapier, since HoneyBook itself has no API.
Frequently Asked Questions
Does Claude work with HoneyBook?
No, not as an integration. HoneyBook has no public API, no official Claude connector, and no MCP server, so there’s nothing for Claude to connect to directly. Any advertised “Claude + HoneyBook integration” relies on a reverse-engineered, terms-of-service-risky workaround. Claude can only help out of band — drafting client-facing copy you then paste into HoneyBook yourself.
Is there a HoneyBook API at all?
Not a public one. HoneyBook has stayed closed for years and remains so in 2026 — no developer portal, no documented endpoints, no self-serve keys. Its official integration path is Zapier. Third-party “HoneyBook API” adapters are unofficial and built against private endpoints; treat them as risky.
How would I automate anything around HoneyBook?
Through the seams HoneyBook leaves open: inquiry email, your calendar, and HoneyBook’s Zapier events. An agent like Carly can act on those — replying to inquiries, sending follow-ups, and prepping your day 24/7 in the cloud — without touching HoneyBook’s record directly. AI agents start at $35/month.
Can Claude send my HoneyBook invoices or replies automatically?
No. Claude only works inside a conversation you start, and it can’t reach HoneyBook regardless. For automatic, trigger-based follow-up around your bookings, you need an agent platform like Carly that acts on your inbox, calendar, and Zapier events.
More: Claude connectors · Claude + Zapier · Claude + Calendly · Can Claude send emails · Claude vs Carly · Best AI tools for solopreneurs
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."
