Integration · HR and recruiting
AI agents for 7shifts
Read and build 7shifts schedules: list shifts, add or change a shift, list, request, approve or decline time off, read time punches, and list employees, locations and roles, with a 7shifts access token.
- Actions
- 10
- Read
- 5
- Write
- 5
Actions
What your agents can do in 7shifts
10 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 5
Look things up. Nothing changes.
List shifts
Lists shifts that start in a time window (UTC, ISO 8601), optionally for one location, department, role or user, only open shifts, or with draft (unpublished) shifts too.
List time off
Lists time-off requests, optionally for one location or user, of one status or category (paid, unpaid, paid_sick), or ending on or after a date.
List time punches
Lists clock-ins (time punches) whose clock-in falls in a window (UTC), optionally for one location, user or role, or only approved ones.
List employees
Lists the company's employees, optionally by (partial) name, status (active or inactive) or location.
List locations
Lists the company's locations, each with id, name, formatted_address, city, state, country and timezone.
Write 5
Create, change or send.
Add a shift
Adds a shift at a location from a start to an end time.
Change a shift
Changes a shift: its start and end (UTC), user, location, role, department, notes, draft state or status (0 none, 1 sick, 2 no show, 3 late, 4 call out, 5 left late).
Request time off
Creates a pending time-off request for a user from one date to another (whole days, or part of a day with partial_from and partial_to times like 09:00), of a category.
Approve time off
Approves a pending time-off request, optionally with a message to the employee.
Decline time off
Declines a pending time-off request, optionally with a message to the employee.
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.
Paste an API key from your 7shifts account.
What you enter
- Access token
Settings
- Company ID
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.
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 7shifts data
Ask a question in plain words. The agent can list shifts, list time off or list time punches in 7shifts, then answers with what it found.
- 02
Let an agent update 7shifts
Have the agent add a shift or change a shift in 7shifts 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 7shifts and Slack: it can list shifts in 7shifts and post a summary to a Slack channel in the same run.
FAQ
7shifts and MyDeepAgents
Can MyDeepAgents connect to 7shifts?
Yes. The 7shifts connector has 10 actions: 5 read and 5 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect 7shifts?
Paste an API key from your 7shifts account. You'll need: Access token. The connection also asks for: Company ID. 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 7shifts without asking?
Only if you let it. Each of the 5 actions that change data can be set to wait for a person's approval before it runs.
Can I use 7shifts in workflows as well as agents?
Yes. Every 7shifts action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put 7shifts to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.