HoneyBook

Webflow forms collect submissions, but they don't manage what happens after someone hits submit. Webflow offers no built-in pipeline after an inquiry: proposals, signed contracts, invoices, follow-up emails, scheduling exchanges, and payment reminders all need manual handling. HoneyBook research found that 36% of customers abandon small businesses because of slow response times, ranking slow response above price and quality.

Connecting HoneyBook with Webflow closes that gap. Visitors submit inquiries on a Webflow page, and HoneyBook handles the booking and payment steps that follow. Each submission creates a project in HoneyBook's pipeline, where automations send follow-up emails, branded proposals, e-signed contracts, and invoices. You can also push HoneyBook events, such as bookings and stage changes, back into Webflow content.

This integration fits independent service businesses that run their marketing site on Webflow. Photographers, wedding and event planners, coaches, consultants, interior designers, and social media managers all follow the same pattern of inquiry, proposal, contract, and payment. Agencies building Webflow sites for these clients can wire each site's forms into the client's HoneyBook account.

How to integrate HoneyBook with Webflow

What is HoneyBook? HoneyBook is an AI-powered client relationship platform for independent businesses, available in the U.S., Canada, the UK, and Australia. It combines lead capture, scheduling, contract signing with e-signatures, invoicing, and online payments in one system. More than 100K small businesses use it to run the full lead-to-payment workflow.

Teams pair the two platforms when the website needs to do more than display a portfolio. A Webflow site brings in traffic and inquiries, and HoneyBook converts those inquiries into booked, paying clients without manual handoffs. HoneyBook does not list Webflow as a native integration, so the connection runs through embeds and links, with Zapier for automation rather than a first-party app.

The HoneyBook-Webflow integration supports these approaches:

• Direct links and embedded forms put HoneyBook lead capture, scheduling, and payment on your Webflow pages without automation tools.
• Zapier sends Webflow form submissions into HoneyBook and syncs HoneyBook events back to the Webflow CMS.
• The Webflow Data API and webhooks give developers server-side control over form data and CMS updates, though HoneyBook itself has no public API.

Most implementations combine two of these methods, depending on whether HoneyBook or Webflow owns the form.

Embed HoneyBook forms with Code Embed elements

HoneyBook contact forms and lead forms embed on any Webflow page through the Code Embed element. This is the fastest path to a working integration and needs only copy-and-paste. Submissions from an embedded form create new projects in HoneyBook's inquiry stage automatically, per HoneyBook's contact form documentation. You need a paid Webflow Workspace or Site plan to use the Code Embed element, and each element accepts up to 50,000 characters.

Embed a lead form

Only published lead forms can be embedded, so publish the form in HoneyBook first. Lead forms support questions, client file uploads, service selection, scheduling blocks, and a payment step.

To embed a lead form:

1. In HoneyBook, go to Lead capture > Lead Forms and open a published form.
2. Select Share > Code tab > Copy code, following HoneyBook's embed instructions.
3. In Webflow, open the Add panel and add a Code Embed element to the canvas.
4. Paste the copied code, then save and close the modal.
5. Publish the site. Custom code does not go live until you publish.

Before you build, account for these lead form constraints:

• The contact info block is mandatory and cannot be deleted.
• Contract blocks and electronic signatures cannot be added to lead forms.
• Each form supports one payment, the payment page must be the last page, and lead-form payments accept credit cards only.
• Smart files like questionnaires cannot be embedded, so the documented workaround is a lead form with question blocks.

Embedded HoneyBook forms bypass Webflow's form system entirely, so submissions never appear in your Webflow form logs and no Webflow form submission event fires.

Link a contact form or scheduler with direct links

Direct links need zero code and no paid Webflow plan. HoneyBook generates public URLs for contact and lead forms as well as scheduling sessions, and you attach that URL to any Webflow button or text link. Session direct links can be shared publicly and copied from the Scheduler dashboard. The scheduler itself cannot be embedded, so a link or a lead form with a scheduling block is the documented path.

To add a direct link:

1. Copy the public link from HoneyBook's Share panel or Scheduler dashboard.
2. In Webflow, select a button element and set its link to the copied URL.
3. Publish the site.

For a full booking flow, link to an instant booking lead form. Visitors complete service selection, scheduling, and payment while HoneyBook creates the project at the same time.

Connect Webflow forms to HoneyBook with Zapier

Zapier is the only automation platform HoneyBook officially documents, per its Zapier help article. This method keeps Webflow's native forms in control, so submissions land in your Webflow form logs and flow into HoneyBook through a Zap. It requires a HoneyBook Essentials or Premium plan, since Starter accounts don't have Zapier access.

