Contact Menu

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 own connectors to multiple systems (e.g. ATS providers, Identity Providers, etc.) as well as a public API. 

If you have any further questions, please don´t hesitate to contact us via pm-integrations@firstbird.com. 

 

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

 

Integrations with Application Tracking Systems

General

Why do I need an integration with my ATS?
An integration between your ATS and Firstbird helps you save precious time, reduce the effort of your recruiters and keep the status of your job offers and applicants up to date. 

Which processes can be covered by an ATS integration?
Firstbird provides different integration scopes based on your requirements and the API of your application tracking systems:

  • Automatic creation and publication of jobs in Firstbird (by importing jobs from the application tracking system)
  • Automatic creation of applications in the ATS (by exporting applications from Firstbird to the application tracking system) 
  • Automatic update of applications with the Talent Scout Feedback (by exporting the Talent Scout Feedback to the application tracking system)
  • Automatic synchronization of the recruiter rating (by importing the recruiter rating from the ATS to Firstbird)
  • Automatic synchronization of the application status (by importing the application status from the ATS to Firstbird)

 

Process Light Advanced Full
Automatic creation and publication of jobs in Firstbird x x x
Automatic creation of applications in the ATS   x x
Automatic update of applications with the Talent Scout Feedback     x
Automatic synchronization of the recruiter rating     x
Automatic synchronization of the application status     x

 

ats_integration_overview_EN__1_.PNG

 

What are the technical requirements?
The technical requirements highly depend on the API of the application tracking system. Firstbird already has experience in developing integrations with REST, SOAP, (S)FTP servers and WebDAV. Our integrations support the following formats: XML, JSON and HTML.

The ATS has to fulfill the following requirements in order to enable the automation of certain processes:

Job Import (LIGHT | ADVANCED | FULL INTEGRATION)

  • Jobs can be requested from ATS (e.g. directly via REST/ SOAP API or FTP Server)
  • Jobs are available during the whole requisition period with the same ID
  • Jobs are removed respectively contain an identifier regarding the status of the job (active or inactive)
  • Updates of jobs are available (ID remains the same even if content is updated)

Candidate/ Application Export (ADVANCED | FULL INTEGRATION)

  • Candidate profiles/ Applications can be created via integration with mandatory fields of Firstbird (only first name, last name, email address)
  • All document types (pdf, doc, docs, zip) can be imported and attached to candidate profile/ application

Talent Scout Feedback Export (ADVANCED | FULL INTEGRATION)

  • After candidate/ application export ATS returns unique identifier of candidate profile/ application
  • Candidate profiles/application can be updated after the initial import to ATS
  • ATS contains a free-text field for Talent Scout Feedback (e.g. additional field or comment field)

Recruiter Rating Import (FULL INTEGRATION)

  • Recruiters are able to perform rating in ATS that could be mapped to Firstbird rating
  • Rating of a certain application can be requested by Firstbird based on identifier that has been returned after candidate/ application export to ATS

Candidate Status Sync (FULL INTEGRATION)

  • ATS can provide final status of an application (only „Hired“ and „Closed/Rejected“ status relevant) incl. 1st day of work (only relevant for „Hired“ candidates)
  • ATS is able to provide enough information about the candidate/ application to enable Firstbird to close the correct application (e.g. ATS returned unique identifier of candidate profile/ application after import (preferred solution), job ID and email address of candidate)

 

How do I provide access to the ATS?
In order to start with the implementation one of your project members or your ATS contact provides us with the access to your ATS API. 

What is a master data comparison or mapping?
In order to ensure a correct and successful data import and export, the required data must be aligned and linked to the data available in your ATS. 

How long does the development of the integration take?
The duration of the development depends on various factors such as which ATS you are using, what kind of integration should be developed, the capacity of our resources, our roadmap, etc. Firstbird provides a delivery date of the integration after the acceptance of all requirements. 

