Skip to content

HubSpot - Delete Object

↩ Part of the HubSpot integration.

Archives a record in the HubSpot CRM (DELETE /crm/v3/objects/{object_type}/{id}).

HubSpot’s delete is an archive: the record leaves lists, reports and the search index, but it stays recoverable from the HubSpot UI for a limited period. The node reflects that by returning archived: true.

FieldTypeRequiredDescription
credentials_idcredentialsYesHubSpot credential
object_typetextYesObject type: contacts, companies, deals, tickets. Defaults to contacts if left empty
object_idtextYesId of the object to archive

Both object_type and object_id accept dynamic variables.

This module requires a HubSpot credential:

FieldDescription
tokenPrivate App token (starts with pat-), from HubSpot → Settings → Integrations → Private Apps

HubSpot answers with an empty body, so the node builds a confirmation object:

{
"archived": true,
"id": "701",
"objectType": "contacts"
}

Along with it, _meta:

{ "moduleVersion": "1.0.0", "success": true, "id": "701", "objectType": "contacts", "totalMs": 150 }
{
"credentials_id": "hubspot_marketing",
"object_type": "contacts",
"object_id": "{{data.contactId}}"
}
{
"credentials_id": "hubspot_sales",
"object_type": "deals",
"object_id": "{{data.dealId}}"
}
{
"credentials_id": "hubspot_service",
"object_type": "tickets",
"object_id": "{{data.ticketId}}"
}
  • The delete is an archive, not a hard erase. To wipe personal data permanently — a GDPR erasure request, for example — use HubSpot’s dedicated GDPR endpoint through the HTTP node.
  • Archiving a company or a deal does not delete the objects associated with it; only the association disappears from view.
  • A 404 means the record does not exist or was already archived. It is not retried.
  • If object_id resolves to an empty value, the node stops with a validation error before calling HubSpot.
  • The record is not returned before being archived. If you need a copy, read it with Get object first.