HubSpot
Landing page leads that arrive in HubSpot, and ads that learn from your deals
Connect HubSpot once and every lead from a Baker Form is submitted to the HubSpot form you choose, so your contacts, lifecycle stages and workflows run as usual. Baker can also put a HubSpot form or meetings calendar on a landing page, and read deal and lead stages to tell Google Ads and Meta which ads brought real customers. Baker reads your CRM and never edits a record.
- Leads into your HubSpot forms
- Your forms and calendars on the page
- Ads that learn from your deals
- Which deals your ads reached
- Answers about your CRM
- Built by
- Baker
- Category
- CRM and email
- Plan
- Every plan
- Connects by
- Signing in
- Updated
- November 21, 2026
How it works
From connecting to publishing, in three steps
- 1
Connect HubSpot
In Brain → Integrations, press Connect on the HubSpot card and approve Baker in HubSpot. A client can do it from a setup link without a Baker login.
- 2
Ask for the Form you need
In a chat, ask Baker for a Form that sends its leads to HubSpot. It picks the HubSpot form, maps the fields and shows you the result before anything goes live.
- 3
Publish
Press Publish. From then on every lead goes to HubSpot, and each submission in Baker says whether HubSpot received it.
What Baker does
Everything Baker does with HubSpot
-
Leads into your HubSpot forms
A Baker Form submits each lead to the HubSpot form you pick, so contacts, lifecycle stages and your HubSpot workflows run as if the form were filled in on your own site.
-
Your forms and calendars on the page
Put a HubSpot form or a HubSpot meetings calendar in any step of a Baker Form, with its redirect, region and fields kept.
-
Ads that learn from your deals
When a contact, a lead or a deal reaches the stage you choose, Baker sends it to Google Ads and Meta as an offline conversion. You build nothing in HubSpot; Baker only follows the stages you chose.
-
Which deals your ads reached
Baker matches the companies your LinkedIn ads reached against your HubSpot companies and deals, and shows the pipeline they influenced.
-
Answers about your CRM
Ask Baker in a chat whether a test lead arrived, which forms redirect, which workflows run after a lead or which deals closed this quarter.
-
Lead ads into HubSpot too
Leads from Meta, LinkedIn and Google Ads lead forms can be sent to the same HubSpot form, checked every few minutes once you publish.
You approve
Nothing changes in HubSpot until you press Publish
Baker prepares every change in a chat and shows it to you. It applies only when someone on your team who may publish presses Publish, and if you discard the chat, nothing applies.
Data and permissions
What Baker reads and what it can change
Exactly what Baker uses from your account, when and why. Baker asks only for the permissions this needs.
| What | Baker | When | Why |
|---|---|---|---|
| Your HubSpot forms, their fields and how many leads they receive | Reads | When you ask | To offer your forms as destinations or page steps, map fields correctly and check a form is producing leads. |
| Leads from your published Baker Forms, submitted to the HubSpot form you chose, with the page they came from and HubSpot's own visitor cookie | Sends | All the time | So each lead becomes a HubSpot form submission, linked to the visitor's earlier visits, and your contacts and workflows update as usual. It starts only once you publish. |
| Your meeting links and their booking fields | Reads | When you ask | To put a HubSpot meetings calendar on a landing page. |
| Your workflows (optional permission) | Reads | When you ask | To show what happens to a lead after it arrives. HubSpot has no read-only version of this permission, so it also allows changes; Baker never changes a workflow. |
| Contacts and their properties (optional permission) | Reads | All the time | To check a lead arrived with its tracking, and to read the lifecycle stage you want counted as a conversion. |
| Deals, deal pipelines and stages (optional permission) | Reads | All the time | To count the deal stages you choose as conversions for your ads, and to report pipeline and revenue. |
| Companies (optional permission) | Reads | All the time | To match the companies your ads reached with your CRM accounts. Baker refreshes them every night. |
| Change notifications for the properties you watch | Reads | All the time | Baker's app subscribes to HubSpot's change notifications for only the properties you chose to watch. They are notifications to Baker, not records in your CRM. |
| Leads and their stages (optional permission, Sales Hub Professional) | Reads | All the time | To count qualified or disqualified leads as outcomes for your ads. |
What you need
- A HubSpot account. Forms and meetings work on any plan; reading workflows needs a HubSpot Professional plan, and reading leads needs Sales Hub Professional.
- A HubSpot user who can install apps in that account, such as a super admin.
- An admin or member role in Baker to connect it. A client can connect it from a setup link instead.
- Any HubSpot form that receives leads must have CAPTCHA switched off, because HubSpot turns away submissions sent to a form that has it.
What Baker's team switches on
- Sending leads from Meta lead ads into HubSpot needs lead access, which Baker's team switches on for your company.
- Ask in Requests in Baker, or write to support@withbaker.com.
Frequently asked questions
Does Baker change records in my CRM?
No. Baker adds leads only by submitting them to the HubSpot form you chose, which is what HubSpot does for any form on your site. It reads contacts, deals and workflows and never edits or deletes a record.
What happens when a lead's email is already in HubSpot?
HubSpot updates the existing contact instead of creating a new one, as it does for any form submission. The lead may not show up as a new contact.
Do I need a paid HubSpot plan?
No for forms, meetings, contacts and deals. Reading workflows needs a HubSpot Professional plan, and reading leads needs Sales Hub Professional. Without them the connection still works and Baker tells you which part it could not read.
What happens to my data if I disconnect?
Everything Baker sent to HubSpot stays in HubSpot. Baker deletes its sign-in, and Baker keeps the Form answers it collected for 90 days. The setup guide explains disconnecting and uninstalling step by step.
Can my client connect their HubSpot without a Baker login?
Yes. Send them a setup link from Baker; they sign in to HubSpot from it and the account connects to your company in Baker.
Keep learning
- Connect HubSpot to Baker Install Baker in your HubSpot account, send your Forms' leads to HubSpot, and disconnect or uninstall it, with what happens to your data.
- Add a form that sends leads to your CRM Create a Form with Baker, choose where its leads go, from HubSpot to a Google Sheet or your inbox, and put it live on your landing pages.
- Send a test lead and check it arrived Prove a Form works end to end, from your live landing page to your CRM, sheet or inbox, and read what Baker says about each submission.
Used together with
- PipedriveBaker's Forms create a person and a lead in Pipedrive for every submission, plus an organization when asked, and Baker reads what happens next.
- GoHighLevelBaker's Forms turn each lead into a GoHighLevel contact, business and opportunity, and put your GoHighLevel calendars and forms on landing pages.
- Google AdsBaker reads your Google Ads accounts, prepares campaigns, keywords, ads and budgets, and changes Google Ads only when you press Publish.
- Meta AdsBaker reads your Meta ad accounts, prepares campaigns, ads, budgets and audiences, and changes Meta only when you press Publish.