Update a contact via the HubSpot catalog gateway (write→ask)
Updates an existing HubSpot contact via the `recued-core.hubspot.contact.update` Tier-P op-step (exercising path-param substitution: the target contact id goes into /crm/v3/objects/contacts/{{contact_id}}). `contact.update` is WRITE-tier, so the call routes through the gateway's preflight approval: the run pauses (awaiting_approval), surfaces a `notification.ask` ('Approve updating this contact?'), and only after you approve does it PATCH the contact — emitting a `connection.gateway` audit row. Prerequisite: the HubSpot contacts write grant must be in place; write ops are NOT auto-granted at enrollment (read-tier only, Invariant 3), so grant it explicitly first.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
hubspot
setting
=
job title
setting
=
contact id
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.