CRM & Sales · Integration
HoneyBook
Add HoneyBook to your product for your customers, and give your AI agents governed access to it.
HoneyBook is a clientflow tool: an inquiry becomes a project, the project moves through stages as a proposal is signed and a retainer is paid, and payments land against it. Its integration surface is narrower than the product, and saying so is better than implying a REST API that has not been published. Each account generates its own key inside its integration settings, and what that key carries is a set of events plus two writes. The events cover the whole arc, a client created, a new inquiry, a meeting scheduled or moved, a project booked, a project stage changed and a payment paid, which is genuinely enough to keep another system in step with a small business's pipeline. The writes create a client and create a project. Building to that shape gives you an accurate integration; building to an imagined query API gives you one that fails in a demo.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each business connect their own HoneyBook account using the key from their integration settings, so nothing routes through a shared one.
Create a client and a project from your product, so a new engagement starts in HoneyBook without anybody retyping a name.
React to a new inquiry the moment it arrives, rather than whenever somebody next opens the pipeline view.
Take project booked, stage changed and payment paid events so revenue and onboarding steps in your product follow the real state.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent creates a project for a qualified inquiry, with the client it belongs to recorded.
An agent reports which projects were booked this week and which are still waiting on a first payment.
An agent notices a stage change and prepares the next document a person will need.
Example prompt
Which projects were booked this month, and for which of them has no payment landed yet?
Set up HoneyBook in 4 steps
- 01Enable the HoneyBook connector in your fastn dashboard.
- 02Have each business copy the key from their own integration settings, so events and writes stay inside their account.
- 03Decide which events your product reacts to, and what a client or project your product creates should look like.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the HoneyBook integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a HoneyBook integration without building it. Your customers connect their own HoneyBook account inside your product and work their accounts, contacts and opportunities there, with no per-customer code on your side.
- Handle the part that actually costs time: every CRM instance is customised, so standard objects are never the whole story. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a HoneyBook update is not your on-call problem.
- One integration serves your product and your agents. The same governed HoneyBook connection powers in-product features and gives AI agents scoped, audited access, so you keep customer records aligned between your product and the CRM each customer already runs without wiring it twice.
Used by these teams
Compare with
Dubsado
PipedriveWorks well with
CalendlyOften used alongside
Tools the same teams tend to run next to HoneyBook, across other categories.
Slack
Mailchimp
Marketo
Google AdsHoneyBook integration FAQ
How do I add a HoneyBook integration to my product?
Enable the HoneyBook connector in your fastn dashboard, then let each customer authenticate their own HoneyBook account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no HoneyBook client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own HoneyBook account?
Yes. Every connection is scoped to the individual customer, so each authorises their own HoneyBook account and only ever sees their own accounts, contacts and opportunities. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this HoneyBook integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent creates a project for a qualified inquiry, with the client it belongs to recorded.
Who maintains the HoneyBook integration?
fastn does. When HoneyBook changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the HoneyBook integration support custom fields and custom objects?
Yes. CRM instances are heavily customised, so field and object mapping is configuration rather than code. Each customer maps their own fields during setup, which means onboarding a customer with an unusual HoneyBook schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from HoneyBook, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in HoneyBook do not drift apart.
What can I build with the HoneyBook integration?
A common starting point: let each business connect their own HoneyBook account using the key from their integration settings, so nothing routes through a shared one. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the HoneyBook integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding HoneyBook does not change your per-connector cost. You can start free with 3 connected accounts.
Add HoneyBook to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.