Integration · HR and recruiting
AI agents for SAP SuccessFactors
Find users and read their profile and job information in SAP SuccessFactors, read time off, time types and time account balances, request time off, and query any OData API entity.
- Actions
- 8
- Read
- 7
- Write
- 1
Actions
What your agents can do in SAP SuccessFactors
Find users and read their profile and job information in SAP SuccessFactors, read time off, time types and time account balances, request time off, and query any OData API entity, through an OAuth client the company registers.
Read 7
Look things up. Nothing changes.
Find users
Lists SuccessFactors users (employees), by default active ones, either by exact email address or with an OData filter over User fields (like department eq 'Sales' or lastName eq 'Lovelace').
Get a user
Reads one user by user ID, with their manager.
Get a user's job information
Reads a user's current Employee Central job record (EmpJob).
List a user's time off
Lists a user's absences (EmployeeTime), optionally only those ending on or after a date and starting on or before another, newest first.
Get time account balances
Reads a user's time account balances (vacation, sick days and other accounts).
List time types
Lists the company's time types (vacation, sick leave …), for the timeType that "Request time off" takes.
Query an OData entity
Reads any SuccessFactors OData v2 entity the API user may see, with $filter, $select, $expand and $orderby.
Write 1
Create, change or send.
Request time off
Requests an absence for a user: a time type (an externalCode from "List time types"), a first and last day, and an optional comment.
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.
Enter the sign-in details SAP SuccessFactors gives you for its API.
What you enter
- API key
- User ID
- Private key
Settings
- API server
- 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 SAP SuccessFactors data
Ask a question in plain words. The agent can find users, get a user or get a user's job information in SAP SuccessFactors, then answers with what it found.
- 02
Let an agent update SAP SuccessFactors
Have the agent request time off in SAP SuccessFactors 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 SAP SuccessFactors and Slack: it can find users in SAP SuccessFactors and post a summary to a Slack channel in the same run.
FAQ
SAP SuccessFactors and MyDeepAgents
Can MyDeepAgents connect to SAP SuccessFactors?
Yes. The SAP SuccessFactors connector has 8 actions: 7 read and 1 makes changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect SAP SuccessFactors?
Enter the sign-in details SAP SuccessFactors gives you for its API. You'll need: API key, User ID and Private key. The connection also asks for: API server and 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 SAP SuccessFactors 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 SAP SuccessFactors in workflows as well as agents?
Yes. Every SAP SuccessFactors action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put SAP SuccessFactors to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.