HubSpot
CRM & salesBearer tokenConnection test available
Create CRM contacts in HubSpot (private-app token).
OCNORA ships 53 typed HubSpot operations and 1 trigger. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run. Endpoints not covered by a typed node are called at https://api.hubapi.com through the HTTP node with the same credential.
Before you connect HubSpot
- Authentication
- Bearer token
- Credential
- {"token", "developer_api_key", "client_secret"}the HubSpot private-app token, or {"token": "…"}the HubSpot private-app token
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
- Prerequisites
- The webhooks API authenticates with the developer API key of the account that owns the app, and signatures are verified with the app's client secret. The private-app token alone cannot do either.
Prerequisites are taken from the connection notes in this provider’s node contracts; each node’s reference page says which apply to it.
What you can do with HubSpot
Operations, grouped by what they do to your data, plus 1 trigger that start a run.
Create and send 8
Read and search 27
Delete and cancel 8
Other operations 3
A sample HubSpot workflow
- 1CRM Eventtrigger.hubspot_eventStart a run when a HubSpot contact, company, deal or ticket changes.
- 2Get Companyhubspot.get_companyRead one company with GET /crm/v3/objects/companies/{companyId}. Set `id_property` to domain to look the company up by domain instead of by id.
- 3Add List Membershubspot.add_list_membersAdd records to a manual list with PUT /crm/v3/lists/{listId}/memberships/add. Records already in the list are left alone, so the call is safe to repeat.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Triggers 1
Operations 53
- Add List MembersAdd records to a manual list with PUT /crm/v3/lists/{listId}/memberships/add. Records already in the list are left alone, so the call is safe to repeat.hubspot.add_list_members
- Batch Read ContactsRead up to 100 contacts in one call with POST /crm/v3/objects/contacts/batch/read, by record id or by a unique property such as email.hubspot.batch_read_contacts
- Batch Upsert ContactsCreate or update up to 100 contacts in one idempotent call with POST /crm/v3/objects/contacts/batch/upsert, matched on a unique property. This is the safe choice for a workflow that may run twice.hubspot.batch_upsert_contacts
- Change Deal StageMove one deal to a pipeline stage with PATCH /crm/v3/objects/deals/{dealId}. This is the narrow, safe form of Update Deal: it sends only the stage, so no other property can be overwritten by accident.hubspot.change_deal_stage
- Create AssociationAssociate two records with the v4 association API. With no `association_type_id` this is the default, unlabelled association (PUT /crm/v4/objects/{from}/{id}/associations/default/{to}/{id}); with one it is the labelled form.hubspot.create_association
- Create CompanyCreate a company in HubSpot CRM.hubspot.create_company
- Create ContactCreate a contact in HubSpot CRM.hubspot.create_contact
- Create DealCreate a deal in HubSpot CRM.hubspot.create_deal
- Create NoteLog a note on the CRM timeline with POST /crm/v3/objects/notes, optionally attaching it to a record in the same step.hubspot.create_note
- Create RecordCreate a record of any CRM object type with POST /crm/v3/objects/{objectType}. Use this for a custom object, or where the object type is decided at run time; the named create nodes are the same call with the type filled in.hubspot.create_object
- Create TicketCreate a support ticket with POST /crm/v3/objects/tickets. HubSpot requires a subject and a pipeline stage id; read the ids with hubspot.list_pipeline_stages for object type tickets.hubspot.create_ticket
- Delete AssociationRemove every association between two records with DELETE /crm/v4/objects/{fromType}/{id}/associations/{toType}/{id}. Labelled and unlabelled associations between the pair all go.hubspot.delete_association
- Delete CompanyArchive one company with DELETE /crm/v3/objects/companies/{companyId}.hubspot.delete_company
- Delete ContactArchive one contact with DELETE /crm/v3/objects/contacts/{contactId}.hubspot.delete_contact
- Delete DealArchive one deal with DELETE /crm/v3/objects/deals/{dealId}.hubspot.delete_deal
- Delete NoteArchive one note with DELETE /crm/v3/objects/notes/{noteId}.hubspot.delete_note
- Delete RecordArchive one record of any CRM object type with DELETE /crm/v3/objects/{objectType}/{recordId}.hubspot.delete_object
- Delete TicketArchive one ticket with DELETE /crm/v3/objects/tickets/{ticketId}.hubspot.delete_ticket
- Get CompanyRead one company with GET /crm/v3/objects/companies/{companyId}. Set `id_property` to domain to look the company up by domain instead of by id.hubspot.get_company
- Get ContactRead one contact with GET /crm/v3/objects/contacts/{contactId}. Set `id_property` to email to look the contact up by address instead of by id.hubspot.get_contact
- Get DealRead one deal with GET /crm/v3/objects/deals/{dealId}.hubspot.get_deal
- Get ListRead one list's definition with GET /crm/v3/lists/{listId} — its name, size, processing type and processing status.hubspot.get_list
- Get NoteRead one note with GET /crm/v3/objects/notes/{noteId}.hubspot.get_note
- Get RecordRead one record of any CRM object type with GET /crm/v3/objects/{objectType}/{recordId}, by record id or by a unique property.hubspot.get_object
- Get OwnerRead one CRM owner with GET /crm/v3/owners/{ownerId}, by owner id or — with `id_property` set to userId — by HubSpot user id.hubspot.get_owner
- Get PropertyRead one property definition with GET /crm/v3/properties/{objectType}/{propertyName}, including the allowed options of a dropdown or radio property.hubspot.get_property
- Get TicketRead one ticket with GET /crm/v3/objects/tickets/{ticketId}.hubspot.get_ticket
- List Association LabelsList every association label defined between two object types, with GET /crm/v4/associations/{fromType}/{toType}/labels. This is where an `association_type_id` comes from — user-defined ids are per portal and cannot be hardcoded.hubspot.list_association_labels
- List AssociationsList every record of one object type associated with a record, with GET /crm/v4/objects/{fromType}/{id}/associations/{toType}.hubspot.list_associations
- List CompaniesPage through every company with GET /crm/v3/objects/companies. Feed the `after` output back in to walk the whole collection.hubspot.list_companies
- List ContactsPage through every contact with GET /crm/v3/objects/contacts, newest cursor first. Feed the `after` output back in to walk the whole database.hubspot.list_contacts
- List DealsPage through every deal with GET /crm/v3/objects/deals. Feed the `after` output back in to walk the whole pipeline.hubspot.list_deals
- List List MembersPage through the record ids in a list with GET /crm/v3/lists/{listId}/memberships, ordered by record id.hubspot.list_list_members
- List NotesPage through logged notes with GET /crm/v3/objects/notes. Ask for `hs_note_body,hs_timestamp` in `properties` — HubSpot does not return them by default.hubspot.list_notes
- List RecordsPage through every record of a CRM object type with GET /crm/v3/objects/{objectType}. Feed the `after` output back in to walk the whole collection.hubspot.list_objects
- List OwnersList CRM owners with GET /crm/v3/owners — the ids that a `hubspot_owner_id` property expects. Filter by `email` to resolve one person.hubspot.list_owners
- List Pipeline StagesList one pipeline's stages in display order with GET /crm/v3/pipelines/{objectType}/{pipelineId}/stages. The stage ids this returns are what `dealstage` and `hs_pipeline_stage` want on a write.hubspot.list_pipeline_stages
- List PipelinesList the pipelines defined for an object type with GET /crm/v3/pipelines/{objectType} — deals and tickets each have their own.hubspot.list_pipelines
- List PropertiesList every property defined on an object type with GET /crm/v3/properties/{objectType}, custom properties included. This is how a workflow discovers the internal names the other nodes need.hubspot.list_properties
- List TicketsPage through every ticket with GET /crm/v3/objects/tickets. Feed the `after` output back in to walk the whole queue.hubspot.list_tickets
- Merge ContactsMerge one contact into another with POST /crm/v3/objects/contacts/merge. The primary contact survives and absorbs the other's activities, associations and any property it has no value for.hubspot.merge_contacts
- Remove List MembersRemove records from a manual list with PUT /crm/v3/lists/{listId}/memberships/remove. The records themselves are not touched.hubspot.remove_list_members
- Search CompaniesSearch companies with POST /crm/v3/objects/companies/search. With no `property_name` a property filter matches on `name`.hubspot.search_companies
- Search ContactsSearch HubSpot contacts by a single property filter (e.g. email equals).hubspot.search_contacts
- Search DealsSearch deals with POST /crm/v3/objects/deals/search. With no `property_name` a property filter matches on `dealname`.hubspot.search_deals
- Search RecordsSearch any CRM object type with POST /crm/v3/objects/{objectType}/search, either with one property filter or with HubSpot's own filterGroups body.hubspot.search_objects
- Search TicketsSearch tickets with POST /crm/v3/objects/tickets/search. With no `property_name` a property filter matches on `subject`.hubspot.search_tickets
- Update CompanyUpdate one company with PATCH /crm/v3/objects/companies/{companyId}. Only the fields you fill in are sent; everything else keeps its stored value.hubspot.update_company
Show 5 more
- Update ContactUpdate an existing contact in HubSpot CRM by its id.hubspot.update_contact
- Update DealUpdate one deal with PATCH /crm/v3/objects/deals/{dealId}. Only the fields you fill in are sent; everything else keeps its stored value.hubspot.update_deal
- Update NoteEdit one note with PATCH /crm/v3/objects/notes/{noteId} — its body, its timeline timestamp, or any other note property.hubspot.update_note
- Update RecordPatch one record of any CRM object type with PATCH /crm/v3/objects/{objectType}/{recordId}. Only the properties you send change; everything else keeps its stored value.hubspot.update_object
- Update TicketUpdate one ticket with PATCH /crm/v3/objects/tickets/{ticketId} — move it to another status, change its priority, or edit its text.hubspot.update_ticket
Templates that use HubSpot
- New Airtable record to a HubSpot contactA record added to an Airtable base becomes a HubSpot contact, so the list people keep by hand reaches the CRM.
- Closed-won HubSpot deal to a spreadsheetEvery deal that changes stage is read back and appended to a Google Sheet for finance.
- Welcome e-mail for a new HubSpot contactWhen a contact is created in HubSpot, read it back and send a personalised welcome e-mail.
- Failed payment to a HubSpot ticket and a Slack alertA Stripe payment failure opens a HubSpot ticket against the customer and pings the billing channel.
- New spreadsheet row to a HubSpot contactA new row in a Google Sheet becomes a HubSpot contact, and the team hears about it in Slack.
HubSpot questions
- How does OCNORA authenticate with HubSpot?
- With a stored Bearer token credential, shaped {"token", "developer_api_key", "client_secret"} or the HubSpot private-app token, or {"token": "…"} or the HubSpot private-app token. A connection test can check it when you add it.
- What can I automate with HubSpot?
- 53 typed operations and 1 trigger, each with a reference page listing its config fields and the shapes it emits.
- What if the HubSpot operation I need is not listed?
- Call https://api.hubapi.com from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use HubSpot?
- Yes: 5 templates, listed above.
- How are HubSpot calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first HubSpot workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.