This document outlines the Push elements of the SAP SuccessFactors ATS integration. Please see the table below detailing the data synced between the SAP SuccessFactors → Beamery CRM.
|
Data Type |
SFSF → BM | BM → SFSF |
|---|---|---|
| Vacancies | |
|
| Candidates | |
|
| Applications | |
|
| Attachments | |
|
Applications are the link between a Candidate and their Vacancy.
Candidate Push Mappings
| Beamery Field Reference | Beamery Field Name | SuccessFactors Field Reference | SuccessFactors Field Name | SuccessFactors Field type |
|---|---|---|---|---|
|
contact.PrimaryEmail (Mandatory) |
Primary Email |
Candidate.contactEmail |
Primary Email | Standard (Mandatory field) |
|
contact.firstName |
First Name |
Candidate.firstName |
First Name |
Standard |
|
|
ATS ID |
Candidate.candidateID |
Candidate ID | Standard |
| contact.lastName | Last Name |
Candidate.lastName |
Last Name | Standard |
| contact.phoneNumbers | Phone Number |
Candidate.cellPhone |
Phone Number |
Standard |
|
contact.location.country |
Country |
Candidate.country |
Country |
Standard |
Application Push Mappings
| Beamery Field Reference | Beamery Field Name | SuccessFactors Field Reference | SuccessFactors Field Name | SuccessFactors Field type |
|---|---|---|---|---|
|
contact.integrations.successfactors.id |
ATS ID |
Candidate.candidateID |
Candidate ID | Standard |
|
Vacancy.integrations.successfactors.id |
Job Requisition ID |
JobRequisition.jobReqId |
Req ID |
Standard |
|
|
Stage Name |
.appStatusSetItemId |
Status | Standard |
| application.currentstage.id | Application ID |
.appStatusSetItemId |
Standard |
Creation or Update of a Candidate on Push?
Whether we create a candidate on Push or update a candidate on Push will depend on whether we have an ATS ID for the contact in question.
If no ATS ID, then SuccessFactors will create a new Candidate. If there is an ATS ID, and it matches an existing ATS ID, then that contact will be updated.
If no ATS ID but there is a matching email address, then that contact will be updated.
Created Contacts
We are unable to create an ATS ID ourselves (as that is owned by the ATS itself), so when we Push a candidate to SuccessFactors, SuccessFactors will generate an ATS ID.
Pushing existing or new Candidates & their Applications
- When pushing a pre-existing Candidate in SuccessFactors, that Candidate will be added to the vacancy in SuccessFactors.
- When pushing a newly created Candidate in Beamery, that Candidate will be pushed and therefore created in SuccessFactors, alongside them being added to the vacancy.
Push Triggers
The current implementation of Candidate Push has only one way of triggering - via Recipes in Beamery CRM.
Recipes must be configured in Beamery prior to a Push mechanism working. Recipes are automated workflows that allow Beamery users to seamlessly manage candidates through the recruiting funnel. More info on Recipes can be found here.
Users can create Recipes with specific parameters to determine when to Push a Candidate or Application.
Every time those parameters are met, then the PUSH will be triggered and we will push both Candidate data and data for Applications on a Candidate. Beamery will need to understand which Vacancy stages you would like to trigger a Push to SuccessFactors to configure accordingly.
For example, you would like to Push to SuccessFactors, only when a contact has reached Interview Stage, Beamery will only trigger a push when that stage is set, and the Recipe is configured
For both Candidate Push and Application Push we suggest the following configurations:
Candidate Push
We suggest creating an “Add to SuccessFactors” Pool within the CRM. The Recipe can then be configured to run when a Contact is added to the Pool 'Add to SuccessFactors”, like below:
This would result in contacts being PUSHED to SuccessFactors when/if a contact is added to a pool.
A key thing to note: we do not PUSH updates on contacts to SuccessFactors. The Recipe has to be met for any changes to be pushed.
If any of the contacts triggered by the Recipe has Applications, we will attempt to push those applications as well, if their stages match the ones for which you asked us to configure.
Application Push
You will also need a push to trigger when stages are changing. Use a Recipe which has “Vacancy Stage” is changed in its parameters. For example: when Vacancy Stage is changed to Interview.
It is best that the stages used as a trigger here match the ones configured in the Integration. Both Recipes are needed because Recipes create candidate actions, which means Integrations are not able to determine which stage change triggered the Recipe. If a candidate has multiple Applications, this eliminates the risk of pushing updates for other stages as well.
Finally, “Add to SuccessFactors”. No filters are required.
This will push any application to SuccessFactors who’s contact’s vacancy stage is moved to Interview.
When pushing an Application, we also push the Candidate data for that Application. Therefore when pushing an Application, we will also push any updates to the Candidates First Name, Last Name, Primary Email.