To set up the connection:

1. In HoneyBook, go to Tools > Integrations > Zapier section > Copy API Key. The key is user-scoped, not company-level.
2. In Zapier, connect Webflow via OAuth and connect HoneyBook with the copied API key.
3. Start from a published template, such as create HoneyBook projects from Webflow form submissions or create HoneyBook clients from Webflow form submissions.
4. Map Webflow form fields to HoneyBook's inputs. Create Project requires Client Full Name and Client Email, with optional fields for Phone Number, Project Type, Project Date, Project Details, Project Budget, and Project Location.
5. Test the Zap and turn it on.

The integration also runs in both directions. A Webflow New Form Submission can trigger HoneyBook's Create Project or Create Client action, while HoneyBook events write back to Webflow: New Project Booked creates a live CMS item, Project Stage Changed updates it, and New Payment Paid updates the item again. Through HoneyBook's Zapier integrations, HoneyBook exposes six instant triggers: New Inquiry, Client Created, New Project Booked, Meeting Scheduled, New Payment Paid, and Project Stage Changed. HoneyBook custom fields are not supported through Zapier, and Zapier polls Webflow form submissions rather than receiving them in real time.

Build with the Webflow Data API and webhooks

HoneyBook does not offer a public REST API or developer portal, and it has no documented native webhooks. That rules out a direct server-to-server integration and makes Zapier the only programmatic write path into HoneyBook. The Webflow side is fully open, so developers can still control how form data leaves Webflow and how HoneyBook-driven events update site content.

The developer path depends on Webflow's API surface and HoneyBook's Zapier credential. Webflow's Data API handles CMS collections and form submissions with Bearer token authentication, and Webflow webhooks push form submission and CMS events to any endpoint in real time. HoneyBook's user-level Zapier API key remains the only programmatic credential it issues.

All Webflow endpoints below use API v2, since v1 support ended March 31, 2025.

Capture Webflow form submissions server-side

Register a webhook so your server receives every submission the moment it happens, then forward the data toward HoneyBook through a Zapier webhook step.

To implement this:

1. Create the webhook with POST https://api.webflow.com/v2/sites/{site_id}/webhooks and set triggerType: form_submission.
2. Handle the payload, which includes name, siteId, data with the submission's key-value pairs, submittedAt, formId, and formElementId, per the form submission event reference.
3. Forward the parsed fields to a Zapier webhook that runs HoneyBook's Create Project or Create Client action, since your server cannot call HoneyBook directly.

This pattern lets your infrastructure validate and log the lead before it reaches HoneyBook, with enrichment when your workflow needs it.

Update Webflow CMS items from HoneyBook events

Use a HoneyBook Zapier trigger to notify your server, then write the change to the Webflow CMS with the Data API. This suits builds where Zapier's built-in CMS actions aren't flexible enough.

To implement this:

1. Trigger on a HoneyBook event in Zapier, such as Project Stage Changed, and pass it to your endpoint.
2. Create or update the item with POST /v2/collections/{collection_id}/items or PATCH /v2/collections/{collection_id}/items/{item_id}. Both require the CMS:write scope, and fieldData must include name and slug, per the create item reference.
3. Publish the change with POST /v2/collections/{collection_id}/items/publish.

Real-time events out of HoneyBook always pass through Zapier's polling, so plan for a short delay between the HoneyBook event and the CMS update.

What you can build with the HoneyBook Webflow integration

Integrating HoneyBook with Webflow lets you capture leads from your own site, then carry booking and payment into the same workflow without stitching a form tool to separate scheduling and invoicing apps.

• Photography portfolio with built-in inquiry pipeline: A portfolio site carries an embedded HoneyBook lead form on the contact page, so each submission creates an inquiry-stage project and triggers automations that send a brochure and scheduling link within minutes.
• Instant booking page for coaches and consultants: A services page opens an instant booking lead form from a CTA button, where prospects select a package, schedule a consult, and pay in one flow while HoneyBook creates the project.
• Event planner lead router: A Webflow inquiry form connected through Zapier's Create Project action maps budget, event date, location, and project details straight into HoneyBook's pipeline for proposal and contract follow-up.
• Live booked-projects page: A Collection List of current clients or events updates from Zaps that create a CMS item on New Project Booked and change its status field on Project Stage Changed.

The same field mapping applies to any CRM: see how to send Webflow forms to HubSpot via Zapier for a walkthrough you can adapt to HoneyBook. If you need tighter control over how submission data is validated or enriched, the developer path handles that before the data reaches HoneyBook.