5pm Zapier integrationAutomate 5pm with Zapier.
The 5pm Zapier integration gives you 6 triggers, 5 actions and 3 searches. Every trigger is instant, so a new task or a progress entry reaches Zapier straight away, even on the free plan. Below: what each one does, what it costs, and where it breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the 5pm Zapier integration actually does
5pm is an online tool where teams plan projects, split them into tasks and log progress. Connecting it to Zapier lets something that happens in 5pm (a new task, a new user, a login) start a chain of steps in your other tools, or lets those tools write tasks, notes and projects back into 5pm without anyone copying data by hand.
Three results people build first. A kickoff note on every new task: New Task starts the Zap, Create Note drops your standard brief into the task, and the assignee never starts from a blank page. A client project opened from your sales tool: when a deal is signed elsewhere, Create Project and Create Task set up the job in 5pm with the name already typed. A timesheet that fills itself: a row in a spreadsheet goes through Find Task by Id, then Add Task Progress records the hours against the right task.
What Zapier does not do for 5pm: there is no delete operation, no trigger on a new project, and no find-or-create shortcut on any of the three searches. Nothing that existed before you switch a Zap on is picked up either, so last month's tasks stay where they are.
Weighing other tools? The n8n vs Zapier and Make vs Zapier comparisons set the criteria side by side, and the Zapier review covers the platform as a whole.
Zapier vocabulary in one minute
Seven words come back on every line of this page. Here they are in plain English, once.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you, in 5pm or in another app.
- Task
- The unit Zapier bills. One task is one action your Zap completed successfully, and your plan counts those per month.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event happens.
- Filter
- A step that lets the Zap carry on only when what arrived meets the condition you set, and quietly stops it otherwise.
- Search step
- A step that looks up something already in an app, such as an existing 5pm task, so later steps can use what it found.
What a 5pm Zap really costs
Short version: the trigger is free, every action that works is billed, and 5pm is not a premium app, so it runs on the free plan.
- Premium appNo, free plan works
- Free plan100 tasks a month, two-step Zaps
- 5pm triggers6 of 6 instant
- Trigger costNone, only actions count
A task is counted only when an action goes through; a failed one is not billed, and watching for new events costs nothing. A three-action Zap eats three times more than a one-action Zap. The free plan gives 100 tasks a month but only two-step Zaps: add a filter, a search or a second action and you need a paid plan. The interval grid below concerns polling triggers; all six 5pm triggers are instant, so it does not slow them down. Figures read for version App148439CLIAPI@1.0.1 on 2026-10-20.
Connect 5pm to Zapier in three steps
- 01
Open your connections
In your Zapier account, go to the Apps page and click + Add connection. A connection is your 5pm account linked to Zapier once, then reused by every Zap that touches 5pm.
- 02
Pick 5pm
Type 5pm in the search box of the dialog, select it, then click Add connection. A new browser tab opens on the 5pm side, ready for you to sign in with the account the Zaps will act as.
- 03
Sign in and allow access
Log in to 5pm in that tab and grant Zapier access to the account. You need a 5pm account, plus read or write rights on any project you do not own but want a Zap to touch.
Your first 5pm Zap: a kickoff note on every new task
GoalAn account manager wants each new task on a client job to open with the standard brief, without pasting it by hand.
- 01
Create the Zap
Start a new Zap and pick 5pm as the app that starts it, with New Task as the event. Choose the connection you set up earlier.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent tasks of the connected account, so you pick a real one to work with in the next steps.
- 03
Add the filter
From the plus icon, add Filter and set the field, the rule and the value so only the client project you care about goes on. This makes the Zap multi-step, which needs a paid plan.
- 04
Add the note
Add 5pm with Create Note as the action, then type your brief in Comment, the one required field. Map the task from the trigger so the note lands on the right one.
- 05
Test, then publish
Test the action once and open the task in 5pm to read the note. If it looks right, click Publish to switch the Zap on. On the free plan, drop the filter and keep the two steps.
The 6 5pm triggers
6 events start a Zap when something happens in 5pm, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.
New Progress
Instant triggerIn Zapier“Triggers when a new task progress is created.”
Someone records progress on a 5pm task, and this trigger hands that entry to your Zap so later steps can report it, total it or pass it on to the person who needs to know.
New Task
Instant triggerIn Zapier“Triggers when a new support task is created.”
The moment a task is created in 5pm, this one starts the Zap and passes the task along, which makes it the natural entry point for anything that should happen at the very start of a piece of work.
New User
Instant triggerIn Zapier“Triggers when a new support user is created.”
When a user account is added in 5pm, this trigger fires with that new person, so your Zap can welcome them, brief them or register them in the other tools of the team.
Updated Task
Instant triggerIn Zapier“Triggers when a new support task is updated.”
Any change saved on an existing 5pm task wakes this trigger up, so a Zap can react to edits instead of only to brand new work, for example to tell someone outside 5pm that a task moved.
Updated User
Instant triggerIn Zapier“Triggers when a new support user is updated.”
This trigger watches user records: when someone's 5pm user account is edited, the Zap starts with that person, which keeps any copy of the team list kept elsewhere from drifting out of date.
User Log In
Instant triggerIn Zapier“Triggers when the user logs in.”
Each time the user signs in to 5pm, this trigger fires, which turns a login into an event you can record, count or answer with a reminder in another app.
The 5 5pm actions
5pm gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Add Task Progress
ActionIn Zapier“Add Task Progress (progress in percent and house down).”
Records progress on an existing task, as a percentage, together with the hours spent on it, so the task reflects work tracked somewhere else.
Create Note
ActionIn Zapier“Creates a new note in task.”
Adds a note inside a 5pm task, with the text you write or map in Comment, its only required field.
Create Project
ActionIn Zapier“Creates a new project.”
Opens a new project in 5pm. Project Name is the one field it cannot do without, which keeps the setup short.
Create Task
ActionIn Zapier“Creates a new task in the application.”
Creates a task in 5pm from whatever your trigger brought in. Task Name is required; the rest depends on what you map.
Update Task
ActionIn Zapier“Update task in the application.”
Changes an existing 5pm task. You point it at the Task to edit, the only required field, then fill what should change.
The 3 5pm searches
3 search steps look for data that already exists in 5pm, so a later step can use it.
In the editor, searches sit at the bottom of the Action event list, under SEARCH. They fetch an existing task or user so a later step can act on it. Each one makes the Zap multi-step, so a paid plan is needed, and 5pm offers no find-or-create version of any of them.
Find Task
SearchIn Zapier“Finds a task in the application.”
Looks for a task inside a 5pm project you name, Project being the required field, and passes the match to the next step.
Find Task by Id
SearchIn Zapier“Finds a task by Id in the application.”
Fetches one precise task from its ID, which is required, so the steps after it work on exactly that task and nothing else.
Find User by Id
SearchIn Zapier“Finds a user by Id in the system.”
Retrieves a 5pm user from the User ID you give it, so a later step can address or credit the right person.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap and skips the steps that relied on it. Switch it on and the Zap carries on empty-handed.
- Create X if it doesn't exist yet?On apps that support it, this box turns a search into find-or-create. None of the three 5pm searches offers it, so a missing task has to be handled another way.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When a 5pm Zap breaks
Zapier links no help article to 5pm, so the failures below are the general ones, applied to this app.
Most broken 5pm Zaps come from four situations. None of them shows up as an error the day you publish, which is why they are worth knowing first. For a second pair of eyes, see the Zapier troubleshooting page.
The old tasks never arrive
A Zap only reacts to what happens after it is switched on. Tasks, users and progress that existed before stay out; moving that backlog is a separate job.The Zap keeps firing itself
Updated Task plus Update Task on the same task, or New Task plus Create Task: the Zap writes where its trigger watches, starts again, and eats your task count.A bulk import gets held back
Importing a batch of users or tasks at once sends a sudden wave to Zapier. Its flood protection can hold that batch back instead of running every item.The search finds nothing
Find Task by Id with a wrong ID, or Find Task in the wrong project, returns empty. By default the Zap stops there and the steps that depended on it are skipped.
Need help automating 5pm with Zapier?
A person reads every message.



