HR & RECRUITING

Agent-Driven Onboarding Coordinator on Offer Accepted

When an offer is accepted, an onboarding agent assembles the full pre-start plan — accounts, equipment, training, and intros — adapting tasks to the hire's role and department.

CategoryHR & Recruiting
Enginepaperclip
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerOffer marked accepted in ATSHTTP webhook
  • ActionRead onboarding playbooksNotionNotion
  • LogicAgent drafts role-adapted task plan
  • ActionWrite onboarding plan pageNotionNotion
  • OutputPost plan to HR for approvalSlack

What it does

Uses an onboarding agent to reason through everything a specific new hire needs before day one — provisioning, equipment, role-specific training, and key introductions — and produces a tailored, ordered plan rather than a fixed checklist.

When to use it

Use it when roles and departments vary enough that a one-size template breaks down, and you want the system to adapt the onboarding plan to each hire while keeping a human approval gate.

How it works

  1. 1A webhook trigger fires when an offer is marked accepted in your ATS, passing role, department, location, and start date.
  2. 2The agent reads internal onboarding playbooks from Notion to ground its plan in current policy.
  3. 3A logic step has the agent draft a role-adapted task plan with owners and due dates relative to the start date.
  4. 4A Notion action writes the structured onboarding plan as a new project page.
  5. 5A Slack output posts the plan summary to HR with an approval request before any tasks are dispatched.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.