HubSpot - Delete Object
↩ Part of the HubSpot integration.
Description
Section titled “Description”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.
Configuration
Section titled “Configuration”| Field | Type | Required | Description |
|---|---|---|---|
credentials_id | credentials | Yes | HubSpot credential |
object_type | text | Yes | Object type: contacts, companies, deals, tickets. Defaults to contacts if left empty |
object_id | text | Yes | Id of the object to archive |
Both object_type and object_id accept dynamic variables.
Credentials
Section titled “Credentials”This module requires a HubSpot credential:
| Field | Description |
|---|---|
token | Private App token (starts with pat-), from HubSpot → Settings → Integrations → Private Apps |
Output
Section titled “Output”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 }Usage Example
Section titled “Usage Example”Archive a contact
Section titled “Archive a contact”{ "credentials_id": "hubspot_marketing", "object_type": "contacts", "object_id": "{{data.contactId}}"}Archive a lost deal
Section titled “Archive a lost deal”{ "credentials_id": "hubspot_sales", "object_type": "deals", "object_id": "{{data.dealId}}"}Archive a resolved ticket
Section titled “Archive a resolved ticket”{ "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
404means the record does not exist or was already archived. It is not retried. - If
object_idresolves 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.
Related Nodes
Section titled “Related Nodes”- HubSpot: Get object — snapshot the record before archiving it.
- HubSpot: Search objects — find the records that should be archived.
- HubSpot: Update object — flag the record instead of archiving it.