Skip to main content

Partner: Skello (HR-System)

Connect Teamtailor with your Skello account

Jonathan avatar
Written by Jonathan
Updated this week

Getting started

To enable the integration, you first have to connect your existing Skello account through our Marketplace page. Once the integration is activated, you will be redirected to the configuration settings.

In the configuration settings you will need to add your "Access token" and "Organization ID":


Set up the workflow on Teamtailor

You can set up the Skello trigger and send candidate data automatically to the Skello platform when they are hired.

Start by going to the job where you would like to add the Skello trigger. Click on the Triggers wand at the top right-hand corner and + Add trigger in the Hired stage. Choose Send Skello webhook to set it up.

Make sure that you configure the mandatory settings for the trigger before finalizing the setup, see example below:

Under "Additional options" you can choose to delay the trigger, as well set up conditions for what candidates the trigger shouldn't be activated on:

Once the trigger is set up, you're ready to go. Happy recruiting!


Custom fields

These are the Teamtailor custom fields or standard fields the integration supports:

Candidate fields

  • first-name (required)

  • last-name (required)

  • email

  • phone

Candidate custom fields

  • birth-name

  • pay-identification-number

  • birth-date

  • birth-city

  • birth-state

  • birth-country

  • nationality

  • identity-document-type

  • identity-number

  • expiration-date-document

  • gender

  • street

  • zip-code (alt: postal-code, zipcode)

  • city (alt: candidate location name)

  • address-details (alt: address or candidate location address)

  • country-code (alt: country)

  • payment-method

  • swift-code

  • social-security-number

  • routing-number

  • number-of-dependents

  • comments (alt: job offer message/response)

Job/offer fields

  • start_date (alt: onboarding start date)

Webhook/config fields

  • primaryShop (required)

  • licenseScope (required)

  • licenses (required)

  • networkLicenses (required when scope = network)

  • teamId

  • positionId

  • unitOfTimeType (required)

  • contractHours

  • numberOfDays

  • contractTypeId

  • hrToolSource

  • sendInvitation

Did this answer your question?