HR & RECRUITING
De-Identify Candidate GitHub Take-Home Repos
When a candidate's code take-home repo is submitted, clones it, rewrites the git author identity and README to a blind code.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives candidate repo URLHTTP webhook
- ActionClone repo and rewrite commit author identityShell
- ActionScrub README and configs of identifiersOpenAI
- ActionCreate private blind-coded reviewer repo and pushGitHub
- OutputSend reviewer repo link to recruiting SlackSlack
What it does
Makes code take-homes truly blind. Candidate repositories carry identity everywhere: commit author names, email addresses, the README header, even the repo name. This workflow ingests a submitted repo, rewrites every author commit to a neutral anonymous identity, removes name traces from the README, and publishes a private reviewer copy named only by blind code.
When to use it
Use it for engineering hiring where candidates submit a Git repository as their take-home. Reviewers should assess code quality, not recognize a name in the commit log. Best when you already collect submissions as repo links or zipped repos in an intake channel.
How it works
- 1An incoming webhook fires with the candidate's submitted repo URL.
- 2A shell step clones the repo and rewrites all commit author and committer fields to an anonymous identity tied to a freshly minted blind code.
- 3An OpenAI step scrubs the README and config files of any name, email, or handle.
- 4The workflow creates a new private GitHub repo named by blind code and pushes the rewritten history.
- 5Recruiting gets a Slack message with the reviewer repo link and the code mapping.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect GitHubRepos, issues, pull requests, actions.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, 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 this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.