Why do I need to provide test data and test the integration?
In order to test the integration under real conditions we require some test data from you. For the testing of error management, the provided test data shall besides valid information also contain invalid data sets. The more diverse the test data the better you can test the functions around import and export before giving us the final approval and the integration goes live. 

What is the User Acceptance Test (UAT)?
After the implementation of your personalized integration, you need to test the implementation in the Firstbird test account and conduct the final user acceptance test. During that you test every possible option that could come up during everyday use and give feedback if the integration has been developed in accordance with your expectations.

 

Job Publication from your ATS in Firstbird

What is required for the job import and publication?
The job import as drafts only requires the import of the following fields:

  • Job Title
  • Job Description
  • Job ID (ID from your ATS)


The automatic publication of jobs, which triggers notifications and makes the job visible for your Talent Scouts requires all mandatory fields:

  • Job Title
  • Job Description
  • Job ID (ID from your ATS)
  • Department
  • Location
  • Contact Person
  • Reward


The branding and Hot Job fields are not mandatory.

With our help you can define how the job from your ATS will be displayed in Firstbird. In general, a job that was created in an ATS contains along with title and description also other information such as contact person, desired work experience and much more. During the requirement alignment phase we clarify the process and the data fields mapping of your ATS as well as the additionally required fields needed to publish a job in Firstbird.

 

Application Export from Firstbird to your ATS

The application export is highly dependent on the configuration of your ATS and its API. Firstbird requests only the following fields:

  • first name
  • last name
  • email
  • phone number (not mandatory)
  • link of social media profile (not mandatory)
  • files (not mandatory by default)
  • photo (not mandatory)


Firstbird is able to add additional information like the source or placeholder values, if the ATS requires additional fields.

 

Talent Scout Feedback export from Firstbird to your ATS

Depending on the possibilities of your ATS, the feedback from Firstbird will be displayed in certain fields that already exist in your ATS (e.g. in "further notes"). This information can also be displayed in your ATS if there is no particular field designated for it. Together with you and your ATS provider, we will search for the best solution without generating additional effort for you.

 

Recruiter rating import from your ATS to Firstbird

As far as your ATS provides the possibility to export recruiter ratings, they will be displayed under the ratings in Firstbird. This automated exchange of feedback and rating enriches the profile of a candidate and facilitates the communication between recruiters and talent scouts. Depending on the possibilities of your ATS, the rating of your ATS will be displayed in a particular rating field in Firstbird

 

Application status import from your ATS to Firstbird

For the synchronization of the application status between your ATS and Firstbird, a distinct application ID and the field mapping is required. The following status are available in Firstbird: in progress, closed, hired. The status "closed" and "hired" trigger pop-up windows that must be filled with new status updates. The hired status requires the 1st day of work.

 

Frequently asked questions

Why was a new job that was published in the ATS not published in Firstbird?
Check the following: have you ticked the channel "Firstbird" in your ATS? Have the mandatory fields been filled (e.g. contact person)? Is the contact person (recruiter) an active user in Firstbird?

Why is an application from Firstbird not exported to the ATS?
Check the following: has the job been created manually in Firstbird / is there no link or reference to the ATS for the published job?

Why are documents/attached files of an application not exported to the ATS?
Perhaps the file size is too big.

 

Email Integration

Standard

You can choose an email address that automatically receives applications that are created in Firstbird. This enables you to easily forward new applications to your ATS for further processes. Application documents are added as attachment to those emails.

Please note!
If you are using a customized email integration, these settings won't have any effect. If in doubt, contact support@firstbird.com.

Install the Email Integration

Go to your “Account Preferences” and next, click the button “Integrations”.

201808_Screenshot_E-Mail_Integration_CA__ENG_.jpg

Next, click the button “Install” at the email integration tile and a new window will pop up. Enter the email address at “Settings” next to “Email” where all future applications should be send.

201808_Screenshot_E-Mail_Integration_CA_1__ENG_.jpg

To activate the email integration, click the button “Save”.

201808_Screenshot_E-Mail_Integration_CA_2__ENG_.jpg

