Free for 30 days on Scale.Start free
Run5 steps45 min setup, ongoing ~2 min per new hire row

Automated employee onboarding sequence

An onboarding workspace where every new hire moves through Day 1 + Day 7 + Day 30 + Day 90 touchpoints automatically, managers get personalized check-in prompts in Slack at the right moments, and HR has a full audit trail.

Open in DockSee every step →

An onboarding workspace where every new hire moves through Day 1 + Day 7 + Day 30 + Day 90 touchpoints automatically

An onboarding workspace where every new hire moves through Day 1 + Day 7 + Day 30 + Day 90 touchpoints automatically, managers get personalized check-in prompts in Slack at the right moments, and HR has a full audit trail.

Spin up an agent for the heavy lifting

Reads New hires every morning at 8 AM, fires Day 1 kickoff for hires whose start date matches today (welcome email + manager Slack checklist), fires Day 7 / Day 30 / Day 90 manager pings within the configured window. Never modifies past hires' touchpoint flags after they're set.

5 steps, 0 official links, 2 agent prompts

Every external doc the agent needs to cite is pre-loaded into the workspace's Pointers table. No hunting for the right URL mid-draft.

What's inside

Pre-loaded so day one is execution.

4Surfaces
5Steps
2Agent prompts
5Tools mapped
Surfaces
  • tableNew hires
  • docSetup guide
  • docOnboarding log
  • docStatus
See every step, link, and prompt
How the loop works

Your agent works. Dock shows you what happened.

Open this template and you get a workspace seeded with an agent prompt. Connect your agent — Claude via our MCP, Cursor, your own setup — and it reads, drafts, and posts updates as it goes. You watch Dock for the latest.

  1. 01

    Connect your agent

    Claim an agent invite at trydock.ai/agent-invites — your agent gets an API key scoped to this workspace. Paste the key into Claude Desktop, Cursor, or any MCP client.

  2. 02

    Your agent reads the workspace

    The agent prompt at the top of the workspace tells your agent its role, the cadence to follow, and the surfaces to update. No extra setup — open Dock and your agent already knows what to do.

  3. 03

    Watch Dock for the latest

    Your agent posts to the Status surface after every meaningful action — newest at top. Wire the workspace's webhooks to Slack or email to get pinged in real time.

Wire it up · Claude Desktop

Add Dock as an MCP server in 30 seconds.

{
  "mcpServers": {
    "dock": {
      "command": "npx",
      "args": ["-y", "@trydock/mcp"],
      "env": {
        "DOCK_API_KEY": "<paste from /agent-invites>"
      }
    }
  }
}

Drop into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on Windows / Linux. Restart Claude Desktop. Ask Claude:“Read trydock.ai/<org>/automated-employee-onboarding-sequence and follow the agent prompt.”

Full MCP setup guideOther agent clients (Cursor, custom MCP)
FAQ

Common questions on this template.

What if I forget to add a hire row until after their start date?
MAX_KICKOFF_LATE_DAYS (default 3) catches you for the first 3 days. Add the row, the next daily run sends the welcome email + manager checklist. After Day 3, the welcome email is skipped (a 2-week-late welcome confuses someone already settled) and Sequence Started is set to 'Skipped late'. The manager checklist is still useful in that case; you can send it manually from the row's Notes column.
Can I customize the welcome email content per department?
Yes via prompt edits in run_onboarding.py. The base script uses one prompt with COMPANY_CONTEXT for tone. To branch by department, extract Department in kickoff_employee() and switch the prompt template. The Extending section in Setup guide shows a department-keyed prompt dict pattern.
What if a hire goes on leave or pauses onboarding?
Set Status to Paused (or any non-Active value). The hire is excluded from future runs. When they return, set Status back to Active. Note that windows still apply: if Day 30 milestone window passed while paused, that milestone is permanently skipped (you can send manually).
Can I add a Day 14 or Day 60 milestone?
Yes. Append the day count to the MILESTONES list (e.g. [7, 14, 30, 60, 90]). The loop handles them automatically. Also add the corresponding 'Day N Sent' column to the New hires table, otherwise Dock may auto-create it untyped with unpredictable column ordering.
What if the manager doesn't use Slack?
Two paths. Either fall back to email (the Extending section in Setup guide shows the Manager Email + send_email() pattern), or just put a generic ops channel as the Manager Slack ID and let the office manager forward via DM. Most ops teams default to the latter for the first quarter, then upgrade to per-manager mentions once Slack adoption is real.
Related templates

More from Run

RunMixed
Launch on Product Hunt the right way

12-step plan from picking the launch date to shipping the post-mortem. Your agents draft the assets + run the 24-hour hunt log + flag every converting comment in real time.

RunMixed
Launch on Hacker News (Show HN guide)

10-step plan for landing on the HN front page with a Show HN. Real title rules, real comment-thread tactics, real survival guide.

RunMixed
Automate Instagram posting with your agents

10-step plan for a posting pipeline that drafts, queues, and ships 6-12 Instagram posts a week with agents drafting and a human approving.

Browse all Run templates →

Open it. Hand it to your agent. Ship.

One click mints a fresh workspace in your org with the template body seeded. Your agents, your team, your edits from there.

Open in DockBrowse all templates →

About this template

Curated by the Dock team at . Every template is a real shared workspace we run with our own agents before publishing.

Reviewed regularly by the Dock team. Each playbook step links to the upstream tool's official docs so we can re-verify the rules as platforms change.