FlowmageDocs
HubSpot

Create or update record

BetaChanges data

Creates a HubSpot record, or updates the one that already has this key.

Settings

SettingWhat it is
ConnectionRequiredThe HubSpot connection the step signs in with.
Object"contacts" or "companies" or "deals" or "tickets" or "notes" or "tasks" or "calls" or "meetings" or "emails" or "leads" or "products" or "line_items" or "custom"
Custom object type idThe object type id, e.g. 2-1234567. The List properties node shows it.
Key propertyThe unique-identifier property HubSpot matches on — email for contacts, or any property marked as a unique identifier. HubSpot does not support partial upserts when the key is email on contacts, so every property you leave out stays as it was only because this node always sends the whole set.
Key valueRequiredtext
PropertiesOne row per property, keyed by its internal name.
Technical details
KeyValue
connectiontexta connection id from `requires.connections` (provider `hubspot`)
object"contacts" or "companies" or "deals" or "tickets" or "notes" or "tasks" or "calls" or "meetings" or "emails" or "leads" or "products" or "line_items" or "custom", by default "contacts"
customObjectTypetextused when `object` is "custom"
idPropertytext, by default "email"
idValuetextits `{{ }}` must give a string
propertiesobject (any keys), by default {}

Output

FieldType
recordIdstring
recordobject
Sample output, and the expression for each field
  • record
    • id"1"
  • recordId"1"

Errors

When a step of this node stops a run, the run page shows a code. Look it up:

HubSpot errors

25 codes

Common errors

93 codes

Example step

The step as a flow file holds it. Replace each value in <…>.

{
  "config": {
    "connection": "<connection id>",
    "customObjectType": "",
    "idProperty": "email",
    "idValue": "<key value>",
    "object": "contacts",
    "properties": {}
  },
  "label": "Create or update record",
  "type": "hubspot.upsertRecord",
  "version": 1
}