HR & RECRUITING

Screen and route new ATS applications via webhook

Receives a new-application webhook from your ATS, scores the candidate against the role.

CategoryHR & Recruiting
Enginesim
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew-application webhook from ATSHTTP webhook
  • ActionScore candidate against role via OpenAIOpenAI
  • LogicBranch on tier: advance vs reject
  • ActionCreate recruiter task in Linear for advancing candidatesLinearLinear
  • OutputSend polite decline email for rejected candidatesGmailGmail

What it does

Acts as an intelligent intake valve on your applicant tracker. Each new application is scored, then routed two ways: promising candidates become an actionable recruiter task, and clear non-fits receive a courteous decline so no one is left waiting.

When to use it

Use it when your ATS can fire a webhook on new applications and you want immediate triage that both protects recruiter time and keeps candidate experience clean. Best where rejection volume is high enough that silence would hurt your brand.

How it works

  1. 1An incoming webhook from the ATS delivers the new application payload.
  2. 2OpenAI scores the candidate against the role's criteria and returns a tier and rationale.
  3. 3A logic branch splits on tier: Strong/Maybe versus Reject.
  4. 4For Strong/Maybe, a Linear issue is created in the recruiting project with the score, rationale, and candidate link assigned to the role owner.
  5. 5For Reject, a respectful, role-specific decline email is sent to the candidate via Gmail.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect LinearIssues, projects, cycles, triage.
  4. 4
    Connect GmailRead, draft, send, label.
  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.