HR & people

HR with AI agents: process applications, collect documents, keep absences on record.

HR work is made of many small moves: read a CV, request documents, enter time off, check files. An agent does all of that by your rules, and decisions about people stay with a person: inviting, approving, hiring is confirmed by someone on the team. Here is a Monday with four such runs.

A Monday in HR

Four agent runs in one day. Each one connects the inbox, the personnel file and Slack and finishes a whole case, not just one move.

  1. 01 · Mon 07:00

    Missing documents and deadlines on Monday

    At 07:00 on Monday a run goes through all 64 personnel files: what is missing, what has expired, whose probation ends. Sara in HR sees the list in Slack and releases the follow-up emails, each person gets only their own open items. Two team leads are reminded of the probation review, and the open items sit on a page that updates itself.

    1. 1Monday 07:00, the run checks every personnel file
    2. 2Missing documents, expired certificates, deadlines
    3. 3One yes from HR, the follow-up emails go out
    4. 4Team leads get their deadlines in Slack
    5. 5The open items sit on a page, live
    SchedulePersonnel filesSlackMail to the peoplePage
  2. 02 · 08:05

    Read the application, offer an interview

    At 08:05 an application for the purchasing assistant role lands in the jobs@ inbox. The agent files the CV in the HR space, turns it into a record and checks it against the job description. Jonas in purchasing gets the short profile in Slack, answers yes with two slots, and the invitation goes out to Lena Brandt.

    1. 1The application arrives at jobs@, with a CV
    2. 2Record created, the May application linked
    3. 3Checked per criterion, without a rating
    4. 4Jonas says yes, the invitation goes out
    InboxHR spaceRecordSlackMail to the candidate
  3. 03 · 10:15

    Collect the documents for day one

    At 10:15 the signed contract for Lena Brandt lands in the HR space. The agent creates the personnel file, takes over start date and role and compares it with the document list: tax number and bank details are missing. Sara in HR says yes, the request goes out by email, IT gets laptop and accounts as a task, and after three days the agent follows up.

    1. 1The signed contract lands in the HR space
    2. 2Personnel file created, start date and role taken over
    3. 3Checked against the document list: two are missing
    4. 4One yes from HR, the request goes out
    5. 5IT gets laptop and accounts as a task
    Google DrivePersonnel fileSlackMail to the personReminder
  4. 04 · 14:00

    Check a time off request and get it approved

    At 14:00 Marek in purchasing emails hr@ asking for Oct 12 to 23 off. The agent creates the absence as a record, works out the remaining days and sees that Anna is already away in the first of the two weeks. Jonas decides in Slack, then the time off sits in the absence sheet and Marek has his confirmation.

    1. 1The request arrives by email at hr@
    2. 2Remaining days and overlaps in the team checked
    3. 3Jonas decides, the agent records it
    4. 4Confirmation sent, absence sheet up to date
    InboxRecordGoogle SheetsSlackMail to the person

Matching templates

All templates in the School

Common questions

No. Decisions about people always stay with a person. The agent puts together what the decision needs: the check against the job description, days left, overlaps in the team. Jonas says yes or no in Slack, and his answer sits on the record with name and time. Without that yes, no invitation and no confirmation goes out.

Only after a yes from the team, or in a category you define up front, for example the acknowledgement of an application. Every email is prepared as a draft first, with recipient and text. Uncertain values are flagged instead of filled in, and every run is logged step by step and can be undone.

Only people with access to the HR space. A skill gets exactly the folders and record types it needs for its task, nothing else. The data is hosted in Frankfurt and kept separate per company. Every change is logged, and the Monday run also reports applications whose retention period has passed. They are deleted after an approval.

Gmail, Microsoft 365, IMAP inboxes, Slack, Google Drive, Google Sheets and Notion are ready to use. Your HR system connects over MCP or an HTTP step, and existing lists move into records as an Excel or CSV import. One inbox is enough to start: a sick note as a PDF is all the agent needs, it reads the dates, files it in the personnel file and enters the absence.

Describe the task. The rest takes shape on the platform.

Start for free, create your first skill with the assistant, and see what a run looks like before you connect anything.

Start for free