Adapt the Email Integration

Go to your “Account Preferences” and next “Integrations”.

201808_Screenshot_E-Mail_Integration_CA_3__ENG_.jpg

Next, click the button “Installed” at the email integration tile and a new window will pop up. Delete the already existing email address and enter the new email address and confirm the change by clicking the button “Save”.

201808_Screenshot_E-Mail_Integration_CA_2__ENG_.jpg


Uninstall the Email Integration

Go to your “Account Preferences” and next, click the button “Integrations”.

201808_Screenshot_E-Mail_Integration_CA_3__ENG_.jpg

Next, click the button “Installed” at the email integration tile and a new window will pop up. Move top right and click the function “Uninstall”.

201808_Screenshot_E-Mail_Integration_CA_4__ENG_.jpg

As soon as the email integration has been uninstalled, no more application documents will be forwarded.

Where to find: Click on your Name (top right) - Account Preferences - Integrations - Services

 

Custom

If the standard email integration does not cover your requirement, we are happily supporting you by developing an own integration based on your needs. Please contact support@firstbird.com if you have any questions.

A member of the integrations team will contact you to align the requirements and to discuss the technical possibilities.

 

Greenhouse

With this integration, users will be able to export job posts automatically from Greenhouse to Firstbird. It will also directly import your referrals/applications, as well as feedback information from Firstbird to Greenhouse. Even candidate updates will be synced back to Firstbird so your employees stay up-to-date on the status of their referral.


Part 1 - Configure your Firstbird and Greenhouse Account

To allow the automatic publishing of your job posts from Greenhouse to Firstbird you have to make sure that your offices, departments, recruiters and rewards have been correctly set up in Firstbird.
Without this information the job import is still possible but jobs will be imported in “Jobs”“Drafts” and will have to be published by a recruiter manually. If this is ok for you, you can skip this step and directly continue with Part 2 - Create a Harvest API Key.


Offices & Departments

Login to Greenhouse as a Site Admin and go to your "Organization" view ("Configure" - "Organization"). You should see a list of your Offices and Departments:

201704_Screenshot_Office_Departments_GH__ENG_.jpg

Now login to your Firstbird Account as a Company Administrator and go to your Company Settings ("Account Preferences" - "Settings" - "General"). Here you have the option to create "Locations" and "Departments". Locations in Firstbird are similar to "Offices" in Greenhouse.

201704_Screenshot_Location_Departments_FB_CA__ENG_.jpg

Now please continue by adding all your "Offices" and "Departments" from Greenhouse as "Locations" and "Departments" in Firstbird. When you are finished it should look like this:

201704_Screenshot_Compare_GH_FB__ENG_.jpg

 

Recruiters

In this step you have to make sure that you have invited all users that could be in the "Hiring Team" of a job in Greenhouse, to Firstbird as well. Please note that you must first invite them either as Company Administrators or as Recruiters. In Greenhouse go to your "Users" view ("Configure" - "Users"). In Firstbird go to the "User Management" ("Account Preferences" - "User Management"). Compare your users and invite any missing users to Firstbird:

201704_Screenshot_Users_Compare_GH_FB__ENG_.jpg


Important: To allow a unique match their first name and last name must be identical in both Greenhouse and Firstbird.


Rewards

In this step you will configure your rewards in Firstbird and you will add a Custom "Reward" field in Greenhouse so you can choose directly in Greenhouse which reward should be visible to your employees.
In your Firstbird Account go to the settings of "Rewards" ("Account Preferences" - "Rewards"). You will have a list of rewards that you can create/edit.

201704_Screenshot_Rewards_FB__ENG_.jpg

When you are satisfied with your customized rewards you will have to add them in Greenhouse as well.

