Pipedream HubSpot → n8n

7 Pipedream HubSpot actions and 5 event sources, and the n8n nodes they become. Converted nodes keep your configured values; expressions like {{steps.x.$return_value}} are rewritten to n8n expressions. Pipedream app slug: hubspot.

Actions

Pipedream action	n8n	Fit	Notes
hubspot-create-or-update-contact	Hubspot contact → upsert	Check output	n8n always upserts by email (v1 createOrUpdate). PD only updates on a 409 conflict when updateIfExists=true and otherwise throws on an existing contact. With updateIfExists=false the n8n node silently updates instead of failing. The named n8n contact fields…
hubspot-create-contact	Hubspot contact → upsert	Check output	Historical key still present in old workflows. propertyGroups only controlled which dynamic props were shown. n8n upserts even when updateIfExists=false.
hubspot-create-deal	Hubspot deal → create	Check output	n8n posts to /deals/v1/deal (legacy). Stage and pipeline are internal IDs in both.
hubspot-create-company	Hubspot company → create	Check output	n8n posts to /companies/v2/companies (legacy).
hubspot-get-contact	Hubspot contact → get	Check output	additionalProperties is not needed because the v1 profile returns every valued property. Do not map it to additionalFields.propertiesCollection: n8n sends it as `properties` (the v1 API expects `property`), so it would be ignored anyway. The contactId…
hubspot-search-crm	Http Request	Check output	HTTP fallback because the n8n HubSpot node only searches per resource with its own filter UI, has no generic object type, and returns other shapes. PD also validated searchProperty against the schema's searchableProperties (not replicated).…
hubspot-add-contact-to-list	Http Request	Check output	HTTP fallback is deliberate. n8n has contactList:add, but it calls the legacy v1 /contacts/v1/lists/{listId}/add, which uses legacy list IDs (PD's v3 ILS listId differs) and contact vids/emails. PD only offers static (MANUAL/SNAPSHOT) lists.

Triggers (event sources)

Pipedream trigger	n8n	Fit	Notes
hubspot-new-or-updated-contact	Hubspot Trigger	Partial	Polling vs webhook. Requires a HubSpot developer app (hubspotDeveloperApi) whose webhook target URL is overwritten by the trigger, with one n8n trigger per app. `lists` filtering (PD checks list memberships) needs a downstream IF. A closer polling equivalent…
hubspot-new-or-updated-deal	Hubspot Trigger	Partial	Polling vs webhook. Same developer-app requirement as contacts. Alternative: Schedule Trigger + HubSpot deal:getRecentlyCreatedUpdated + dedupe.
hubspot-new-or-updated-company	Hubspot Trigger	Partial	Polling vs webhook. Same developer-app requirement. Alternative: Schedule Trigger + HubSpot company:getRecentlyCreatedUpdated + dedupe.
hubspot-new-contact	Hubspot Trigger	Check output	Removed from the registry on 2024-07-01 (replaced by hubspot-new-or-updated-contact with newOnly=true); old workflows may still reference it. Polling vs webhook; needs a hubspotDeveloperApi app.
hubspot-new-deal	Hubspot Trigger	Check output	Removed 2024-07-01 (replaced by hubspot-new-or-updated-deal newOnly=true). Polling vs webhook; needs a hubspotDeveloperApi app.

Credentials

Create a HubSpot credential in n8n (type hubspotOAuth2Api). Converted nodes reference it by name, so n8n links it on import when the names match. Pipedream connected accounts can't be exported and are deleted by April 30, 2027.

What "Fit" means

Direct: same operation, same inputs. Check output: the n8n node returns a different JSON shape, so later steps that read its result need a look. Partial: some options have no n8n equivalent. Mappings verified on 2026-10-13 against the Pipedream registry and n8n source.

Questions

Does n8n have a HubSpot node?+

Yes. 5 of the 7 Pipedream HubSpot actions listed here map to a native n8n node; 2 map to n8n's HTTP Request node with the HubSpot credential.

Will my Pipedream HubSpot connection move to n8n?+

No. Pipedream exports only an account ID, never the token, and deletes connected accounts by April 30, 2027. Create a HubSpot credential in n8n (type hubspotOAuth2Api) and select it on the converted nodes.

Are Pipedream HubSpot triggers supported in n8n?+

5 of the 5 Pipedream HubSpot event sources listed here have an n8n trigger node. The rest are rebuilt with a Schedule Trigger that polls the API, or a Webhook node.

What happens to code steps that call the HubSpot API?+

Code steps keep working through a compatibility layer, and tokens read via this.<app>.$auth move to a secrets block in the Code node. Steps that use an npm SDK are rewritten to plain HTTP calls so they run on n8n Cloud.

Other apps

Airtable Asana Calendly ClickUp Discord Dropbox Email (SMTP)GitHub Gmail Google Calendar Google Drive Google Gemini All apps →