An applicant shouldn't wait a month for an answer.
Slow hiring loses good people. This demo shows an intake workflow that acknowledges every applicant, sorts them into shortlist / pool / reject, and hands the shortlist to a human panel — without a generic auto-rejection.
What triggers this workflow
Form submission or email-to-CRM pipeline creates a Person + Application record in Twenty CRM.
Source: Form / email pipeline
Workflow steps
- Twenty CRMCaptureApplication form or forwarded CV lands in Twenty CRM as a Person + Application record.
- n8nExtractRole, experience, location and consent captured from the form fields.
- n8nClassifyRule-based check against the role's required criteria — no opaque scoring.
- n8nBranchShortlist / pool / reject each get a different acknowledgement.
- Chatwoot + Twenty CRMHandoffShortlist goes to the hiring panel with the application attached.
Tools used
Human handoff
A person always makes the final call
The AI classification is a triage suggestion. Every shortlist, pool and reject email goes out only after a human reviewer signs off in Twenty CRM.
- Application matches the role's required criteria
- Application is borderline — needs human judgement
- Application is incomplete or missing consent
Try it in your browser
Edit the sample inputs, choose a branch, and see what the workflow produces. The sandbox runs offline — no accounts touched, no messages sent.
Try it in your browser
Edit the inputs, pick a branch, and see what the workflow produces. Runs entirely in your browser — no messages are sent, no accounts are touched.
1. Application received
Sam Brewer applied for Coding coach. Stated experience: 2 years tutoring, 1 year coding.
2. Triage branch
Subject: Next steps — Coding coach at Brisbane Coding Club Hi Sam Brewer, Thanks for applying. We'd love to chat — please pick a 20-minute slot here: brisco.example/i/abc. We'll send a small take-home task afterwards; nothing tricky. — Maya, Hiring
3. Internal record
- Applicant
- Sam Brewer
- Role
- Coding coach
- Experience
- 2 years tutoring, 1 year coding
- Branch
- shortlist
- Stage
- Interview
Sample data only. Numbers, names and messages are placeholders for illustration. Wire the live workflow separately using the setup notes below.
Setup for production
Wiring it for production
Live deployment needs application storage, classification rules and reviewer sign-off.
- Configure Twenty CRM with a Person + Application record and custom fields for consent.
- Document the role's required criteria in plain English — these become the n8n classification rules.
- Add a reviewer-sign-off step in Twenty CRM so acknowledgement emails only send after a person approves.
- Wire Chatwoot so the shortlist branch pings the hiring panel.
Production prerequisites
- Role criteria agreed with the hiring manager
- Consent question on the application form (Australian Privacy Principles apply)
- Reviewer sign-off step in Twenty CRM
Nothing here runs by default. Configuration has to be in place before any live send, booking or contact write.
Questions
Could this introduce bias?
Rule-based triage against documented role criteria is more transparent than a black-box score, but it's still the human reviewer's responsibility to confirm. The classification is a suggestion; the decision is always a person's.
What about Australian Privacy Principles?
Application data is collected under APP 3 (collection) with consent, used only for the role advertised, and disposed of when the role closes unless the candidate has opted into the talent pool.
More demos you can run in your browser
Want this recruitment intake & triage workflow running on your stack?
Pick the demo you're curious about or describe your own. We'll come back with what a real deployment looks like for your business — the workflow, the prerequisites, the people involved.