Fetch SAP SuccessFactors PerPerson data via SAML 2.0 bearer OAuth2 flow
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 6 nodes and runs manually, when you click “Execute workflow”. It uses only n8n's built-in nodes.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Configuration (Edit Fields (Set)): sets 9 fields: SF_API_BASE_URL, SF_IDP_URL, SF_TOKEN_URL…
- Get SAML Assertion (HTTP Request): calls an HTTP API (POST)
- Get Bearer Token (HTTP Request): calls an HTTP API (POST)
- Fetch PerPerson from SF (HTTP Request): calls an HTTP API
- Flatten Results (Code): runs custom JavaScript code
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (4)
- Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code
From the author
SAP SuccessFactors via SAML 2.0 Bearer Assertion based on OAuth 2 configuration How it works 1. Configure SuccessFactors OAuth2 SAML client within SuccessFactors 2. Get SAML assertion, exchange for bearer token for API connection 3. Fetch PerPerson data via…