Therefore proceed by logging in as a Site Admin to your Greenhouse Account again. Follow these steps

  1. Go to "Configure" at the menu bar, next to "Custom Options" and "Jobs".
  2. Click next to "Manage Job Fields", on the button "+Add Field".
  3. Create the Custom Field "reward".
    • Type in "Field" "reward".
    • Choose from the drop down menu at "Type", "Single select".
    • A new field will pop up. Add in "Options" all the rewards you have created in your Firstbird account previously (place each one in a new line)
    • Activate the checkbox next to "Required".
    • Save your changes by clicking "Save".

201704_Screenshot_Greenhouse_CA_4__ENG_.jpg

If you do not create this "Custom Field" and you activate the integration between Firstbird and Greenhouse, all imported Jobs in Firstbird will be automatically saved in "Jobs""Drafts".

 

Hot Job

This step is optional and is only needed if you want to be able to set jobs as "Hot Jobs" directly from Greenhouse. You can find more information on hot jobs in this article.

Login as a Site Admin to your Greenhouse Account and follow these steps:

  1. Go to "Configure" at the menu bar, next to "Custom Options" and "Jobs".
  2. Click next to "Manage Job Fields", on the button "+Add Field".
  3. Create the Custom Field "hot".
    • Type in the "Field" "hot".
    • Choose from the drop down menu at "Type", "Yes/No".
    • Activate the checkbox next to "Required".
    • Save your changes by clicking "Save".

201704_Screenshot_Greenhouse_CA_3__ENG_.jpg


Part 2 - Create a Harvest API Key

The API Key is required later on, after you have installed the integration. To create a Harvest API Key login again as a Site Admin in Greenhouse, follow these steps:

  1. Go to "Configure" at the menu bar, next to "Dev Center" and "API Credential Management".
  2. Click the button "Create new API Key".
  3. Add into "Description" Firstbird so you can remember which app is using this key.
  4. Choose from the "Type" drop down menu "Harvest".
  5. Save your changes by clicking on the button "Create".
  6. You will be directly forwarded to "Manage API Key Permissions" . Please activate "Permissions" as it’s required for the integration or just click on "Select All". Following permissions will be needed for the integration:
  • Jobs
    • GET: Retrieve Job
    • GET: List Jobs
  • Job Posts
    • GET: List Job Posts
  • Users
    • GET: List Users
  • Sources
    • GET: List Sources
  • Candidates
    • POST: Add Candidate
    • POST: Add Attachment
    • POST: Add Note
  • Applications
    • GET: List Applications
    • GET: Retrieve Application
    • PATCH: Update Application
  • Departments
    • GET: Retrieve Department
    • GET: List Departments
  • Offices
    • GET: List Offices
    • GET: Retrieve Office

 

7. Save your changes by clicking the button "Update".

201704_Screenshot_Greenhouse_CA_8__ENG_.jpg

201704_Screenshot_Greenhouse_CA_20__ENG_.jpg

 

Part 3 - Install the Integration in Firstbird

The Accounts have now been setup and the integration is ready to be installed. Login to your Firstbird Account as a Company Administrator and follow these steps:

  1. Go to "Account Preferences", choose "Integration" and then "Services".
  2. Click the button "Install" on the Greenhouse tile.
  3. Click "Connect" and you will be forwarded to the authentication process (new window will pop up).
  4. Enter your Greenhouse login email, click on the button "Next Step" and enter your Greenhouse password. Confirm by clicking on the button "Authorize".
  5. In the next step enter the "Harvest API Key" you created before
  6. If you would like to enable the integration now, activate the checkbox next to "Enable" and click the button "Save". If you would like to enable the integration later, click the button "Save" without activating the checkbox.

Important: You can not activate the integration without the "Harvest API Key".

As soon as you have clicked on the "Save" button , the integration is installed.
Please note that your jobs are synced at least every 60 minutes. So it may take a while until your jobs are visible in Firstbird.

201705_Screenshot_Greenhouse_CA__ENG_.jpg

 

Scope of Integration

This section describes the processes involved in the Greenhouse - Firstbird Integration.

 

Job Synchronization

