Right-to-be-forgotten / data subject erasure request internal queue trigger
One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.
Professional
Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Marketing Hub Professional.
OutcomeAn erasure request gets logged into one queue the moment it comes in, with a task and a deadline reminder, so compliance never misses one even though HubSpot cannot perform the actual deletion as a workflow action.
Workflow mapmarketing-ops-019
When to use it, when not to
Use it
- Use once you have a way for a contact or an internal team member to flag "this person asked to be forgotten," whether through a form, a support ticket, or a manually set property.
- Use to make sure a request is never handled only by memory or a Slack message that scrolls away.
Read more on when to use itShow less
Skip it
- Do not use this fiche as the deletion mechanism itself. HubSpot has no workflow action that deletes a contact record or its associated data. Deletion happens through the GDPR delete tool in Settings or the API, run manually by a person after legal review, never automatically.
- Do not use if your process already runs the request through a dedicated case management or legal tool with its own SLA tracking; duplicating the queue there adds confusion.
Read more on when to skip itShow less
The rest of this spec
Not the workflow you needed?
More in Marketing ops
50 specs in this section
Read 12 complete specs before you pay.
One per category, same format as the paid ones. Email only, no card.
We email the link, then a short note when specs change. Nothing else.
Here it is. Download the pack now (.zip) The link is in your inbox too.
Read the free Marketing ops spec