Track data deletion requests from Gmail with Jira, BigQuery, and Slack
Ready for 3.0What this workflow does
This workflow has 11 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects Gmail. It also calls slack.com and gmail.googleapis.com over HTTP.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).
- Set workflow variables (Edit Fields (Set)): sets 11 fields: jira_base_url, jira_project_key, jira_issue_type…
- Normalize and classify privacy request (Code): runs custom JavaScript code
- Check if request is clear enough (If): checks a condition and branches into true / false
- Create Jira privacy task (HTTP Request): calls an HTTP API (POST)
- Create manual review Jira task (HTTP Request): calls an HTTP API (POST)
- Insert audit row in BigQuery (HTTP Request): calls an HTTP API (POST)
- Send Slack manual review alert (HTTP Request): calls slack.com (POST)
- Send Slack privacy alert (HTTP Request): calls slack.com (POST)
- Create Gmail confirmation draft (HTTP Request): calls gmail.googleapis.com (POST)
Services it uses
HTTP calls to: slack.com, gmail.googleapis.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
- Still check Gmail Trigger below v1.4 runs as v1.4 (drafts skipped, max emails per poll) (Watch privacy request inbox).
Nodes used (6)
- Manual Trigger
n8n-nodes-base.manualTrigger - Gmail Trigger
n8n-nodes-base.gmailTrigger - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest
From the author
Quick Overview This workflow monitors a Gmail inbox for potential privacy/data deletion requests, classifies each email, creates the appropriate Jira issue, logs a minimal audit record to BigQuery, and alerts the team in Slack, with an optional Gmail…