Quick overview
Quick overview This workflow receives new job orders from an ATS webhook, optionally extracts structured requirements using Anthropic, scores and filters matching candidates, and upserts the job, campaign, candidates, and scheduled enrollments into Supabase, with an optional Slack webhook summary. How it works Receives a job order via an incoming webhook (or runs manually) and normalizes the payload into a consistent job spec using a configurable ATS field map. If the job order has too few skills, calls the Anthropic Messages API to extract required and nice-to-have skills from the job description and merges them into the job spec. Searches candidates in the configured ATS via its API (or falls back to a bundled sample candidate pool) and normalizes records by formatting phone numbers to E.164 and deduplicating people. Scores each candidate against the job spec using transparent, rule-based weights and produces a ranked list with human-readable match reasons. Fetches opt-outs, recent contact history, and active enrollments from Supabase (or uses a demo stub) and gates candidates out based on suppression rules, cooldown windows, and a minimum score threshold. Upserts the job order, campaign, and candidate records into Supabase and inserts enrollments for the top-ranked eligible candidates with the first outreach touch scheduled (not sent). Builds a run summary and optionally posts it to Slack via an incoming webhook. Setup Configure your ATS to send “job order created” events to the workflow webhook URL and update the ATS vendor settings, base URL, token, and ATS_FIELDS mapping in the config. Add Supabase connection details (URL and service role key) and ensure your Supabase project has the required tables/RPC (including the engagement_history function) used for suppression and upserts. (Optional) Add an Anthropic API key and model settings if you want the workflow to extract skills from job descriptions. (Optional) Add a Slack incoming webhook URL to receive the launch summary message. Review the demo/test controls in config (DEMO_MODE, TEST_RUN, DRY_RUN_DB) before enabling production writes. Customization Part 1 of 3 parts Candidate Engine Workflow. Part 2 : https://n8n.io/workflows/19776-send-scheduled-sms-and-voice-outreach-from-supabase-via-twilio-and-retell/ Part 3 : https://n8n.io/workflows/19777-qualify-inbound-candidate-replies-and-book-interviews-with-retell-and-google-calendar/. An n8n automation workflow template by Atharva Ashtekar.
Atharva Ashtekar
web
free
Others in the same category, ranked by how often they are opened.
