Connect Planday to Kula
Last updated: August 17, 2026
Connecting Planday lets you push a hired candidate straight into Planday 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 Planday straight away. It opens a secure connection window: the permissions Kula is asking for, then a hand-off to Planday's own login.
Planday asks for the least of any HRIS connection — three permissions, where most ask for five or six.
Permission | What Kula can do |
|---|---|
Read employees | Read your employee data |
Read groups | Read your group data |
Create and manage employees | Create and update employees on your behalf |
Every screen has a View Guide button in the footer, next to "Need help? Check out our detailed connection guide." Use it. It opens , which has screenshots of every Planday screen you need to click through
Before you connect
The person setting up the connection must be an Administrator in Planday. The connection will not work otherwise.
Know your Planday URL. Planday asks for it before it will show you a login form, and it is your company's own portal address in the form yourcompany.planday.com. If you do not know it, Planday's advice is to ask your manager — or check the address bar next time someone opens Planday.
Step 1 — Review the permissions
Go to Settings → Organization → Organization integrations.
Find the Planday card under HRIS and onboarding.
Turn the toggle on. The connection window opens on Connect your Planday account to Kula.
Read the three permissions.
Click Continue.
Step 2 — Sign in to Planday
Click Sign in with Planday.
Planday's own login page opens.
Enter your company's Planday URL in Portal URL — for example
adamscafe.planday.com.Click Continue to log in.
Sign in with your Planday username and password, and authorise the 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 Planday
Field mapping decides which Kula value fills which Planday field, so the employee form arrives prefilled instead of blank.
Hover over the connected Planday card.
Click Edit.
Match each Planday field to the Kula field that should fill it.
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 Planday
Once the mapping is set, open the hired candidate's application and send them to Planday. Kula loads the Planday employee form, prefills every mapped field, and fetches Planday'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 Planday 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 authorisation was revoked or expired on the Planday side and pushes will fail.
Hover over the Planday card.
Click Re-authenticate.
Sign in to Planday again and authorise the integration.
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 Planday, Kula reports it rather than creating a duplicate.
A permissions error means Planday, not Kula. If the push fails with a permission error, the Planday credentials that authorised the connection do not have rights to create employees. Ask your Planday 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 Planday.
HRIS and onboarding integrations are only available on ATS accounts.
The Planday URL is asked for on Planday's side, not Kula's. You enter it into a field labelled Portal URL on Planday's own login page, after clicking Sign in with Planday. It is your company portal address, like
yourcompany.planday.com— not your email address and not a Kula URL.The connection must be made by a Planday Administrator. A standard Planday user cannot complete it.
Planday requests only three permissions, the fewest of any HRIS connection Kula offers. It does not ask to read legal entities, work locations or employments, so those will not come across from Planday.
FAQ
Planday is asking for a Portal URL and we don't know what to put. It is your company's own Planday address, in the form yourcompany.planday.com — the same one you use to open Planday day to day. Planday's own advice on that screen is to ask your manager. Checking the address bar next time a colleague has Planday open is usually quicker. For more, see .
Can I send a candidate to Planday 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 Planday? 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 or use the in-app chat.