A recruitment pipeline touches more systems than almost any other HR process: an ATS, a resume parser, a calendar, an assessment platform, an e-signature tool, and eventually the onboarding system. This workflow connects all of them end to end, screening every application consistently, routing technical and non-technical roles down genuinely different evaluation paths, and handing off directly into onboarding the moment an offer is accepted rather than leaving that connection to someone's memory.
Workflow diagram
flowchart TD
A[New Application] --> B[Parse Resume]
B --> C[AI Score]
C --> D{Threshold Met?}
D -->|Yes| E[Schedule Screening Call]
D -->|No| F[Polite Rejection] --> G[Tag For Future Roles]
E --> H[Confirmation Email]
I[Screening Complete] --> J[Collect Feedback]
J --> K{Advance?}
K -->|No| L[Log Rejection]
K -->|Yes| M{Role Type}
M -->|Technical| N[Coding Assessment] --> O[Wait Completion]
M -->|Non-Technical| P[Schedule Panel]
O --> Q[Merge]
P --> Q
Q --> R[Final Decision Gate]
R --> S{Hired?}
S -->|Yes| T[Generate Offer] --> U[Send via DocuSign] --> V[Offer Accepted]
V --> W[Trigger Onboarding]
W --> X[Log To Registry]
S -->|No| Y[Final Rejection] Every branch shown here (IF/Switch outcomes) exists as a real conditional in the downloadable JSON, not a simplification for this diagram.
Screening consistency without losing the human decision
AI Score Against Requirements evaluates every application against the specific role's actual requirements, not a generic resume quality heuristic, and Screening Threshold Met? gates who gets an automatic screening call. This does not replace human judgement, it replaces the inconsistency of different recruiters applying different informal bars on different days.
Rejected candidates are not simply discarded. Tag For Future Roles logs them to a searchable candidate pool, since a candidate who is not right for this specific role today is frequently the right fit for a different opening in six months, and that connection is invisible without a system tracking it.
Why technical and non-technical roles need genuinely different paths
Role Type Router is not a cosmetic branch. A coding assessment is the correct next evaluation step for a technical role and actively counterproductive for most non-technical ones, where a structured panel interview evaluates the skills that actually matter. Forcing every candidate through the same generic pipeline is the single most common design mistake in recruitment automation.
Send Coding Assessment and Wait For Assessment Completion use webhook-resume so the workflow costs nothing while waiting, potentially days, for a candidate to complete an assessment, exactly the same pattern used for fulfillment waits in the order-to-cash template.
The handoff into onboarding that most companies never automate
Offer Accepted Webhook triggers Trigger Onboarding Workflow, which calls directly into the Employee Onboarding & Offboarding template with the new hire's details already populated. This single connection eliminates the most common gap in the entire hire lifecycle: the moment between "candidate said yes" and "IT knows a laptop needs ordering," which at most companies depends entirely on someone remembering to loop in HR operations manually.
Node-by-node reference
| Node | Type | Role |
|---|---|---|
| AI Score Against Requirements | HTTP Request | Consistent screening bar per role, not per recruiter |
| Role Type Router | Switch | Technical vs non-technical get genuinely different evaluation paths |
| Wait For Assessment Completion | Wait (webhook resume) | Zero-cost pause while a candidate completes a coding test |
| Final Decision Gate | Wait (webhook resume) | Hiring manager makes the call with full history in view |
| Offer Accepted Webhook → Trigger Onboarding Workflow | Webhook + HTTP Request | Direct handoff into the onboarding template, no manual handover |
28 total nodes in the downloadable file, including sticky-note documentation embedded directly on the canvas.
Key logic, in code
Handoff payload into the onboarding workflow
// Fires the same webhook shape the Employee Onboarding template expects
return [{
json: {
startDate: $json.agreedStartDate,
role: $json.roleTitle,
department: $json.department,
email: $json.personalEmail,
githubHandle: $json.githubHandle || null,
}
}];Before / after
| Metric | Before | After this workflow |
|---|---|---|
| Screening consistency | Varies by recruiter and day | Same criteria applied every time |
| Time from application to screening call | Days, manual review queue | Same day for qualifying candidates |
| Rejected candidates retained for future roles | Effectively lost | Searchable candidate pool |
| Gap between offer acceptance and onboarding start | Depends on someone remembering to notify HR ops | Automatic, same-day trigger |
Prerequisites
- n8n v1.40+ with webhook-resume Wait support
- ATS with API access (Greenhouse or Lever)
- Affinda or equivalent resume parsing API
- Anthropic API key, Cal.com or Google Calendar, CodeSignal or equivalent assessment platform
- PandaDoc, DocuSign, Airtable PAT
Common pitfalls
AI screening scores need regular bias auditing
Any automated resume screening carries legal and ethical obligations to audit for disparate impact across protected characteristics. Review scoring outcomes by demographic segment periodically, not just once at launch.
The threshold score is a floor, not a hiring decision
Screening Threshold Met? decides who gets a conversation, never who gets hired. Keep every substantive decision with a human interviewer.
Test the onboarding handoff end to end before relying on it
A field-name mismatch between this workflow's output and the onboarding template's expected input fails silently unless you validate the full chain with a test candidate first.
Want this deployed, configured and monitored?
The template is free. Wiring in your real credentials, tuning the logic to your business, and keeping it running when an upstream API changes is what we do.
Get my free automation plan →Frequently asked questions
Does AI resume screening create legal risk?
It can, if not implemented carefully. Ensure the scoring criteria are job-related and consistently applied, document the criteria, and audit outcomes for adverse impact. Consult employment counsel before deploying AI screening at scale.
Can this handle multiple open roles simultaneously?
Yes, each application carries its own role ID, and AI Score Against Requirements pulls the specific requirements for that role, so multiple pipelines run independently through the same workflow.
What if a candidate needs to skip the screening call and go straight to a panel?
Add a manual override path that a recruiter can trigger to bypass Screening Threshold Met? for referred or pre-vetted candidates, feeding directly into Role Type Router.