All templates

Automated X-Team Developer Onboarding Checklist

Every hour, WebRun opens X-Team, checks for developers newly activated on your account, builds an onboarding checklist covering kickoff, repo access, and timezone overlap hours, schedules the kickoff call on Google Calendar, and notifies the engineering team in Microsoft Teams so nothing about day one gets missed.

Runs on WebRun · Strict Lockdown policy
Every hour during business hours WebRunorchestrates each step
1 X-Team find newly activated developers
2 Google Calendar schedule the kickoff call
3 Microsoft Teams notify the engineering team
In short

How do I onboard a new X-Team developer without missing a step?

WebRun checks X-Team every hour for newly activated developers, builds an onboarding checklist covering repo access, tools, and kickoff, schedules the kickoff call on Google Calendar within a workable timezone overlap, and notifies the engineering team in Microsoft Teams. It never grants access itself, so every credential stays a deliberate step your team takes.

  • New developers get a kickoff call booked the same day they activate
  • No onboarding step gets skipped because it wasn't written down
  • Engineering teams know a new developer is starting before day one

Built for engineering managers · CTOs · People operations for engineering teams · technical program managers

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens x-team.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    X-Team - find newly activated developers
    x-team.com
    WebRun in X-Team: find newly activated developers
    WebRun opens X-Team to find newly activated developers.
    • Open X-Team and check for developers newly activated on your account
    • Note their stack, timezone, and start date
    • Build an onboarding checklist covering repo access, tools, and kickoff

    Done when Every newly activated developer has an onboarding checklist ready.

  3. 2
    Google Calendar - schedule the kickoff call
    calendar.google.com
    WebRun in Google Calendar: schedule the kickoff call
    WebRun opens Google Calendar to schedule the kickoff call.
    • Schedule a kickoff call within the overlap hours between the developer and the team
    • Add the checklist as the event description

    Done when A kickoff call is booked for every newly activated developer.

  4. 3
    Microsoft Teams - notify the engineering team
    microsoft.com
    WebRun in Microsoft Teams: notify the engineering team
    WebRun opens Microsoft Teams to notify the engineering team.
    • Notify the engineering team of the new developer and their start date
    • Share the onboarding checklist in the team channel

    Done when The engineering team has been notified with the checklist for every new developer.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
x-team.com
ScheduleRuns automatically on this cadence
Every hour during business hours
DeliveryHow each run's result reaches you
Onboarding checklist · Microsoft Teams
OutputWhat each run produces - An onboarding checklist per newly activated X-Team developer, with a kickoff call booked and the team notified.
Checklist
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Does WebRun grant repo or tool access itself?

No. It only builds the checklist and books the kickoff. Actually granting access to code or tools stays a manual step for your engineering team.

How does it pick the kickoff call time?

It looks for overlap hours between the new developer's timezone and your team's working hours, so the call lands somewhere reasonable for both.

What if two developers activate on the same day?

Each one gets their own checklist, their own kickoff call, and their own Teams notification, so nothing gets merged together.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.