Contact Menu

General Information about Integrations

Firstbird integration

Integrations enable you to connect Firstbird seamlessly with your IT landscape (e.g. application tracking system, identity provider, etc.) in order to decrease the effort for Firstbird users by automating certain processes in Firstbird.

Firstbird provides its own connectors to multiple systems (e.g. ATS providers, Identity Providers, etc.) as well as a public API.

 

Definitions

 

ATS: Applicant Tracking System

API: Application Programming Interface

XML: Extensible Markup Language

JSON: JavaScript Object Notation

REST: Representational State Transfer

SOAP: Simple Object Access Protocol

(S)FTP: (Secure) File Transfer Protocol

WebDAV: Web-based Distributed Authoring and Versioning

SSO: Single-Sign-On

IdP: Identity Provider

SAML: Security Assertion Markup Language

 

 

FAQs

Why was a new job that was published in my ATS not published in Firstbird?

Please check the following:

  • Was the job sent to "Drafts"?
    If so, please check to see if some of the required fields (Location, Department, Contact Person,...) are empty. If the "Contact Person" (recruiter) field is empty, please invite the responsible recruiter to Firstbird. If the "Location" and/or "Department" field is empty, please add them under your "Account Preferences" - "Settings". It's important to make sure there are no typing errors or different spellings of the "Location", "Department" and recruiter name. Otherwise the job import will not work successfully.

  • Have you ticked the channel in your ATS that publishes jobs to Firstbird?

  • Have the mandatory fields been filled in (e.g. contact person) in your ATS?
    If not, please update the mandatory fields and wait for the next integration sync.

  • Is the contact person (recruiter) an active user in Firstbird?
    If not, please invite the contact person as a recruiter to Firstbird and wait for the next integration sync.

  • Please check if the spelling of the "Location" and/or "Department" is/are identical in Firstbird and your ATS.
    If not, please make the changes in Firstbird and wait for the next integration sync.

 

Why is an application from Firstbird not exported to my ATS?

Please check the following:

  • Was the job created manually in Firstbird?
    If so, the application can't be exported as the job is not available in your ATS. In this case a manual upload of the application is needed.

  • Has the reference number of the job the candidate applied for been changed manually?
    If so, the application can't be exported as there is no job with this reference number in your ATS. In this case a manual upload of the application is needed.

 

Why are documents or attached files of an application not or only partially exported to the ATS?

This may be caused by the size of the documents, attachments or the uploaded photo (of the applicant). At Firstbird, attachments up to approximately 10MB can be uploaded. If an ATS has a MB limit of 5MB for example, documents and attachments larger than this cannot be exported to the ATS. In this case a manual upload of the application is needed.

If this happens on a regular basis we recommend switching to our Candidate Experience Package. For further details, please get in touch with your Engagement Manager.

 

Why is a job "published" twice or is "closed" in Firstbird although it is still active in my ATS?

This happens when the reference number of the job has been changed in Firstbird after the import.

PN_Ref_Number__ENG_.jpg

The reference number assigned by the integration always includes the "Reference no. from the ATS::Location::Job title".

 

Why are manual changes to the job in Firstbird always overwritten?

This is how our integrations work. The synchronization of jobs always starts from the ATS (not from Firstbird to the ATS). Therefore, please do not make any changes of a job in Firstbird.

Always make changes in your ATS and wait for the next integration sync.