Connect Remote to Kula

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

What the connection window looks like

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

Remote asks for five permissions. It does not ask to read legal entities.

Before you connect

Your Remote account needs the Super Admin or Owner role. To check:

1. Log in to your company's Remote instance.

2. Click Admins & Permissions in the sidebar. If you cannot see that tab, your account does not have the right role.

3. Find yourself in the Company admins table and check the ROLE column.

If your role is not Super Admin or Owner, ask someone who holds one to grant it to you or to run the setup.

Step 1 — Review the permissions

1. Go to Settings → Organization → Organization integrations.

2. Find the Remote card under HRIS and onboarding.

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

4. Read the five permissions.

5. Click Continue.

Step 2 — Generate an API token in Remote

The next screen is headed API Token and carries a direct Remote API page link — use it to jump straight to the right page in Remote rather than navigating there yourself.

1. Open the Remote API page. If you would rather navigate manually, click Integrations in Remote's left sidebar, then the card titled Remote API.

2. Click Generate a new token and create a token. Give it a name you will recognise later, such as "Kula".

   

3. Press the three-dot circular button at the end of the token's row.

   

4. Click Copy Token.

   

Copy the token now. Remote shows the value once — if you lose it, generate a replacement rather than hunting for it.

Step 3 — Paste the token into Kula

1. Return to the Kula connection window.

2. Paste the token into Your API Token.

3. Click Set up integration.

   

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 Remote

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

1. Hover over the connected Remote card.

2. Click Edit.

3. Match each Remote 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:

Push a hired candidate to Remote

Once the mapping is set, open the hired candidate's application and send them to Remote. Kula loads the Remote employee form, prefills every mapped field, and fetches Remote'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 Remote 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 API token was revoked or regenerated in Remote and pushes will fail.

1. Generate a fresh API token in Remote, following Step 2 above.

2. Hover over the Remote 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.

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 Remote, Kula reports it rather than creating a duplicate.

• A permissions error means Remote, not Kula. If the push fails with a permission error, the Remote credentials that authorised the connection do not have rights to create employees. Ask your Remote 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 Remote.

• Copy the API token when Remote shows it. Remote generates it once, and you will need to generate a replacement if you lose it.

• The connection uses a token generated by one admin, not that person's login session. Removing them from Remote does not break the integration, but revoking the token does.

• Remote does not ask to read legal entities, unlike most other HRIS connections. If you rely on legal entity data downstream, it will not come across from Remote.

• The API Token screen links straight to Remote's API page, so you do not have to find it yourself.

FAQ

I can't find the Integrations page in Remote — is our account missing the feature? More likely your Remote role. Only Super Admin and Owner accounts can see Admins & Permissions and manage the Remote API. Check your role in the Company admins table and ask an owner to run the setup. The Kula connection screen also has a direct Remote API page link that skips the navigation. For more, see Remote's connection guide, which screenshots every step.

Can I send a candidate to Remote 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 Remote? 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.