Safety Rails & Auditing#

Automated deletion is powerful, but it carries inherent risk. A poorly configured workflow trigger could inadvertently wipe out a large segment of your database. Delete is built to throttle itself and leave a paper trail for every action it takes.

Per-Request Rate Limiting#

Delete caps how fast delete tasks can be enqueued to HubSpot. When a workflow enrolls a large batch of records, Delete does not fire them at HubSpot all at once — it processes them in batches of 100 and rate-limits the enqueue rate to a steady, sustainable throughput.

In practice this means:

• Large workflow enrollments (thousands of records) drain through Delete smoothly instead of triggering HubSpot API 429s.
• If HubSpot does return a rate-limit response (429) on a batch, Delete surfaces a Retry-After header and lets the task queue retry the batch automatically.

You do not need to configure this — it’s on by default for every portal.

Automatic Retries#

Every batch that fails with a transient error (HubSpot 5xx, network blip, timeout) is retried up to three times before it’s marked failed. Retries use exponential-style backoff so Delete doesn’t compound a HubSpot outage.

If a batch ultimately fails after retries, the failure is logged, HubSpot is told the workflow action failed, and the workflow enrollment can be re-run manually once the underlying issue is resolved.

GDPR Delete Is Permanent#

Unlike Standard Delete (which lands in HubSpot’s recycle bin), GDPR Delete is immediate and irreversible. Once a GDPR delete action runs, the record is gone — there is no recycle bin and no recovery. Reserve GDPR Delete for genuine right-to-erasure requests.

Audit Trail#

Every batch delete Delete issues is recorded. The audit entry captures:

• The timestamp of the action.
• The object type and record IDs included in the batch.
• The deletion mode used (Standard or GDPR).
• The HubSpot workflow and callback IDs that triggered the action.
• The final status returned by HubSpot (success, bad request, rate-limited, error).

Use these records during compliance audits or when reconciling a workflow run with downstream systems.