The job synchronization takes care of the importing and updating jobs from Greenhouse to Firstbird, and is also responsible for "closing" them when they are disabled in Greenhouse.

Before a job can be synced with your Firstbird Account it has to be published on your job board:

201704_Screenshot_Greenhouse_CA_18__ENG_.jpg

 

Referral/Application Export

As soon as a new referral/application arrives through Firstbird a new candidate will be created in Greenhouse with the following Information:

  • First Name
  • Last Name 
  • Email address
  • Phone number
  • Social Profile Link (e.g. LinkedIn)
  • Attachments

 

Talent Scout Feedback

A Talent Scout can provide feedback for the referral/application to give the recruiter more information about the candidate. This information is added automatically to the Greenhouse candidate as well.

 

Candidate Status Update

It is important to keep the Talent Scouts updated. That’s why the integration also syncs back relevant status updates of the candidate (rejected/hired) from Greenhouse to Firstbird so your employees are always kept informed on their referral.

 

 

User Provisioning at Firstbird

To simplify the administration of Talent Scouts in Firstbird and the registration and login process for all user groups, Firstbird offers the option of integration with Single Sign On (SSO) and User Provisioning.

 

1. SSO Just-In-Time provisioning


The Single-Sign-On Integration gives you the option of users registering and logging in Firstbird with one click. Additional master data such as:

  • Email (Must)
  • First name
  • Last name


can be sent. If the user does not yet exist, it will be created automatically. The user must manually select his location and department as a second step in the registration process in Firstbird. Currently we support the above mentioned attributes. You can find more information here.

Advantages of this integration:

Usability

Your Talent Scouts are able to login to Firstbird much easier as they do not require any new credentials to be created and remembered, which helps to ensure that are more actively using Firstbird.

Security

Special security requirements of your company, such as password length or password validity, are taken over for Firstbird. The number of different logins in cloud services is limited, which reduces the risk of phishing attacks. Different password policies can be adopted for different user groups.

Administration

Support requests due to forgotten passwords are reduced. Users assigned to specific groups can automatically log in with Firstbird's corresponding user group rights.

 

2. User Pre-Provisioning


The Pre-Provisioning functionality enables the automated provision of user profiles. Here we synchronize (one-way) via a SFTP or HTTPS endpoint user data into our system.

It is important to note that the information must be in a format defined by us. If this is not possible, a customer-specific extension can be developed.

How does user Pre-Provisioning work?

If a user registers in Firstbird, we check if for the user are additional information available and fill them in. The following attributes can currently be pre-filled:

  • First name
  • Last name
  • Employee ID
  • Location
  • Department


All changes from the integrated system are synchronized to Firstbird at defined time intervals. If an employee is no longer present in their system, the user is automatically deactivated in Firstbird and deleted with all personal data after a time selectable by the customer.

Advantages of this integration

This integration simplifies the administration of users in Firstbird from a corporate as well as from an employee viewpoint.

For example, employees leaving the company are automatically deleted from Firstbird. In addition, changes of an employee (e.g. last name or location) are also automatically transferred to Firstbird.

 

 

Configuration of sign-on with SAML SSO

SAML-based single sign-on (SSO) allows users access to Firstbird through an identity provider (IdP) of your choice.

PLSN_SSO_1.jpg

Provisioning


Firstbird supports identity provider (IdP) initiated flow, service provider (SP) initiated flow and just-in-time provisioning.

For SP login, please go to https://YOURDOMAIN.1brd.com/login.

Your IdP should ensure that a user is authenticated and authorized befor sending a request. If a user is not authorized, the request shouldn't be sent.

 

Step 1: Setup your Identity Provider (IdP)

First, create a connection for Firstbird at your IdP. Below you will find several provider created "how to" articles for activating SAML for your Firstbird account:

Manual Identity Provider (IdP) Configuration

For an easy setup, you will find all important information for the configuration of your IdP directly in your Firstbird company account in "Account Preferences" - "Authentication" - Single Sign-on" (only visible when SSO was activated by Firstbird).

