The Workflow Library

Library / Staffing and recruiting / recruiting-001

Candidate assignment to the right recruiter by skill and availability, with a first-contact SLA

Staffing and recruitingContactSales Hub ProfessionalIntermediate~55 min to buildFull spec

Outcome. Every new candidate lands with a recruiter who works that discipline, the immediately available ones jump the queue, and a manager hears about it when the first call has not happened inside the SLA window.

Workflow map Enrollment, branches and actions at a glance recruiting-001
flowchart TD
    A[Candidate status new or available, skills known, no owner] --> B{In redeployment pool?}
    B -->|Yes| C[Copy previous recruiter into contact owner]
    B -->|No| D{Skills}
    D -->|Engineering| E[Rotate across engineering pool]
    D -->|Finance| F[Rotate across finance pool]
    D -->|Healthcare| G[Rotate across healthcare pool]
    D -->|No match| H[Rotate across general pool, status screening]
    E --> I[Stamp candidate routed date]
    F --> I
    G --> I
    H --> I
    C --> I
    I --> J{Available within 14 days?}
    J -->|Yes| K[Call task due in 2 business hours, notify owner]
    J -->|No| L[Call task due in 1 business day]
    K --> M[Delay 4 business hours]
    L --> M
    M --> N{Contacted since routing?}
    N -->|Yes| O[SLA met = true]
    N -->|No| P[Warn owner, delay 2 business hours]
    P --> Q{Contacted since routing?}
    Q -->|Yes| O
    Q -->|No| R[SLA met = false, notify manager, create task]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when the agency is split into desks by discipline or sector and each desk has two or more recruiters.
  • UseUse it when applications arrive through a form, a job board integration or an import, so a skill value exists on the record before assignment.
  • SkipDo not use it for client side contacts. Hiring managers belong in the business development routing built from lead-routing-010, and mixing the two puts candidates into a sales sequence.
  • SkipDo not use it when skills arrive as free text from a parser. Branching on free text fails silently on every spelling variant, so map the text to the fixed option list first with the lookup pattern in data-quality-014.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.10 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.6 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.6 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the staffing and recruiting pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.