↔ 
Native vs Make vs n8n vs Relay, setup time, cost & field mapping
Salesforce (CRM) has a native integration with HubSpot (CRM). Sync customer interactions from Salesforce to HubSpot for unified customer view and automated sales follow-up. Typical setup takes around 30 minutes.
Salesforce HubSpot Connect Salesforce and HubSpot for seamless customer data sync and automate sales workflows with our integration.
Sync customer interactions from Salesforce to HubSpot for unified customer view and automated sales follow-up.
medium
30 minutes
Calculate your monthly automation cost based on data volume
💡 Tip: Make is best for complex logic and data transformations. n8n is great if you need privacy and self-hosted control. Pabbly Connect offers unlimited tasks at a flat rate, ideal for high-volume workflows on a budget.
Salesforce to HubSpot is a setup workflow.
This pair usually requires custom mapping (Lead Migration), so an automation layer is needed between Salesforce and HubSpot.
Make is the fastest way to map fields and automate Salesforce -> HubSpot without custom code.
Pabbly Connect is a one-time payment automation tool — ideal for Salesforce → HubSpot workflows without monthly fees.
Choose the right tool for your requirements:
| Platform | Cost | Setup | Flexibility | Best For | |
|---|---|---|---|---|---|
| 🔗 Native | Free Free | 5-15 min Fastest | Low Limited | Zero-config sync Data syncs directly between apps, no middleman. Perfect for simple, one-way flows. | Included |
Use Make to get running in 15–45 minutes. Map fields, transform data, and connect dozens of apps without touching code. Best for startups and fast iterations.
Deploy n8n on your own servers for zero cloud dependencies. Full data residency, unlimited customization, and complete audit trails, essential for healthcare, finance, and GDPR compliance.
Free, open-source workflows you can import into n8n in one click, no subscription required.
Copy this Salesforce → HubSpot blueprint, open n8n, paste it into the canvas, and your workflow is ready to configure.
{
"name": "Salesforce → HubSpot Sync",
"nodes": [
{
"id": "node-1",
"name": "Salesforce Trigger",
"type": "n8n-nodes-base.salesforceTrigger",
"typeVersion": 1,
"position": [
240,
300
],
"parameters": {},
"credentials": {
"salesforceOAuth2Api": {
"id": "1",
"name": "Salesforce account"
}
}
},
{
"id": "node-2",
"name": "HubSpot Action",
"type": "n8n-nodes-base.hubspot",
"typeVersion": 1,
"position": [
460,
300
],
"parameters": {},
"credentials": {
"hubspotApi": {
"id": "2",
"name": "HubSpot account"
}
}
}
],
"connections": {
"Salesforce Trigger": {
"main": [
[
{
"node": "HubSpot Action",
"type": "main",
"index": 0
}
]
]
}
},
"active": false,
"settings": {
"executionOrder": "v1"
},
"tags": [
"integratestack",
"blueprint",
"salesforce",
"hubspot"
]
}Blueprint copied to clipboard. open n8n and paste it into the canvas to activate your workflow.
Detailed mapping of how fields sync between systems.
| Source Field | Type | Target Field | Direction | Notes |
|---|---|---|---|---|
| lifecycle_stage | string | Type | bidirectional | Tricky mapping. HubSpot stages are fixed; Salesforce picklists are custom. |
| associated_company_id | id | AccountId | bidirectional | Relationship link. |
Yes, Salesforce has a native integration with HubSpot. It is available directly within the Salesforce app marketplace.
Yes. This integration typically uses OAuth 2.0, meaning you grant permission via a secure login window. You do not need to share your raw password, and you can revoke access at any time from your Salesforce security settings.
This is typically a one-way sync: Salesforce → HubSpot. Changes in HubSpot do not sync back to Salesforce.
Usually, no. Most native integrations are "forward-looking," meaning they only sync data created or updated *after* you activate the connection. To move historical data, you will likely need to perform a one-time CSV export/import manually.
Buyer Guide
Not sure which tool is the best fit? Compare all options side-by-side.
Build your full stack map, see all connections and gaps at once.