Skip to content

Start building

Integration · HR and recruiting

AI agents for Deputy

Read and build schedules in Deputy: find shifts, add or change a shift, list employees, locations' areas and leave rules, find and add leave requests, and read timesheets, with a Deputy permanent token.

Actions
8
Read
6
Write
2

Actions

What your agents can do in Deputy

8 actions. Each one is a tool your agents can call and a step your workflows can run.

Read 6

Look things up. Nothing changes.

  • Find shifts

    Finds rostered shifts that start in a time window, optionally for one employee or one area (operational unit), oldest first.

  • List employees

    Lists employees, by default only active ones, optionally whose display name contains a text.

  • List areas

    Lists areas (operational units: Kitchen, Front of House …) that shifts are rostered in.

  • List leave rules

    Lists the leave types (rules) the install uses, like Annual Leave or Sick Leave, each with Id (what "Request leave" takes), Name, PaidLeave and UnitType.

  • Find leave requests

    Finds leave requests that start in a date window, optionally for one employee or of one status (0 awaiting approval, 1 approved, 2 declined, 3 cancelled).

  • Find timesheets

    Finds timesheets (the times actually worked) that start in a time window, optionally for one employee or only approved ones.

Write 2

Create, change or send.

  • Add or change a shift

    Adds a shift, or changes one when shift_id is given: start and end time, the area (operational unit) it is for, the employee working it (or open for anyone to claim), a meal break and a comment.

  • Request leave

    Adds a leave request for an employee, awaiting a manager's approval.

A person can approve first

Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.

Connection

How it connects

Connect it once in the console, then give it to the agents and workflows that need it.

API key

Paste an API key from your Deputy account.

What you enter

  • Permanent token

Settings

  • Deputy address

Kept safe

  • Credentials are stored encrypted with your organization's own keys.
  • They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
  • Calls go only to the tool's own servers.

How we protect your data

Ideas

Ideas to start with

Starting points made only from the actions above. Mix them with any other tool your agents can use.

  • 01

    Ask about your Deputy data

    Ask a question in plain words. The agent can find shifts, list employees or list areas in Deputy, then answers with what it found.

  • 02

    Let an agent update Deputy

    Have the agent add or change a shift or request leave in Deputy as part of a larger task. Turn on approval and a person signs off on each change first.

  • 03

    Share what it finds in Slack

    Give one agent Deputy and Slack: it can find shifts in Deputy and post a summary to a Slack channel in the same run.

FAQ

Deputy and MyDeepAgents

Can MyDeepAgents connect to Deputy?

Yes. The Deputy connector has 8 actions: 6 read and 2 make changes. Your agents can call them as tools, and your workflows can run them as steps.

How do I connect Deputy?

Paste an API key from your Deputy account. You'll need: Permanent token. The connection also asks for: Deputy address. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.

Can an agent change data in Deputy without asking?

Only if you let it. Each of the 2 actions that change data can be set to wait for a person's approval before it runs.

Can I use Deputy in workflows as well as agents?

Yes. Every Deputy action also works as a step in a workflow, and the same connection serves your agents and your workflows.

Early access

Put Deputy to work

Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.