Delete Contact
hubspot.delete_contact
ActionCRM & salesconnection required
Calls the HubSpot API with the connection's credentials.
Archive one contact with DELETE /crm/v3/objects/contacts/{contactId}.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- HubSpot
- Secret shape
- the HubSpot private-app token, or {"token": "…"}
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
contact_id The HubSpot record id of the contact to archive. | string | Yes | — | — | 101 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"contact_id": "101"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok True once HubSpot accepted the archive. | boolean | — |
id The record id that was archived. | string | — |
{
"id": "",
"ok": false
}Notes
- A delete archives the record: HubSpot moves it to the recycling bin, where it can be restored for 90 days, and keeps counting against portal limits.
See Delete Contact run in a workflow.
In a technical demo we add the HubSpot connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.