Per-pair page

HubSpot + Salesforce: bridge two CRMs without losing data.

Sync HubSpot contacts and Salesforce records during migrations, dual-CRM operations, or M&A scenarios. Avoid sync loops with directional field ownership.

Connect Salesforce to HubSpot — start free See reverse direction

Trigger app

Salesforce as the trigger

Workflows fire when something happens in Salesforce.

Salesforce has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.

Action app

HubSpot as the action

Workflows do something in HubSpot, instantly.

See all 23 actions →

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Salesforce → HubSpot

When something happens in Salesforce, do it in HubSpot.

0 Salesforce triggers wired to 23 HubSpot actions.

HubSpot → Salesforce

Or fire it the other way around.

18 HubSpot triggers wired to 13 Salesforce actions downstream.

See HubSpot → Salesforce →

How it works

Connect Salesforce and HubSpot in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize Salesforce and HubSpot
Open TinyCommand, authorize Salesforce and HubSpot once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Salesforce trigger
Drop the Salesforce → New event trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/salesforce.event
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the HubSpot action
Drop the HubSpot → Create Company action below it. Map fields from the Salesforce payload into the HubSpot inputs.
hubspot.create-company
5
Publish
Publish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Salesforce + HubSpot.

When do organizations run both HubSpot and Salesforce?

During CRM migrations (gradual switchover), in M&A scenarios (acquired company had different CRM), or when different business units chose different tools. The pair keeps both in sync while you decide.

How do I sync HubSpot contacts into Salesforce?

HubSpot Contact Created or Updated → Salesforce Find or Create Lead/Contact by email → Update fields. Use HubSpot ID as Salesforce external_id custom field for idempotent upserts.

Can I sync Salesforce Opportunities back to HubSpot Deals?

Yes. Salesforce Opportunity Updated → HubSpot Find or Create Deal by Salesforce ID custom field → Update Deal with stage, amount, close date. Pick one side per field as source-of-truth.

How do I avoid sync loops?

Pick one direction per field. HubSpot owns marketing fields (lifecycle, lead source); Salesforce owns sales fields (stage, owner). Or vice versa. Document field ownership rules clearly.

Can I sync custom objects between HubSpot and Salesforce?

Possible but complex. HubSpot custom objects map to Salesforce custom objects (__c suffix). Maintain a field-level mapping table; expect this to be a multi-week setup effort.

How do I respect Salesforce API limits when syncing high HubSpot volume?

Use Salesforce Bulk/Composite API for batched updates. Filter HubSpot triggers to changes only (not every contact, every update). Most orgs stay under SFDC's 15K-150K daily call limit.