< Back to all integrations

SAP SuccessFactors

HR & Talent

Connect AI agents and workflows to SAP SuccessFactors: employees, jobs, org structure, time off, requisitions and candidates, with events on hires and changes.

Book a demo
[ SAP SuccessFactors + engini ]

SAP SuccessFactors for AI agents and workflows.

engini lets your AI agents and workflows work in SAP SuccessFactors: read employees, jobs and the org structure from Employee Central, update employee data, read time-off balances and request time off, manage job requisitions, candidates and applications in Recruiting, and start a workflow when someone is hired, changes jobs or leaves. Joiners, movers and leavers reach every system that needs to know. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.

MCPPython and TypeScript SDKCLIREST APIWorkflow Studio
Sign-inOAuth 2 with a SuccessFactors API client, for your company ID
ReachEmployee Central, time off, org structure, Recruiting and any OData entity your instance exposes
TriggersHires, job changes and terminations, as they happen
[ 01 / What agents can do ]

What your agent can do in SAP SuccessFactors. Every tool is one you allow or leave out.

The SAP SuccessFactors tools in engini, grouped by what they change. Read tools are safe to hand out widely. Write and delete tools go only to the agents that need them.

Read

Get Employees, Get Employee

Read people with their job, position, manager and location.

Read
Get Org Structure

Read companies, departments, divisions and cost centers.

Read
Get Time Off Balances, Get Time Off Requests

Read balances and what was requested.

Read
Get Job Requisitions, Get Candidates, Get Job Applications

Read hiring in Recruiting.

Read
Get Records

Read any OData entity your instance exposes, with a filter.

Read

Write

Upsert Employee Data

Change job, personal or compensation data through the Employee Central upsert.

Write
Create Time Off Request

Request time off for an employee.

Write
Create Job Requisition, Update Job Requisition

Open and change requisitions.

Write
Update Application Status

Move a candidate to the next status.

Write

Any endpoint

Send API Request

Call any SuccessFactors OData API, with the sign-in added for you.

Any call

Triggers

Employee Hired, Job Changed, Employee Terminated

SuccessFactors Intelligent Services sends the event as it happens.

Event
Check for Changed Employees

Employee records changed since the last check.

Scheduled

A trigger starts a workflow, and a workflow can include an AI agent step. In Code, a trigger delivers the event to your own endpoint.

[ 02 / Connect your agent ]

Connect your AI agent to SAP SuccessFactors. Four ways in, one set of permissions.

MCP

Claude, ChatGPT, Cursor

Create an MCP server in engini with your SAP SuccessFactors connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.

MCP client setup →
SDK

Python and TypeScript

Hand your agent a toolset of SAP SuccessFactors tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.

SDK guide →
CLI

For coding agents

The engini CLI connects SAP SuccessFactors and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.

CLI guide →
REST API

Any language

Every SAP SuccessFactors tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.

API reference →
MCP in four steps
In engini, connect SAP SuccessFactors and create an MCP server with that connection and the tools this agent may use.
Claude: Settings, Connectors, Add custom connector, then paste the server address.
Cursor: add the address to .cursor/mcp.json. Claude Code: claude mcp add.
Sign in through engini when the client asks. The agent sees only the tools you chose.
Cursor, connected to SAP SuccessFactors through engini
// .cursor/mcp.json: Cursor, connected to SAP SuccessFactors through engini
{
"mcpServers": {
"engini-sap-successfactors": {
"url": "<your engini MCP server address>"
}
}
}

Create the MCP server in engini with your SAP SuccessFactors connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.

Try asking your agent
“Who joined Engineering in Germany this month?”
“What is Dana's time-off balance?”
“Which requisitions have been open more than 60 days?”
“Who reports to the VP of Sales?”
“Move candidate 4412 to the interview stage.”
“Which employees change cost center on the first of the month?”

Each request runs through the SAP SuccessFactors tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.

[ 03 / What teams build ]

What teams build on SAP SuccessFactors. Agents and workflows, across systems.

IT

Joiners, movers and leavers

When SuccessFactors reports a hire, a job change or a termination, accounts are created, changed or closed in Entra ID or Okta, and ServiceNow requests open for equipment.

SAP SuccessFactorsMicrosoft Entra IDOktaServiceNow
Finance

Headcount in the ERP

Employees and cost centers flow to SAP S/4HANA, so payroll costs land where they belong.

SAP SuccessFactorsSAP S/4HANA
Recruiting

Offers out the same day

A candidate moved to offer gets the offer letter by DocuSign, and the signed letter starts onboarding.

SAP SuccessFactorsDocuSign
Employees

HR answers in Teams

An agent answers time-off balances, managers and org questions from SuccessFactors. Its toolset holds read tools only.

Microsoft TeamsSAP SuccessFactors

Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between SAP SuccessFactors and another system engini connects is available.

[ 04 / Agent Policy ]

You decide what each agent may do in SAP SuccessFactors. engini enforces it on every call.

Toolsets

Only the tools you allow

A toolset lists the SAP SuccessFactors tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.

MCP servers

Scoped when you set them up

An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.

Identity

Whose permissions apply

Connect a person's own SAP SuccessFactors account and engini acts as that person, with their SAP SuccessFactors permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.

Credentials

Kept out of prompts

Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.

Audit

Every call on record

Every call lands in History and the audit log, which you can export or stream to your SIEM.

Environments

Test before production

Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.

SOC 2 Type IIISO 27001GDPRSecurity at engini →
[ 05 / Set up ]

Connect SAP SuccessFactors in three steps. Then decide what each agent may do.

Step 01

Sign in to SAP SuccessFactors

In SuccessFactors, register an OAuth client for engini and give its API user a permission role with only the data the workflows need, then add a SuccessFactors connection with your API server, company ID and the client.

Step 02

Choose the tools

Add the connection to an MCP server or a toolset with only the tools each agent needs.

Step 03

Build or ask

Use the connection as a step in a workflow, or ask your agent to work in SAP SuccessFactors from Claude, ChatGPT, Cursor or your own code.

[ 06 / Questions ]

SAP SuccessFactors and engini. Straight answers.

Can an AI agent write to SAP SuccessFactors, or only read?

Both. engini has tools to update employee data, request time off, open and change job requisitions and move candidates. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.

Does it reach custom MDF objects?

Yes. Get Records reads any OData entity your instance exposes, custom MDF objects included, and Send API Request writes to them.

Does the agent act as me in SAP SuccessFactors?

It acts as the SuccessFactors API user behind the connection, with that user's role-based permissions. Every run is recorded under the person who started it.

Can a change in SAP SuccessFactors start work?

Yes. SuccessFactors Intelligent Services sends hires, job changes and terminations to engini as they happen, and a scheduled trigger checks for changed employee records. A workflow can include an AI agent step.

What if the tool I need is not listed?

Use Send API Request to call any SAP SuccessFactors API endpoint through the same connection, and give it only to the agents that need it.