Planday

Read and write Planday employees, departments and shifts; read employee groups, skills, positions, shift types, time and cost, absence requests and punch clock records.

Connect shift planning and worked hours in Planday with HR, payroll, POS and budgeting systems.

Build a flow with Planday Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

absence requests

List absence requests
Source
Vacation and absence requests with period and status.
absence_requests.list

departments

Create department
Destination
Not retried automatically
Approval before production
Creates a department.
departments.create
List departments
Source
Departments with number.
departments.list

employee groups

List employee groups
Source
Employee groups (roles people are scheduled as).
employee_groups.list

employees

Create employee
Destination
Not retried automatically
Approval before production
Creates an employee in one or more departments.
employees.create
Get employee
Source
One employee by ID.
employees.get
List employees
Source
Incremental
Active employees with departments, groups, job title and supervisor.
employees.list
Update employee
Destination
Provider duplicate protection
Approval before production
Updates an employee's details, departments and groups.
employees.update

positions

List positions
Source
Positions within departments and sections.
positions.list

punch clock records

List punch clock records
Source
Punched-in and punched-out times with the planned shift and approval.
punch_clock_records.list

shift types

List shift types
Source
Shift types with salary code and pay supplement.
shift_types.list

shifts

Create shift
Destination
Not retried automatically
Approval before production
Creates a shift in a department, assigned or open.
shifts.create
Get shift
Source
One shift by ID.
shifts.get
List shifts
Source
Incremental
Scheduled shifts with employee, department, position and status.
shifts.list
Update shift
Destination
Provider duplicate protection
Approval before production
Changes a shift's date, times, employee, position or comment.
shifts.update

skills

List skills
Source
Skills that can be required on shifts.
skills.list

time and cost

List time and cost
Source
Scheduled duration and wage cost per shift for a department (breaks excluded).
time_and_cost.list

Authentication

Planday app ID and portal refresh token

Plans and access

Planday portals with API access enabled by an administrator. The app's scopes (employee, department, shift, timeandcost, punchclockshift, absence) must be granted to the portal under Settings → Integrations → API Access.

Test environment

Planday provides test portals to integration partners on request.

Rate limits

Per portal 20 requests per second and 750 per minute; per app 100 per second and 2000 per minute; HTTP 429 with x-ratelimit-reset.

Pagination

offset and limit (max 50) with paging.total.

Provider events

Planday webhooks for employee, shift and punch clock events. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

Planday's token request takes only client_id, grant_type and refresh_token; the shared OAuth runtime also sends the client secret field, so the App ID is entered twice. That Planday ignores the extra client_secret is not verified on a live portal.
Whether Planday rotates refresh tokens is not documented; Nexra stores any new refresh token it returns.
Employee updates use PUT; whether omitted fields are kept or cleared is not documented, so map every field you want to keep.
SSNs, birth dates, bank accounts and salary identifiers are never requested or mapped.
Time and cost, absence requests and punch clock records are read only; approvals, punching in or out and payroll exports are not automated.
Deletes are not implemented. Planday has no idempotency key; uncertain creates are not repeated.

Developer reference

Create the Planday A/S (Xero) credentials described above with the narrowest permissions your flows need.
In Nexra, open Connect, then Connections, then New connection, choose Planday, enter its settings and credentials, and tick only the write actions you need. Connection guide
Test the connection, then use its actions as flow sources and destinations. Flow guide

Planday A/S (Xero) docsAPI reference Planday A/S (Xero) docsAuthentication Planday A/S (Xero) docsRate limits

Machine-readable detail: GET /api/public/connect/connectors/planday and the Connections API.