Integration · HR and recruiting
AI agents for Rippling
Find workers and read their profile in Rippling, list departments, leave types, balances and requests, request leave, and read job requisitions, candidates and applications, with an API token.
- Actions
- 13
- Read
- 12
- Write
- 1
Actions
What your agents can do in Rippling
13 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 12
Look things up. Nothing changes.
Find workers
Lists workers (employees and contractors, current and past), optionally filtered.
Get a worker
Reads one worker by ID, with related records expanded if asked (user gives name and personal details; manager, department, teams, level, employment_type, compensation).
Get a user
Reads one Rippling user (the person behind a worker's user_id): their name, display name, emails, phone numbers, addresses and status.
List departments
Lists the company's departments.
List leave types
Lists the company's leave types.
List leave balances
Lists leave balances, optionally for one worker, with the leave type expanded.
List leave requests
Lists leave requests, optionally for one worker or of one status (PENDING, APPROVED, REJECTED, CANCELED), or matching a filter expression.
Get a leave request
Reads one leave request.
List job requisitions
Lists recruiting job requisitions.
List candidates
Lists recruiting candidates.
List candidate applications
Lists applications to job requisitions, with the job expanded.
Get the company
Lists the company (and its legal entities) the token belongs to.
Write 1
Create, change or send.
Request leave
Creates a leave request for a worker of a leave type (from "List leave types"), from a start date to an end date, optionally with partial hours on the first or last day, a reason and comments.
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 Rippling account.
What you enter
- API token
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 Rippling data
Ask a question in plain words. The agent can find workers, get a worker or get a user in Rippling, then answers with what it found.
- 02
Let an agent update Rippling
Have the agent request leave in Rippling 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 Rippling and Slack: it can find workers in Rippling and post a summary to a Slack channel in the same run.
FAQ
Rippling and MyDeepAgents
Can MyDeepAgents connect to Rippling?
Yes. The Rippling connector has 13 actions: 12 read and 1 makes changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Rippling?
Paste an API key from your Rippling account. You'll need: API token. 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 Rippling without asking?
Only if you let it. Its one action that changes data can be set to wait for a person's approval before it runs.
Can I use Rippling in workflows as well as agents?
Yes. Every Rippling action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Rippling to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.