- Home
- Resources
- Integrations
- Planday
Planday Zapier integrationAutomate Planday with Zapier.
The Planday Zapier integration gives you 4 actions, 0 triggers and 0 searches. Planday only receives data: another app starts the Zap, and Planday gets new employees, daily revenue or data-set values. It works on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the Planday Zapier integration does for you
Planday is a staff scheduling tool that weighs holidays, availability and wage costs when you build a rota. With Zapier, other tools can push data into it: a new hire, the revenue of the day, or a figure for a data set. Planday never starts a Zap itself, it only receives.
Three results justify the setup. A new hire that exists in Planday without retyping: Create Employee takes the person from your recruitment or HR tool, with first and last name, user name, salary identifier, departments and gender. Daily revenue that lands where shifts are planned: Update Daily Revenue writes a value for a revenue unit and a date, with a note, so the schedule sits next to what the day brought in. Data sets kept current: Update Data Sets - Daily and Update Data Sets - Hourly send a value with its timestamp into a data set.
The limits are just as clear. Planday has no trigger on Zapier, so nothing that happens in Planday (a shift, a swap, an absence) can start a Zap. It has no search either, so a Zap cannot look up an employee before acting. And no action edits or removes an employee once created.
The Zap therefore always starts in another app. To see how other tools handle the same job, the n8n vs Zapier page is the place to compare.
Zapier words, in plain English
Seven words are enough to follow the rest of this page.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. With Planday, it always comes from another app, such as a new row in a sheet.
- Action
- What the Zap does once started: the step that writes something for you, like creating an employee in Planday.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts only those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by its app the moment the event happens.
- Filter
- A step that lets the Zap go on only when what arrived meets your condition, and stops it there otherwise.
- Connection
- Your Planday account linked to Zapier once, then reused by every step of every Zap that writes into Planday.
What it really costs in tasks
Planday is not reserved to paid plans on Zapier: it runs from the free plan. You pay in tasks, and only the Planday actions that succeed count.
- Free plan100 tasks a month, unlimited Zaps
- Steps on the free planOne trigger and one action
- Failed actionNot counted
- Paid-only appNo, Planday works on the free plan
The trigger in the other app never costs a task, and Zapier checking it costs nothing either. Each Planday action that goes through counts once; one that fails does not. The free plan gives 100 tasks a month, unlimited Zaps, and two steps per Zap: one trigger, one Planday action. A filter or a second action makes the Zap multi-step, which needs a paid plan. Since Planday has no trigger, the speed of your Zap comes from the trigger of the other app; if it polls, the grid below applies.
Connect your Planday account in three steps
- 01
Open the Apps page
In your Zapier account, open Apps and click + Add connection. You need a Planday account first, with access to the departments, data sets and revenue units the Zap will write into.
- 02
Pick Planday
Type Planday in the dialog, select it in the results and click Add connection. A new browser tab then opens so you can sign in on the Planday side of the link.
- 03
Sign in and grant access
Sign in to your Planday portal in that tab, then allow Zapier to reach the account. From then on, every Zap that writes into Planday reuses this connection, without asking you to sign in again.
Your first Zap: daily revenue from a sheet
GoalEach revenue line added to a sheet lands in Planday, next to the schedule, without retyping it.
- 01
Build the trigger
Start a new Zap and pick the sheet app as the trigger, with the event that reports a new row. Planday has no trigger, so the Zap always starts outside it.
- 02
Test the trigger
Run the test: Zapier brings back the three most recent rows of the connected sheet. Pick a real one, the next steps are mapped on it.
- 03
Add a filter
From the plus icon, add Filter so only rows with a revenue value go on. This step makes the Zap multi-step, so it needs a paid plan.
- 04
Add Update Daily Revenue
Pick Planday and Update Daily Revenue, then map the revenue unit, the value, the date and the notes. All four are required.
- 05
Test, then publish
Test the action once and check the revenue in Planday for that date. When it looks right, publish the Zap to switch it on.
Planday actions
Planday gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Employee
ActionIn Zapier“Create an Employee in your Planday portal”
Adds a new person to your Planday portal from another tool. The step asks for first name, last name, salary identifier, user name, departments and gender, all of them required.
Update Data Sets - Daily
ActionIn Zapier“Upload daily data to a data set in Planday”
Sends one value per day into a Planday data set, with its timestamp. Any daily figure your team tracks elsewhere can sit next to the schedule this way.
Update Data Sets - Hourly
ActionIn Zapier“Upload hourly data to a data set in Planday”
The hourly twin of the previous action: it writes a value into a data set for a given hour, again with a timestamp, so peaks inside the day show up.
Update Daily Revenue
ActionIn Zapier“Update daily revenue data in Planday”
Records the revenue of a day against a revenue unit in Planday. It needs the unit, the value, the date and a note, and the note is required too.
When it breaks
Zapier links no help article to Planday, so these are the general limits that matter most for an app that only receives data.
With no Planday trigger, most surprises come from the app that starts the Zap. Four cases to check first, and the Zapier troubleshooting page helps when a run still fails.
Past rows never reach Planday
A Zap only reacts to what happens after you switch it on. Revenue or hires recorded before are ignored, and moving that history is a separate job.A bulk import gets held back
If the source app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold it back instead of sending everything.The same row is not sent twice
On a polling trigger, Zapier remembers what it has already seen, so the same row does not start the Zap twice.A failed action is not billed
When a Planday action does not go through, for instance because a required field arrived empty, no task is counted, but nothing is written either.
Need help automating Planday with Zapier?
A person reads every message.



