Eano Pro doesn’t have a direct integration with HubSpot — but we don’t need one.
Zapier sits in the middle and gives you a no-code way to wire the two systems together. This guide walks you through getting them talking, including the bidirectional setup most teams want: new HubSpot deals show up as Eano projects, and stage changes flow both ways.
Before You Begin
You’ll want a few things in your back pocket:
An Eano account with the right scope to act on the projects you want to sync. Whoever connects Zapier is the user that inbound Zaps will create and update projects on behalf of, so this is usually an Owner or Admin.
A Zapier account (the free tier works for simple one-way Zaps; bidirectional setups usually need a paid plan because of multi-step Zaps).
A HubSpot account where you can create and edit deals, and connect new apps.
A rough idea of which HubSpot deal stages should map to which Eano project stages. Jot these down before you start — it’ll save backtracking later.
Step 1: Connect Eano Inside Zapier
Sign in to Zapier
Click Create Zap
When prompted to pick an app, search for Eano and select it
Zapier will pop open a small window asking you to sign in to Eano — this is Eano’s front door, and Zapier is politely knocking.
Sign in with your Eano credentials
Click Authorize
The window will close on its own once the handshake is complete. Zapier now has a secure, revocable connection to your Eano account — no copy-pasting API keys, no token rotation to worry about.
Tip: If your browser blocks the pop-up, allow pop-ups for Zapier and try again.
Step 2: Connect HubSpot Inside Zapier
In the same Zap builder, pick the other app
Search for HubSpot and select it
Sign in and authorize access
Zapier will walk you through signing in to HubSpot the same way. Once both apps are connected, you’re ready to start building Zaps.
You only have to do Steps 1 and 2 once. Every Zap you build from here on can reuse the same connections.
The Three Things Eano Can Do With HubSpot
Before building your workflows, it helps to understand what’s available.
Eano shows up in Zapier with a set of triggers and actions:
Triggers (Eano → HubSpot)
New Project Created — fires when a new project (or opportunity) is created in Eano
Project Stage Changed — fires when a project moves from one stage to another
Actions (HubSpot → Eano)
Create Project — creates a new project in Eano from a HubSpot deal
Link External CRM Record — connects an Eano project to a HubSpot deal
Update Project Stage — updates the stage of an Eano project
Most teams use a combination of these depending on their workflow.
Setup A: One-Way — HubSpot Deals Become Eano Projects
This is the simplest setup and a great place to start. When a new deal lands in HubSpot, a project is automatically created in Eano.
Steps
In Zapier, create a new Zap
For the trigger, pick HubSpot → choose New Deal
Or use New Deal in Stage if you only want specific deals (e.g., “Contract Sent”)
For the action, pick Eano → Create Project
Map the fields:
Project Name — HubSpot deal name
Address — your HubSpot project address field (or create one if needed)
Customer Name, Email, Phone — from the associated contact
External ID — set this to the HubSpot Deal ID (this is the most important field)
Eano Stage — optional (defaults to “New” if left blank)
Test the Zap with a real HubSpot deal
Turn it on
From now on, matching HubSpot deals will automatically appear in Eano.
Setup B: Two-Way — Stages Stay in Sync
Once the basic flow is working, most teams want stage changes to flow both ways.
The key idea:
Each system needs to know the other’s record ID.
HubSpot stores the Eano project ID
Eano stores the HubSpot deal ID
Once linked, updates can sync in either direction.
You’ll build three Zaps.
Zap 1: HubSpot Deal Created → Eano Project Created
This is Setup A above.
Make sure the External ID is mapped to the HubSpot deal ID — this is what makes everything else work.
Zap 2: Eano Project Created → HubSpot Deal (Optional)
If your team creates projects directly in Eano, this Zap mirrors them back to HubSpot.
Steps
Trigger: Eano → New Project
Action: HubSpot → Create Deal
Action: Eano → Link External CRM Record
That third step closes the loop. Without it, stage syncing won’t work.
Zap 3: Stage Changes Flow Both Ways
This is two Zaps—one in each direction.
HubSpot → Eano
Trigger: HubSpot → New Deal Property Change
Property Name: Deal Stage
Action: Eano → Update Project Stage
Map HubSpot Deal ID → External CRM ID
Map HubSpot Stage → External Status
Select the matching Eano stage
Eano → HubSpot
Trigger: Eano → Project Stage Changed
Action: HubSpot → Update Deal
Match using the External CRM ID and update the deal stage.
Because each Zap only fires on actual changes—and Eano briefly suppresses outbound updates after receiving one—you won’t get stuck in a loop.
A Note on Stage Mapping
Eano and HubSpot stages don’t need to match one-for-one.
HubSpot focuses on the sales pipeline
Eano covers the full lifecycle
The goal is to pick the closest match.
Common examples:
Appointment Scheduled → Qualifying
Qualified to Buy → Estimating
Contract Sent → Proposal Sent
Closed Won → Closed (Won) or Site Measurement
It’s normal for multiple HubSpot stages to map to the same Eano stage.
Corner Cases Worth Knowing
Duplicate Deals
If a deal appears twice, check that External ID is mapped correctly.
This is what enables deduplication.
Fast Stage Changes
If a deal changes stage immediately after creation, Eano may briefly pause (up to ~30 seconds) to let everything sync properly.
Missing Stage Updates
If stages aren’t syncing:
Check if the project has an External CRM ID
If not, run Link External CRM Record manually
Rate Limits
Eano allows up to 60 inbound calls per minute per user per Zap action.
For bulk imports:
Run in batches
Slow down the Zap if needed
Disconnecting
To stop syncing:
Turn off Zaps in Zapier
Or revoke Zapier access in Eano settings
Existing projects will remain — disconnecting only stops live sync.