SAP SuccessFactors
HRRead core HR data from SAP SuccessFactors through the OData v2 API. Agents look up users, employment records, effective-dated job information, biographical data, and legal entities to feed provisioning, payroll, and org reporting workflows.
What This Integration Enables
In an enterprise running SAP SuccessFactors, Employee Central is the legal source of truth for who is employed, in what position, under which legal entity. The problem was never the data; it was that reaching it required OData expertise and every downstream team queued behind the integration backlog. This connector puts the core entities, User, EmpEmployment, PerPerson, EmpJob, and FOCompany, inside FlowRunner flows with paging, server-side filtering, and field trimming intact, so agents can ask the HRIS precise questions and feed the answers wherever they need to go. - Sync the active directory into provisioning, payroll, and analytics systems - Look up any employee's account or job history by userId or personIdExternal - Build headcount and org-chart reports from effective-dated job records - Enrich HR automations with biographical and legal-entity attributes - Give AI agents grounded answers to HR and org-structure questions The enterprise pattern this replaces is worth naming: the extract-transform-email pipeline, where SuccessFactors data reaches downstream teams as attachments that are wrong by the time they are read. Orchestration inverts it. The HRIS stays the single source of truth, flows carry deltas instead of dumps, and every consumer reads data with a timestamp measured in hours. FlowRunner adds the governance layer SAP-scale organizations actually require: a [human-in-the-loop](/concepts/human-in-the-loop) checkpoint on the changes with consequences, and an audit trail showing which person approved which delta before the downstream systems moved.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The nightly delta that keeps every system honest
Each night, List Users with a filter on last-modified pulls the day's changes, and List Job Information adds the effective-dated detail: who moved departments, who got a new manager, whose FTE changed. The reviewed delta lands in the provisioning queue, updates the reconciliation record in [BambooHR](/integrations/bamboohr) where a second HRIS runs in parallel, and appends to the audit sheet in [Google Sheets](/integrations/google-sheets). Downstream systems reflect yesterday's org, not last quarter's.
Headcount by legal entity, on demand instead of on request
List Companies pulls the FOCompany foundation objects with country, currency, and standard hours; List Employment Records joins active employments to each entity. The agent posts the roll-up to the HR operations channel in [Slack](/integrations/slack) weekly: headcount per legal entity, deltas since last week, new hires and exits called out. When finance asks mid-quarter, the answer is the latest post, not a three-week extract project.
An HR agent that answers from the system of record
A manager asks the internal assistant who on their team is eligible for the retention program based on tenure. The agent resolves the manager with Get User, pulls their reports' List Employment Records for original hire dates, and answers with service years computed from the actual EmpEmployment data, decoded from OData's epoch-millisecond dates. No spreadsheet archaeology, no "let me ask HRIS ops," and the answer cites the record it came from.
Human-in-Loop Highlight
List Users reporting a status flip from active to inactive is a read with teeth, because of what every downstream flow does with it: revoke accounts, cut building access, stop payroll, notify a team. In an enterprise directory sync, a false termination signal, a data-entry slip in Employee Central, an effective-dated future change read as current, or a filter written against "status eq 'f'" catching a leave of absence, gets amplified by automation into a person locked out of their job by 8am. So FlowRunner deprovisioning flows never act on the flip alone. The agent assembles the evidence: the User record, the EmpEmployment status and dates, the latest EmpJob entry with its effective date, and presents the list to the HR operations lead: "3 users flipped inactive since last sync. Two match approved terminations. One has an EmpJob record effective next month. Proceed on which?" Directory reads, reports, and enrichment run unattended all night. The signal that ends someone's access gets read twice, once by the agent, once by a person.
Agent Capabilities
6 actionsUsers
2- List Users Lists the core people directory from the User entity: names, email, manager, department, status. Supports OData paging with Page Size and Skip, field trimming with Select, and server-side $filter expressions like "status eq 't'". The backbone of directory syncs and delta detection.
- Get User Retrieves a single user account by its userId key, with optional Select trimming. The precise lookup behind manager resolution and per-employee enrichment.
Employment
1- List Employment Records Lists EmpEmployment records linking a person to a hire event, with original hire date, service dates, and employment status. Filter to one person by Person ID External or supply a custom $filter. The tenure and employment-status source.
Person
1- List Person Records Lists PerPerson biographical records keyed by personIdExternal, with date of birth, country of birth, and links to personal, national ID, and employment sub-objects. The enrichment source for workflows that need the person behind the user account.
Job Information
1- List Job Information Lists effective-dated EmpJob records holding position, department, division, location, manager, employee class, and FTE over time. Filter by User ID or Person ID External. The entity org charts, transfer detection, and headcount reporting are built on.
Foundation
1- List Companies Lists FOCompany legal-entity foundation objects keyed by externalCode, with company name, country, currency, and standard hours, effective-dated like all foundation objects. The dimension table for headcount-by-entity and compliance reporting.
Frequently Asked Questions
What can FlowRunner do with SAP SuccessFactors?
FlowRunner agents can run List Users, Get User, and List Employment Records in SAP SuccessFactors, plus 3 more actions.
Does connecting SAP SuccessFactors to FlowRunner require OAuth?
No. SAP SuccessFactors connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can SAP SuccessFactors trigger a FlowRunner workflow automatically?
SAP SuccessFactors doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SAP SuccessFactors
$100 in credits. No card required. Connect in minutes.