All important information at a glance:

  • Entity-ID
    https://YOURDOMAIN.auth.1brd.com/saml/sp

  • Post-Backup-URL for SSO-Login (SSO)
    https://YOURDOMAIN.auth.1brd.com/saml/callback

  • Address of Metadata.xml 
    https://YOURDOMAIN.auth.1brd.com/saml/sp/metadata
    (If automatic configuration is possible)

HC_SSO_Account_Einstellungen_ENG.jpg

 PLSN_SSO_2.jpg

 

Settings for the configuration of your Identity Provider

  • NameID (mandatory field)

<saml:Subject>

    <saml:NameID Format="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent">

Your unique identifier

   </saml:NameID>

</saml:Subject>

 

PLSN_SSO_3.jpg

 

  • Email attribute (mandatory field)

<saml:Attribute Name="email" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">

    <saml:AttributeValue

     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">your.user@yourdomain.com

    </saml:AttributeValue>

</saml:Attribute>

 

  • First name attribute (optional)

<saml:Attribute Name="first_name" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">

    <saml:AttributeValue

        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">Max

    </saml:AttributeValue>

</saml:Attribute>

 

  • Last name attribute (optional)

<saml:Attribute Name="last_name" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">

<saml:AttributeValue xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">Mustermann</saml:AttributeValue>

</saml:Attribute>

 

  • Session duration attribute (optional)

The attribute only impacts the sign-on duration. This element contains an AttributeValue element indicating how long the user can access Firstbird via mobile app before the user must sign on again. This value is an integer indicating the number of seconds for the session. The value must be at least 1,200 seconds (20 minutes). If the attribute SessionNotOnOrAfter of the AuthnStatement is also set, the lower value of the two attributes will be used. When none of these two attributes is available, the sign-on information will apply for a period of 30 days.

 

<saml:Attribute Name="https://auth.1brd.com/saml/attributes/sessionduration">

    <saml:AttributeValue

        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">86400

    </saml:AttributeValue>

</saml:Attribute>

 

Step 2: Set-up your Firstbird account (SP configuration)

Finalize the configuration in Firstbird with the following three important items from your IdP:

  1. Entity-ID 
    This is the unique identification for the connection to Firstbird and will be provided by your IdP.
  2. SSO Service URL
    This is the address of your IdP. Firstbird will send all authentication requests to this URL.
  3. Signing Certificate
    Firstbird requires that SAML assertions are signed and that a valid X.509 .pem certificate is stored at Firstbird to verify your identity.

 

All settings described above can be found in the Metadata XML of your IdP.

Firstbird offers three options to make the configuration as easy as possible:

1. Configuration via IdP Metadata.XML upload
2. Configuration via IdP Metadata URL
3. Manual configuration

 

1. Configuration via IdP Metadata.XML upload

You can upload the Metadata XML of your IdP. If the XML was uploaded successfully, the settings are preconfigured accordingly. Changes can be done at any time.

HC_SSO_Account_Einstellungen_1_ENG.jpg

 

2. Configuration via IdP Metadata URL

You can enter the Metadata XML address of your IdP. Once we have checked the XML, the settings are preconfigured accordingly. Changes can be done at any time.

HC_SSO_Account_Einstellungen_2_ENG.jpg


3. Manual configuration

If none of the above options are suitable for you, the configuration can be done manually as well.

HC_SSO_Account_Einstellungen_3_ENG.jpg

 

Click the button "Save Configuration" to save your settings.

 

Step 3: Activate SSO

As soon as you saved the SSO settings, you're able to activate SSO for your Firstbird company account.

HC_SSO_Account_Einstellungen_4_ENG.jpg

 

After activating SSO for your company account, a new button "Login via SSO" will appear on the login page. From now on, your users will be able to login only via SSO.

HC_SSO_Account_Einstellungen_6_ENG.jpg

 

 

SSO for exisiting User

