HR & RECRUITING

Route new hires to engineering or sales onboarding plans by department

Reads a new-hire record, branches on department, and builds the matching 30-60-90 plan — Linear project for engineers, Asana project for sales.

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew hire added to HRIS sheetAirtableAirtable
  • LogicBranch on department (eng vs sales)
  • ActionExpand role template into dated tasksOpenAI
  • ActionCreate Linear project for engineering hiresLinearLinear
  • OutputCreate Asana project for sales hiresAsanaAsana

What it does

Applies the right onboarding playbook per function instead of one generic plan. It inspects the new hire's department and routes accordingly: engineers get a 30-60-90 project in Linear (environment setup, first PR, on-call shadowing), sales hires get one in Asana (product certification, pitch reps, pipeline targets). Each plan is dated against the start date.

When to use it

Use it when onboarding genuinely differs by department and you want a single intake that fans out to the correct tool and template. Best for cross-functional teams where engineering lives in Linear and go-to-market lives in Asana.

How it works

  1. 1A new hire added to the HRIS sheet (Airtable) triggers the flow.
  2. 2A logic branch reads the department field and selects the engineering or sales path.
  3. 3An LLM expands the department-specific template into dated 30/60/90 tasks.
  4. 4Engineering hires get a Linear project with milestone cycles; sales hires get an Asana project with phase sections.
  5. 5The created plan link is the final output, written for the manager to review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect LinearIssues, projects, cycles, triage.
  4. 4
    Connect AsanaTasks, projects, milestones — everywhere.
  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.