HoneyBook and Gmail: what syncs, what doesn't, and how to set it up
HoneyBook sends client email from your Gmail address and finds new leads in your inbox. Email you start in Gmail never appears in HoneyBook projects.
- Connector
- Native connection built by HoneyBook, set up in Company Settings > Integrations; no separate fee listed in the docs
- Sync direction
- Mostly HoneyBook → Gmail for sending; Gmail → HoneyBook for replies in project threads and lead detection
- Setup time
- Under 30 minutes per HoneyBook's integration page; each team member connects their own address
- Availability
- No plan restriction in the email docs; Gmail lead finder is part of HoneyBook AI, which the pricing page lists on Starter, Essentials and Premium. Gmail-side account types are not specified
- Our rating
- 3 out of 5. Sends from your Gmail address and finds leads in the inbox, but email started in Gmail never reaches HoneyBook.
| What | Direction | Detail |
|---|---|---|
| Messages and files sent from HoneyBook | HoneyBook → Gmail | Clients see your Gmail address in the From field. A copy lands in your Gmail Sent folder. Without the connection, HoneyBook uses a proxy address. |
| Client replies in project threads | Gmail → HoneyBook | Replies appear in both HoneyBook and your regular inbox. A reply sent from outside HoneyBook still shows in the project if the thread started there. |
| Lead detection | Gmail → HoneyBook | Gmail lead finder scans the past 30 days when first turned on, then monitors new activity. It creates a contact and, for qualifying inquiries, a project in the Inquiry stage. |
| Marketplace inquiries | Gmail → HoneyBook | Inquiries from The Knot, WeddingWire, Zola and PartySlate are matched by sender domain. They create projects the same way, with no source label. |
| Lead details | Gmail → HoneyBook | Each lead gets email address, name and last interaction date. HoneyBook AI also fills project name, type, date and location when the inquiry states them. |
| Conversation summary | Derived | HoneyBook AI writes a summary and adds it to the lead details and to the original Gmail thread. The lead cannot see it. |
| Google Calendar events | Two-way | A separate connection under the Calendar section. You choose whether to share HoneyBook events with Google and show Google events in HoneyBook. |
Setting it up
- In HoneyBook, click your profile photo, then Company Settings, then the Integrations tab.
- Under Email, click Connect, enter your Gmail address and click Continue.
- Select Connect Google Account, choose the Gmail address and approve the permissions.
- Return to HoneyBook and decide whether to switch on Enable opportunity and project suggestions from Gmail. The lead finder article says it is on by default, so check Company settings > HoneyBook AI.
- Ask each team member to connect their own address, because email integration is set per account.
- Optional: connect Google Calendar under the Calendar section and pick your sync preferences.
Where the integration stops
- Email started in Gmail does not appear in HoneyBook. HoneyBook's docs state this even with the integration on. Start client threads from HoneyBook, or log them by hand.
- Lead finder stops at 50 projects per member per day. HoneyBook silently drops any qualifying inquiries beyond that, with no project and no notification.
- Auto-created projects don't trigger automations. Move the project to another stage or start the workflow yourself.
- Relay addresses need fixing by hand. Marketplace leads that arrive through a relay address get a warning icon, and you replace the address with the client's real email.
- Calendar edits flow one way. Edits to a HoneyBook event in your external calendar do not update HoneyBook, and HoneyBook syncs only one external calendar at a time.
- Custom domains need DNS records. If your Gmail address uses your own domain, you set up DKIM, SPF and DMARC yourself.
HoneyBook's Gmail connection makes client email come from your own address and watches your inbox for new inquiries. It suits solo and small-team service businesses that already run client work from HoneyBook projects. HoneyBook builds it, and you set it up in Company Settings.
The fact that most often surprises teams: email you start in Gmail does not reach HoneyBook. HoneyBook's docs say so directly. The connection is not a full mailbox sync. See HoneyBook and Gmail for the vendor profiles.
HoneyBook sends through Gmail, but only for threads it starts
When you connect Gmail, messages and files you send from HoneyBook show your address in the From field. A copy sits in your Sent folder. Clients reply as usual, and the reply appears in the project and in your inbox.
A message belongs in a project only if you sent it from that project or it answers a thread that began there. A new email you write in Gmail stays in Gmail. If your team quotes and negotiates by typing in the inbox, the project history will have gaps.
Each team member connects their own address. The docs list no plan requirement for the connection. See the HoneyBook pricing page for the plans.
Gmail lead finder turns inquiries into projects
Gmail lead finder reads the past 30 days when you first turn it on, then keeps watching. For each new prospect it creates a contact and, for qualifying inquiries, a project in the Inquiry stage with a "New lead" badge. It skips contacts who already have a booked project.
Marketplace inquiries need no extra setup. HoneyBook matches the sender domain for The Knot, WeddingWire, Zola and PartySlate. The project carries no marketplace label, so you cannot filter by source. Relay addresses create the project with a warning, and you swap in the client's real email.
The lead finder has hard edges. It creates at most 50 projects per member per day and drops the rest without a notice. The projects it creates do not start automations. Plan a manual first step, such as moving the project to a new stage.
What you build yourself
Calendar sync is a separate connection to Google Calendar. It runs two-way if you turn on both options. Edits to a HoneyBook event made in Google do not come back, and HoneyBook syncs one external calendar at a time.
For anything beyond this, HoneyBook's integration page points to Zapier. You copy an API key from your HoneyBook settings and paste it into Zapier. The docs read for this review do not list which Gmail triggers or actions that route supports, so check Zapier before you plan around it.
If you send from a custom domain on Gmail, you also own the DKIM, SPF and DMARC records. HoneyBook's email FAQ explains what each one does.