ACTION_ID: hubspot_update_object
NAME: HubSpot: Update Object
CATEGORY: CRM
CREDITS: 0

Update an object in HubSpot.

PREREQUISITE: HubSpot account connection — the user must create it in the Floqer UI
(Connections page); an agent cannot. Without it the action fails the row with
a connection / authentication error. Confirm it exists before configuring.

1. INPUTS

choose_hubspot_object (static dropdown, required)
  Choose HubSpot Object. Values:
    - { value: "contacts", label: "Contact" } (default)
    - { value: "companies", label: "Company" }
    - { value: "deals", label: "Deal" }
    - { value: "leads", label: "Lead" }
    - { value: "calls", label: "Call" }
    - { value: "meetings", label: "Meeting" }
    - { value: "users", label: "User" }
  Users are update-only in HubSpot (there is no create endpoint) and
  expose just nine settable properties: hs_additional_phone,
  hs_availability_status, hs_job_title, hs_main_user_language_skill,
  hs_out_of_office_hours, hs_secondary_user_language_skill,
  hs_standard_time_zone, hs_uncategorized_skills, hs_working_hours.

hubspot_object_id (string, required)
  The unique identifier of the HubSpot record to update, e.g.
  44542243321. Usually a reference to an upstream
  `hubspot_lookup_object` output.

hubspot_object_properties (dynamicJsonArray, optional)
  HubSpot Object Properties. Select the properties to update. Values
  from hubspot_properties.

2. OUTPUTS

id (string) — ID. Placeholder: "431231243".
properties (json) — Properties.
created_at (date) — Created At.
update_at (date) — Update At.
archived (boolean) — Archived.

3. HOW TO CONFIGURE

Resolve the property list via Get Action Field Options before
configuring:

  POST /api/v1/workflows/{workflow_id}/sheets/{sheet_id}/actions/{action_instance_id}/options/hubspot_object_properties
       (body: { "context": { "hubspot_object": "contacts" } })

Configure Action body:

{
  "inputs": {
    "choose_hubspot_object": "contacts",
    "hubspot_object_id": "{{hubspot_lookup_object_1.id}}",
    "hubspot_object_properties": [
      { "name": "lifecyclestage", "value": "customer" },
      { "name": "phone",          "value": "{{input.phone}}" }
    ]
  }
}

Field-by-field:
  - choose_hubspot_object       Object type — `contacts` or `companies`.
                                Must match the type of the record being
                                updated.
  - hubspot_object_id           HubSpot's internal record ID — usually a
                                `{{ref}}` to an upstream
                                `hubspot_lookup_object` output.
  - hubspot_object_properties   `[{name, value}]` — `name` is HubSpot's
                                internal property name. Fetch valid
                                names via Get Action Field Options.

4. KEY NOTES

- Updates by HubSpot record ID. Pair with `hubspot_lookup_object`
  upstream when the ID is not already known on the row.
- Property names are HubSpot's internal names (`firstname`, not
  `first_name`) — fetch via Get Action Field Options.
- The HubSpot connection must live on the API key's user account.
  If the connection lives under a different team member, Get Action
  Field Options returns a 424.
- For create-or-update by a unique property (e.g. email), prefer
  `hubspot_upsert_object`.

5. WHERE IT FITS IN A WORKFLOW

Pattern: hubspot_lookup_object -> workflow_if_else (found) ->
hubspot_update_object.

6. WHEN TO USE

Use hubspot_update_object to update an existing HubSpot record by ID.

7. WHEN NOT TO USE

Need create-or-update by unique property
  -> action-detail/hubspot_upsert_object.txt

Need to create
  -> action-detail/hubspot_create_object.txt

Need to look up records
  -> action-detail/hubspot_lookup_object.txt

Last updated: 2026-05-25.