Automation library · Data collection

Track data deletion requests from Gmail with Jira and BigQuery

Started by an arriving email, and works across Gmail. 11 steps, 1 branch: a working afternoon to understand properly.

Medium

11 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 2Logic 3Service 6

The steps in the order they run, from what starts it.

  1. 1Manual test triggerManual triggerStarts it
  2. 2Watch privacy request inboxGmail triggerStarts it
  3. 3Set workflow variablesSetLogic
  4. 4Normalize and classify privacy requestCodeLogic
  5. 5Check if request is clear enoughIfLogic
  6. 6Create Jira privacy taskHttp RequestService
  7. 7Create manual review Jira taskHttp RequestService
  8. 8Insert audit row in BigQueryHttp RequestService
  9. 9Send Slack manual review alertHttp RequestService
  10. 10Send Slack privacy alertHttp RequestService
  11. 11Create Gmail confirmation draftHttp RequestService

How it's built

Starts on
An arriving email
Steps
11, with 1 branch
Size
Medium: a working afternoon
Connects to
Gmail
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Gmail account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an arriving email.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 11 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 11 steps before you point it at anything that matters.