You can activate SSO for your company account even if some users have already registered through your Firstbird company account. This will be done through an automatic link. The email address of the existing Firstbird user will be sent from your IdP via assertion attribute to Firstbird and must be an existing user email address in Firstbird.

If the email address is not identical, a new user account will be created.

 

 

Slack

Firstbird is an innovative recruiting tool that connects you with talent for your company, through the power of personal referrals. Integrating your Firstbird account with Slack results in a streamlined, rich, notification system that's easy-to-use. It's perfect for keeping Talent Scouts up-to-date, as they can easily connect their account and will be directly notified of new activities.

Firstbird for Slack will allow users to receive notifications directly into their Slack channel. Firstbird Company Administrators will have the ability to install Slack for their teams, and select a channel in which the public notifications will be published to. Company Talent Scouts will then have the ability to connect their Firstbird account and Slack, which will allow them to receive direct messages directly into their private Slack channel, as well as public notifications into a team channel. All users have the ability to select the specific notifications they wish to receive as well as uninstall the app.

The Slack integration option is available for all Firstbird payment plans. 

Where to find: Click on your Name (top right) - Account Preferences - Integration - Services

201705_Screenshot_Slack_CA__ENG_.jpg

 

How to install Slack for Company Administrators:

  1. Log in to your Firstbird account - Firstbird Log In
  2. Go to "Account Preferences" - "Integrations" - "Services"
  3. Click “Install” on the Slack tile
  4. Click “Add to Slack and you will be redirected to the Slack authentication flow (extra window)
  5. Select your team or click on "Sign in to another team"
  6. Click the “Authorize” button to give access to Firstbird Slack App
  7. Select your “Channel” and “Language”
  8. To activate Slack, select the check box next to "Enabled" 
  9. Confirm your settings by clicking the button “Save”
  10. Your Slack account is now connected to Firstbird

Note: You must have the required permission to add the Slack integration

Where to find: Click on your Name (top right) - Account Preferences - Integration - Services

201705_Screenshot_Slack_CA_2__ENG_.jpg

 

How to disable Slack for Company Administrators:

  1. Log in to your Firstbird account - Firstbird Log In
  2. Go to "Account Preferences" - "Integrations" - "Services"
  3. Click "Installed" on the Slack tile
  4. Remove the checkmark next to "Enabled"
  5. Confirm your settings by clicking the button “Save”
  6. You will see a toast if Slack was disabled successfully

Where to find: Click on your Name (top right) - Account Preferences - Integration - Services

201705_Screenshot_Slack_CA_3__ENG_.jpg

 

How to uninstall Slack for Company Administrators:

  1. Log in to your Firstbird account - Firstbird Log In
  2. Go to "Account Preferences" - "Integrations" - "Services"
  3. Click "Installed" / "Disabled" on the Slack tile
  4. Click "Uninstall" on top-right
  5. You will see a toast if Slack was uninstalled successfully

Where to find: Click on your Name (top right) - Account Preferences - Integration - Services

201705_Screenshot_Slack_CA_4__ENG_.jpg



API Key Management

You can easily connect Firstbird with an existing Application Management System to exchange jobs and referrals automatically.

 

Generate API Key

To generate an API Key, go to your "Account Preferences" and then to "Integration". Next, click on the button "Generate API Key" and a new API key will appear.

Read more for a detailed description of this kind of integration.

Where to find: Click on your Name (top right) - Account Preferences - Integration

201705_Screenshot_API_CA__ENG_.jpg

 

Webhooks

In addition to our open API, we have developed our webhooks to send Firstbird events to other systems, such as your Application Management System. Read more for a detailed description of this kind of integration.

Go to your "Account Preferences" and then to "Integration". Our "Webhooks" are located here. To add a new hook, click the button "Add webhook".

All events that have occurred will be saved under "Event Logs". 

Where to find: Click on your Name (top right) - Account Preferences - Integration

201705_Screenshot_Webhooks_CA__ENG_.jpg201705_Screenshot_Webhooks_Event_CA__ENG_.jpg