List departments
Read one bounded returned FODepartment page effective as of the explicit date.
Connector library
SAP SuccessFactors connector.
Read one bounded effective-dated department reference page or find an exact department code as of an explicit date through two SAP SuccessFactors OData v2 actions using managed OAuth Bearer credentials.
Connector download
Download SAP SuccessFactors
Versioned ZIP for your CXFabric tenant.
Use this connector in a flow
- Register the ZIP in your tenant, or add a new version if the connector is already installed.
- Create or select a credential if the action requires one.
- In a Draft flow, add an available action, choose its version, connect it, and map inputs.
- Test the step and flow; review output and failures before activation.
See readme.md in the ZIP for settings and limitations.
- Version
v0.2.0.0 Choose version
- Release
- 2026-10-04
- Package
- Implemented source
- Schema credentials
- Bearer token
- Connection settings
- API Hostname
- Package size
- 9 KB
- SHA-256
13d949a6240a89bd8a514ca18b950fd48715b2c5ca0459227b74884ac9c30d2a
Version history
What's new
- v0.2.0.0Latest · 2026-10-04 · Implemented source
Two named OData v2 department reads replace the generic scaffold: a bounded reference page and exact-code lookup as of a required date using managed OAuth Bearer credentials.
- v0.1.1.0Earlier · 2026-10-02 · Starter scaffold
Historical configurable HTTP scaffold without implemented vendor actions.
Included in this version
Included actions
Implemented in v0.2.0.0. Use a separate flow trigger; no webhook trigger is included.
Find department
Find selected department metadata for an exact externalCode as of the explicit date; no match is a successful scoped result.
Vendor API
API and access
Implementation considerations
- Effective-date department page: Read one checked reference page with selected code, localized name, status and raw start/end date metadata.
- Exact department lookup: Find one API-visible exact code as of an explicit date; preserve no match and reject ambiguity.
- Caller-managed reference queries; no employee synchronization or webhook trigger is included.
- Use the assigned lowercase native API Hostname without scheme, port or path. Supported vendor forms are checked; certificate/custom gateways are unsupported. Select a managed bearer-token credential with an issued OAuth access token. Registration, issuance/renewal and SAML/OIDC exchanges remain external.
- As-of Date is required in YYYY-MM-DD form. It is sent as the native asOfDate parameter; company/datacenter effective-date and timezone semantics apply. Exact externalCode strings retain leading zeroes and case within the documented local character subset.
- Page Limit/Row Offset check one bounded page without truncation. Continuation is reported as presence only; links are not followed or echoed and absence does not prove complete coverage. Caller owns pacing, consistency, iteration and completeness.
- Find with zero API-visible rows returns found: false, which does not establish that the department never existed. Multiple rows, mismatched codes or continuation fail. Nullable/empty/future text is preserved; native OData date strings are retained without calendar conversion or interpreting readiness.
- No employee/person/payroll data, contact/manager/cost-center expansion, write, arbitrary entity/filter, historical range or token job is included. Hosted import, executor dependencies and live company/server/OAuth/IP/MDF Department permissions/field/paging require validation.
- Two packaged OData v2 department reads use an explicit as-of date and managed OAuth Bearer credentials. Current public examples establish selected fields; target company permissions, metadata and effective-date behavior require validation.
Related connectors
More in Enterprise, ERP & HR APIs
Support
Need help with SAP SuccessFactors?
Tell us what you need to connect or change.