How we handle GDPR data-subject requests on a deadline
Legal
A new-hire record triggers an agent to provision accounts, add the person to the right groups and channels, and file a first-week checklist, with account creation and group membership held for approval.



Onboarding a new hire spans several systems on day one. There's a Google Workspace account to create, groups and aliases to add them to, Slack channels to invite them into, and a first-week checklist someone has to remember to file. Each step is small, but they live in different tools, and the person doing the setup is rarely the person who owns every system. Steps get missed, and a new hire waits on access they should have had on their first morning.
We handle this by tying the setup to the event that starts it: a new record in our HR system. This writes up how we run that on Kortix — the connections, the steps, and the guardrails — so you can set up the same flow for your own team.
The common approaches each leave gaps. A written runbook depends on a person following every step by hand, and the steps drift as the tools change. A no-code automation handles the happy path it was built for but can't reason about which groups a given role needs. And handing each system to a different owner means the new hire's access lands piecemeal over their first few days.
We wanted the accounts, memberships, and checklist a new hire needs to be prepared the moment their record exists, with the irreversible steps held for a person to confirm.
On Kortix, a new-hire record triggers an agent. Each new hire runs in its own isolated session — a cloud sandbox — with scoped access to what onboarding needs: Google Workspace, Slack, and Linear. The agent reads the role, prepares the account, the group and channel memberships, and a first-week onboarding checklist, and files them. Account creation and group membership stop at an approval gate before anything is provisioned.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the onboarding checklist skill and the hourly trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up an employee onboarding agent in this workspace.
Create the agent agents/employee-onboarding.md. Its job is to prepare the accounts, channels and first-week checklist for each new hire. It may use the Google Workspace, Linear and Slack connectors.
Create the skill skills/onboarding-checklist/SKILL.md with these rules:
Add a cron trigger onboarding-check to kortix.yaml. It runs the employee-onboarding agent every hour, on the hour, with the prompt "Load the onboarding-checklist skill and onboard every new hire in the Pending Onboarding group."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect Google Workspace, your task tracker and Slack. Credentials are brokered server-side and never enter the agent's machine.
Finds new hires and prepares accounts, aliases and groups.
Files the new hire's first-week checklist.
Marks the new hire who is ready to onboard.
Adds the hire to team channels and posts the prepared setup.
Merge the change request, then start a session with the employee-onboarding agent and send this prompt. Check the planned account and the checklist before you let the schedule take over.
Run the onboarding check once.
The change request added this trigger to kortix.yaml. From now on the agent
runs every hour, on the hour, each run in a new session on its own cloud
computer.
To change the time, edit the cron line, or open Triggers in the workspace.
triggers:- slug: onboarding-check name: New-hire onboarding check on: cron: "0 0 * * * *" run: agent: employee-onboarding prompt: Load the onboarding-checklist skill and onboard every new hire in the Pending Onboarding group.Slack invites and the Linear checklist run on their own, because they grant no system access. Creating the Workspace account and adding groups stop for a person. An automated session waits at most 30 minutes for a person, then stops without creating the account, and the next run asks again.
Each new hire ends as one report in #it-ops. This is what a run looks like in the session:
Found 2 new hires. Added each one to 4 team channels and filed 6 first-week issues in Linear. Both Workspace accounts are waiting for approval, each with a planned mailbox and 3 groups.
Once it works, paste any of these into the same session.
On each hire's start date, send them a Slack DM with the link to their first-week checklist and the name of their manager.
When a role needs a laptop, file a hardware request in the Onboarding project with the start date as the due date.
Seven days after the start date, ask the manager in Slack which first-week items are still open, and update the Linear checklist.
Giving an agent the ability to create accounts and grant access is a trust question. The relevant controls on Kortix:
The scramble to set up a new hire across several tools now arrives as one prepared, reviewable setup the moment their record exists, with the access-granting steps held for a person. Extending it to another system means connecting one more platform.