This article outlines the main steps to Integrate SuccessFactors with Enboarder. The SuccessFactors integration utilizes the SuccessFactors webhook feature and API. The current Integration supports the ‘Hired event’, when an employee is marked as hired and is moved to the ‘hire’ stage.

Before you begin: Like anything worth doing, integrations take time. Please allow up to 4 weeks for this integration to be completed, this includes time for scoping, development and testing. You’ll also need to have a system expert and/or system administrator to assist in the completion of this integration.

Using SAP’s Intelligent Services, you are able to configure a webhook to call Enboarder’s API to receive and process the payload. The Enboarder API will validate the data, and launch a workflow in Enboarder.

Click on the hyperlinks to skip to that topic!

Here are the steps for Integration:

Enter your SuccessFactors subdomain. Only a prefix is required. For example, if your custom domain is https://enboardersandboxaccount.Successfactor.com, then enter enboardersandboxaccount only.

On the next screen, create basic authentication credentials. These will be required to configure the webhook within SuccessFactors.

Please note down the UserID, Secret, and Webhook URL before clicking on “Integrate Now”, as these will be available one time only.

There are two options on this page:

Click on the 'Copy secret' button to copy the secret if you have selected the 'Auto-create ID' option.

Make sure to note down the below 3 values:

Click on ‘Integrate now’. The tile will now show as integrated.

In SuccessFactors, we need to set up an Intelligent Services New Hire Event to push data into Enboarder. When you add a new employee, the Intelligent Services event will trigger and data will be pushed to Enboarder.

Search for and select ‘Integration Center’ in the search box at the top right of the page.

On the next page, click on My 'Integrations'.

On the next screen, click on ‘Create’ at the top right of the page to create a new Integration. Then select ‘More Integration Types’.

On the next page, select the values, as shown below, and click on ‘Create’.

On the next page, select the ‘Employee Hire’ event from the list and click ‘Select’.

On the next page, provide a name and description for this integration.

On the next tab, configure the elements required for your payload by adding them one by one.

Click on the + sign and select ‘Insert Sibling Element’.

Add a label and description.

Click on the 3-line menu button and select ‘Change Association’. Associate the elements with the column on the right.

Add elements as shown in the table below, and click ‘Next’.

Note - Please use the labels as mentioned below. All are in lowercase. You can map these elements with any business object field. You may need help from your SuccessFactors support team to do the correct association of these fields.

Note: The manager in the list above would be mapped to "Direct Manager" in Enboarder.

If required, you can send additional managers and stakeholders into Enboarder. The convention to be used for the “Immutable Field Key” value of the label should be lower case Stakeholder label defined in Enboarder with spaces converted to “_”.

For example, if there is a stakeholder in Enboarder called Report To Manager, the value in "Column Heading Override XML Alias" should be report_to_manager).

To define Mobile or Email for this manager user, the Key name convention should be the same as the manager label, however, suffixed with _mobile or _email. ( Example - report_to_manager_mobile).

On the next page, upload a JSON file (optional). You can skip this step by clicking 'Next'. This step helps in validating your JSON structure and elements which you have added in the previous steps. You can create a JSON file with a payload the way that you have designed in the previous steps, and see the view with sample data.

On the next page, add any desired filters (optional). For example (below), if you were wanting to filter employees by country CHE only, then you can add this filter.

On the final page, add detail for Enboarder’s URL and save it. Below are the values to be configured in ‘REST SERVER SETTINGS’:

You will see a summary as below:

Save the Integration, and it will now send a payload to Enboarder for future hire events.

Trouble Shooting

You can investigate mapping issues very easily. The API response is available in Enboarder. Click into Settings -> Integrations -> Integration logs to view the complete payload. There will be multiple rows. One will contain the complete response message, and the other will provide candidate information that was launched.

The new hire event is triggered once an employee is created in SuccessFactors.

On the next screen, click on the ‘Add an employee’ icon.

On the next screen, add the required information. Select event reason as 'New Hire'

Make sure to add email or phone information, as this is required to launch the new hire in Enboarder.

Once all required information is completed, click on ‘Submit’ to trigger the new hire event.

Note - You will need to complete the 'Add new employee' workflow to trigger the hire event.
​

Add Business Rule Trigger to JobInfo in Manage Business Configuration (BCUI)

Note: Without these extra steps, the integration will not be triggered by a New Hire

We've made it easy for you to integrate with one account in Enboarder (the parent account), and then be able to pass data into other child accounts. In order to enable data to flow from a parent account to a child account, you will need to configure child account IDs.

We need a mapping of your child account names and the unique ID of each child account. The child account ID can be any ID that is unique per child account and available in the source system. This ID will be used to find the child's account in Enboarder. The ID can be alphanumeric or string. It should be passed to our system as a string.

Example: If you have 3 child accounts in Enboarder and you are using the office location city as child ID, you will need to send us the below data in a CSV file:

Please add a field with the label subsidiarycompanyid in New hire event configuration and map to the business field that you have chosen. The values of this field should be the same that you have provided in the previous steps to us. E.g Sydney, Brisbane, London.

Got questions? Click on the '?' button at the top right of any Enboarder page to start a chat with us. Alternatively, email us! support@enboarder.com ✌