Connect Leapsome to Kula

Last updated: August 17, 2026

Connecting Leapsome lets you push a hired candidate straight into Leapsome as a new employee, with the details you already hold in Kula filling the form for you.

Who can do this: Super Admin, Admin 

Where to find it: Settings → Organization → Organization integrations → HRIS and onboarding

What the connection window looks like

Turning the toggle on does not connect Leapsome straight away. It opens a secure connection window: first the permissions Kula is asking for, then the token you need to fetch from Leapsome.

Every screen has a View Guide button in the footer, next to "Need help? Check out our detailed connection guide." Use it. It opens Leapsome's connection guide, which has screenshots of every Leapsome screen you need to click through — this article tells you what to do, the guide shows you what it looks like on Leapsome's side.

Before you connect

You need to be a Super-Admin in Leapsome. To check:

  1. Log in to Leapsome and click Your Profile.

  2. Open the Role tab.

  3. Check your primary role reads Super-Admin.

If it does not, ask your IT admin or Leapsome admin to grant it or to run the connection themselves.

Step 1 — Review the permissions

  1. Go to Settings → Organization → Organization integrations.

  2. Find the Leapsome card under HRIS and onboarding.

  3. Turn the toggle on. The connection window opens on Connect your Leapsome account to Kula.

    image.png

  4. Read the list of permissions Kula is asking for.

  5. Click Continue.

Permission

What Kula can do

Read work locations

Read your work location data

Read employees

Read your employee data

Read employments

Read your employment data

Read groups

Read your group data

Create and manage employees

Create and update employees on your behalf

Step 2 — Copy your SCIM token from Leapsome

Leapsome connects with a SCIM Authentication Token rather than a sign-in. Getting it takes a slightly awkward sequence, and the dialog closing on you partway is expected rather than a fault.

  1. In Leapsome, click Settings.

  2. Click HRIS Integrations.

  3. Click SCIM (Azure AD, Okta, …).

  4. Click Update & Synchronize.

  5. If the dialog closes by itself, click SCIM (Azure AD, Okta, …) again to reopen it.

  6. Select the whole token and copy it.

Select the full token. Leapsome may not display all of it, so selecting what you can see is not enough — the token starts with something like eyJhb and is much longer than the visible box.

Step 3 — Paste the token into Kula

  1. Return to the Kula connection window.

  2. Paste the token into SCIM Authentication Token.

  3. Click Continue.

The field is required — Kula will prompt you with "Please fill out this field." if you try to continue without it.

image.png

The field mapping screen opens automatically straight after a successful connection, so you can set your mappings while you are already there. You can reopen it at any time — see below.

Map your Kula fields to Leapsome

Field mapping decides which Kula value fills which Leapsome field, so the employee form arrives prefilled instead of blank.

  1. Hover over the connected Leapsome card.

  2. Click Edit.

  3. Match each Leapsome field to the Kula field that should fill it.

  4. Save.

These Kula fields are available to map, from your job, requisition and offer records:

Group

Fields you can map

Organisation

Department, Sub Department 1, Sub Department 2, Sub Department 3

Address

Full Address, Street, City, State, Country, Zipcode

Office

Office Name, Office Location

Dates

Hire Date — the date the candidate was last moved to the Hired stage

Push a hired candidate to Leapsome

Once the mapping is set, open the hired candidate's application and send them to Leapsome. Kula loads the Leapsome employee form, prefills every mapped field, and fetches Leapsome's own dropdown options live so the values you pick are always valid.

You can also attach documents from the application — offer letters and other files — and choose which Leapsome document category each one goes into.

For the full flow, see [Push a hired candidate to your HRIS]

Fix an invalid connection

If the card shows Invalid, the SCIM token was regenerated or revoked in Leapsome and pushes will fail.

  1. Fetch a fresh SCIM token from Leapsome, following Step 2 above.

  2. Hover over the Leapsome card in Kula.

  3. Click Re-authenticate and paste the new token.

Your existing field mappings are kept — you do not have to set them up again.

A truncated token produces the same failure as a revoked one, so if this is the first connection attempt, re-copy the token and make sure you selected all of it.

Good to know

  • Only hired candidates can be pushed. If the application is not in the Hired stage, Kula blocks the push.

  • Documents are limited to 20 MB per file. Anything larger is rejected. Files over 10 MB, and any push covering more than one document category, upload in the background — the push itself completes straight away and the documents follow.

  • Pushing the same person twice fails. If the employee already exists in Leapsome, Kula reports it rather than creating a duplicate.

  • A permissions error means Leapsome, not Kula. If the push fails with a permission error, the Leapsome credentials that authorised the connection do not have rights to create employees. Ask your Leapsome administrator to widen them and re-authenticate.

  • Where a job or requisition has more than one office, the first office is used when sending to Leapsome.

  • Leapsome asks for five permissions, not six. It does not request Read legal entities, which the other tools checked do. Nothing to act on — worth knowing if you are comparing what each integration can see.

  • The Leapsome dialog closing on you is expected. Clicking Update & Synchronize often auto-closes the SCIM dialog. Reopen it and carry on — nothing has gone wrong.

  • The SCIM token is longer than the box shows. Leapsome may not display it in full, so select the whole value rather than what is visible. A truncated token fails in exactly the same way as a wrong one.

FAQ

Where is the SCIM Authentication Token in Leapsome? I can't find it under Integrations. Go to Settings → HRIS Integrations → SCIM (Azure AD, Okta, …), then click Update & Synchronize. If the dialog closes itself, reopen SCIM (Azure AD, Okta, …) and the token will be there. Select all of it — it is longer than the box displays. For more, see Leapsome's connection guide, which screenshots every step.

Can I send a candidate to Leapsome before they are marked as hired? No. The push is only available once the application reaches the Hired stage — Kula blocks it before then to avoid creating employees for candidates who have not accepted.

We changed our field mapping — do we need to reconnect Leapsome? No. Mapping and connection are separate. Hover over the card, click Edit, change the mapping and save; the connection is untouched.

Need help? If you have questions or need assistance, reach out to us at support@kula.ai or use the in-app chat.