Revision History Initial Release Added the "Time Off" module to the samples. Added the "Position Management" module to the samples.



Type: Connection Input
The Connection Property

Type: String


Your Success Factors instance url including the odata endpoint. e.g.


Used for authentication.

Type: Password

Used for authentication.

Type: Multiline Text

Used for authentication.

Type: Multiline Text
Optional (Auto-Generated using the other connection properties)

Used for authentication.

Type: Boolean
When turned ON - Errors are not expressed as node errors, but are instead expressed inside the response payload.

Type: Boolean
When turned ON - Any empty custom properties on the node that would usually be expressed as query string paremeters are ignored.


Type: String Input

Mandatory (Auto-generated when a sample is selected)
Contains the ID of the operation chosen from a Node Sample. This property shouldn't be manually changed.


Type: String Input
A generated description of the operation based on what was available in the Swagger document.


Type: Multiline Text Input

Any custom-custom headers can be passed in to this property. Headers can be composed using the Formatter Node and should be formatted one per line with the notation header-name:header-value .


Type: Multiline Text Input
Contains the request payload (usually JSON) that provides the detail of the operation to perform. A sample value for this property is populated when a Node Sample is selected.


Type: Type: String Output
Contains the response code returned from the API Server. 200 = Success etc.


Type: Multiline Text Output
Contains the response headers as received from the API Server.


Type: Multiline Text Output
Contains the response payload (usually JSON) as received from the API. Where possible, a sample value of this property is populated when a Node Sample is selected.

Custom Inputs

This Node supports Custom Input Properties and the appropriate properties will be added to the Node when a Node Sample is selected. These Properties are resolved into parameters in the URL that is generated for the request. For example, if the operation will query a customer record, the Swagger document may specify the URL template as /customers/{customerId} . In this case, a Custom Property called customerId will be added to the Node when a "get customer" Node Sample is selected.


The Success Factors OData API node authenticates through the OAuth 2.0 process. Using a SAML assertion token and other credentials generated by and placed in the connection by the user, a temporary access token is requested. Upon succesful retrieval of an access token, the token is then used to authenticate any transactions on the API. The node can detect an expired access token and begin the journey of retrieving a new one.

Access tokens are placed back into the connection for use in other workflows using the same connection, it is not recommended that the AccessToken field is manually modified.


See Also

Success Factors OData API defintions can be found here,

Did this answer your question?