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.
How it runs
The automated pipeline, trigger to output.
- TriggerNew labeled submission email in GmailGmail
- ActionRedact name and contact details from attachmentOpenAI
- LogicRoute low-confidence redactions to manual review
- ActionUpload blind-coded file to Google Drive folderGoogle 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
- 1A new message in the recruiting Gmail inbox matching the submission label triggers the run.
- 2An OpenAI step reads the attachment text and redacts name, email, phone, and address, replacing them with a generated blind code.
- 3The workflow uploads the redacted document to the Google Drive review folder under the blind code.
- 4A logic step checks whether redaction confidence was high; low-confidence files are flagged for manual review instead of auto-filing.
- 5Recruiting receives a Slack summary listing the new blind code and its status.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect Google DriveDocs, sheets, slides, files.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More HR & Recruiting workflows
Route interview feedback by score the moment it is submitted
Receives each interviewer's scorecard via webhook, normalizes the rating, and routes strong-yes feedback to fast-track and any flagged concern to the recruiter.
Loom intake to recruiter handoff email
Transcribes a hiring manager's Loom intake, summarizes the role, and emails a recruiter handoff brief via Outlook with clarifying questions when details are missing.
New-hire equipment order email to IT and vendor
On a scheduled lead-time before each start date, drafts and sends an equipment order email (laptop, monitor.
Compile interview scorecards into a hire-decision packet
When every interviewer has submitted their scorecard in Notion, automatically aggregates the scores, builds a one-page decision packet in Google Drive.
Assemble and send the debrief packet after the final interview
Triggered when a candidate's final interview ends on the calendar, it waits a short window for scorecards, compiles the aggregated packet to Google Drive.
New-Hire Credential Intake to Renewal Calendar Holds
When a new credential is added to the tracker, it validates the record, files the document.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.

Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.
