HR & RECRUITING

Redact PII from Emailed Take-Home Attachments

Monitors a recruiting inbox for take-home submissions, extracts the attachment, redacts the candidate's name and contact details from the document.

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew labeled submission email in GmailGmailGmail
  • ActionRedact name and contact details from attachmentOpenAI
  • LogicRoute low-confidence redactions to manual review
  • ActionUpload blind-coded file to Google Drive folderGoogle DriveGoogle Drive
  • OutputSend blind code and status to recruiting SlackSlack

What it does

Handles take-homes that arrive by email. When a candidate replies to an assignment with their work attached, this workflow pulls the attachment, redacts the candidate's name, email, phone, and address from the document text, swaps in a blind code, and stores the cleaned file in a shared Google Drive review folder so reviewers never see the originating email.

When to use it

Use it when your submission channel is a recruiting email alias rather than a portal. It removes the most common identity leak in email-based intake: the sender address and the name typed into the cover page. Pairs well with a downstream reviewer-assignment workflow.

How it works

  1. 1A new message in the recruiting Gmail inbox matching the submission label triggers the run.
  2. 2An OpenAI step reads the attachment text and redacts name, email, phone, and address, replacing them with a generated blind code.
  3. 3The workflow uploads the redacted document to the Google Drive review folder under the blind code.
  4. 4A logic step checks whether redaction confidence was high; low-confidence files are flagged for manual review instead of auto-filing.
  5. 5Recruiting receives a Slack summary listing the new blind code and its status.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GmailRead, draft, send, label.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect Google DriveDocs, sheets, slides, files.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.