- Home
- Resources
- Integrations
- Everhour
Everhour Zapier integrationAutomate Everhour with Zapier.
The Everhour Zapier integration gives you 7 triggers, 7 actions and 5 searches. Six triggers are instant, so a new project or a stopped timer starts your Zap right away; only the tag trigger waits for Zapier's scheduled check.
Verified Trustpilot reviews · AI, automation & growth agency
What the Everhour Zapier integration does for your team
The Everhour Zapier integration plugs your time tracker into Zapier, the tool that runs automations between apps. Everhour tells Zapier when a client, project or task appears, when a timer starts or stops, and when time is logged. Zapier can write back: clients, projects, sections, tasks, timers and time entries.
Three results justify the setup in an agency or a studio.
Projects that arrive structured. New Project fires, Create Section lays out the phases you always use, and Create Task drops in the kickoff. Nobody rebuilds the same skeleton by hand.
Time logged from somewhere else. Add Time writes hours on a task from a value like 2h 15m, and Start Timer or Stop Timer drive the clock from another tool.
Hours that leave Everhour the moment they change. Task Time Updated fires when time on a task is added, edited or removed, so a billing sheet or a client report stays in step.
What Zapier does not do here: there is no action to edit or delete an existing task, project or client, and no trigger for an updated project or client. Tags can be watched, never created. And Stop Timer stops the current timer, it does not let you pick another one.
The same app has a page on Make too: the Everhour Make integration.
Zapier vocabulary, in plain words
Eight terms, explained once. The rest of the page reuses them as they are.
- 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 that starts the Zap. Once the Zap is on, Zapier waits for it: a new task, a timer stopping, time logged.
- Action
- What the Zap does once it has started: the step that writes something for you, such as a section, a task or a time entry.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Not to be confused with an Everhour task.
- Instant trigger
- A trigger the app reports itself: Everhour calls Zapier as soon as the event happens, so nothing waits for a scheduled check.
- Polling trigger
- A trigger Zapier checks on a timer, asking the app for new items at a fixed interval and keeping only what it has not seen.
- Filter
- A step that lets the Zap continue only when what arrived meets the condition you set, and stops it there otherwise.
- Search step
- A step that looks up something already in Everhour, like a member or a project, so the next steps can use it.
What an Everhour Zap actually costs
Zapier bills completed actions. The trigger never costs a task, and Zapier checking for new tags costs nothing either, however often it looks.
- TriggerNever costs a task
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps only
- Premium appNo, Everhour works on the free plan
Each successful action counts on its own: the first Zap below, with two sections and a task, uses three tasks per project. A failed action is not counted. Everhour is not a premium app, so it runs on the free plan: 100 tasks a month, unlimited Zaps. The limit people miss is shape, not volume: free Zaps stop at two steps, one trigger and one action. A filter, a search or a second action makes it multi-step, and that needs a paid plan. The interval grid below only touches List Tags, the one polling trigger; the six others are instant on every plan.
Connect Everhour to Zapier
- 01
Start from the Apps page
In Zapier, open Apps and click + Add connection. A connection is your Everhour account linked to Zapier once, then reused by every step that touches Everhour.
- 02
Find Everhour
Search for Everhour by name in the dialog, select it, and click Add connection. You need an Everhour account already in place for this to lead anywhere.
- 03
Sign in and allow access
Everhour opens in a new tab. Sign in with the account whose projects the Zap should work on, then grant Zapier access. For projects you do not own, you also need read or write rights on them.
Your first Zap: a new project with its phases ready
GoalWhen a project is created in Everhour, add a Discovery and a Delivery section, plus a kickoff task.
- 01
Build: pick the trigger
Create a Zap, choose Everhour and the event New Project, then pick your connection. The trigger is instant, so there is no interval to worry about.
- 02
Test it on a real project
Run the test. Zapier brings back the three most recent projects of the account, so you map the next steps on a real one.
- 03
Add the two sections
Add Create Section twice. In each, map Project from the trigger and type the Section Name: Discovery in the first one, Delivery in the second.
- 04
Add the kickoff task
Add Create Task, map the same Project, and type a Task Name such as Kickoff call. With three actions, this Zap is multi-step and needs a paid plan.
- 05
Test, then publish
Test each step and check the project in Everhour. Then click Publish. From now on, each new project gets the same structure; existing ones are left as they are.
Everhour triggers on Zapier
7 events start a Zap when something happens in Everhour, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.
New Client
Instant triggerIn Zapier“Triggers when a new client is created.”
Fires when a client record is added in Everhour. It is the earliest signal that new work is coming, before any project exists.
New Project
Instant triggerIn Zapier“Triggers when a new project created.”
Reacts the moment a project is created. Use it to give every project the same starting structure, or to announce it elsewhere.
List Tags
Polling triggerIn Zapier“Lists all tags.”
The odd one out. It lists the tags of the account, and Zapier keeps only the ones it has not seen before, so a new tag starts the Zap once.
New Task
Instant triggerIn Zapier“Triggers when a new task created.”
Starts the Zap whenever a task is created in Everhour. It is the hook for anything that should follow a fresh piece of work.
Task Time Updated
Instant triggerIn Zapier“Triggers when time that belongs to a task is added, edited or removed.”
Catches any change to the time on a task: added, edited or removed. Despite the name, a deletion fires it too.
Timer Started
Instant triggerIn Zapier“Triggers when a timer is started. Timer should be with a task.”
Fires when someone hits start on a timer. Only timers attached to a task count, so a timer running without a task is ignored.
Timer Stopped
Instant triggerIn Zapier“Triggers when a running timer is stopped. Timer should be with a task.”
The mirror of the previous one: it reacts when a running timer is stopped, again only for timers attached to a task.
Everhour actions on Zapier
Everhour gives you 7 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Client
ActionIn Zapier“Creates a new client.”
Adds a client to Everhour. Only the Name is required, which makes it easy to feed from a CRM or a signed proposal.
Create Project
ActionIn Zapier“Creates a new project.”
Opens a new Everhour project. Project Name and Project Type are required: List shows sections stacked vertically with their tasks, Board shows them as columns.
Create Section
ActionIn Zapier“Сreates section (column) in a project.”
Adds a section, which is a column on a Board project, inside a project you name. Project and Section Name are required.
Stop Timer
ActionIn Zapier“Stops the current timer.”
Stops the timer currently running. No field to fill is listed for it: it acts on whichever timer is running, not on one you pick.
Create Task
ActionIn Zapier“Creates a new task.”
Creates a task in a project. Project and Task Name are required, so the project has to exist first.
Add Time
ActionIn Zapier“Adds your time to a task.”
Logs time on a task. Project, Task and Time are required, and Time takes values like 4h or 2h 15m.
Start Timer
ActionIn Zapier“Starts a new timer for a task.”
Starts a new timer on a task. It needs the Project and the Task, both required.
Everhour searches on Zapier
5 search steps look for data that already exists in Everhour, so a later step can use it.
Search steps sit at the bottom of the action list in the editor, under their own SEARCH heading. They fetch something that already exists so later steps can use it. Three settings decide what happens when the lookup goes sideways.
Find Member
SearchIn Zapier“Finds a member by name.”
Looks up a member of your Everhour team by name, with Member Name required.
Find Internal Project
SearchFind or createIn Zapier“Finds a project for creating task/section by name”
Finds an Everhour project by name, the kind that tasks and sections can be created in. Projects from connected tools will not be found. Its find-or-create variant, Find or Create Internal Project, is this same search with creation ticked.
Find Project
SearchIn Zapier“Finds a project by name”
Retrieves a project by its name, Project Name being the only required field. It has no find-or-create variant.
Find Section
SearchFind or createIn Zapier“Finds a section by name.”
Locates a section by name inside a project; Project and Section Name are both required. Find or Create Section is the same search with creation ticked, so a missing phase gets added on the fly.
Find Task
SearchFind or createIn Zapier“Finds a task by name.”
Fetches a task by its Task Name, the one required field. Find or Create Task is this search with creation ticked, which avoids duplicates when the same request comes in twice.
The three settings every search exposes
- Successful if no search results are found?On its default, a search that finds nothing stops the Zap and the steps depending on it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking this turns a search into a find-or-create. It then drops the setting above and asks for what it needs to create the missing item.
- 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.
Where an Everhour Zap breaks
Zapier attaches no help article to Everhour and no limit specific to the app is documented. The breakages come from Zapier's general mechanics, and they show up in time tracking in very recognizable ways.
Four cases cover the ground. If your Zap misbehaves beyond them, the Zapier troubleshooting page is the next stop.
Past hours never come through
A Zap reacts only to what happens after it is published. Time already logged, tasks and projects created before are not picked up; moving that backlog is a separate job.The Zap that feeds itself
New Task followed by Create Task, or Task Time Updated followed by Add Time on the same task, fires the trigger again and again. Tasks drain fast.A bulk import gets held back
Importing a batch of projects or tasks sends a burst of events at once. Zapier's flood protection can hold such a batch back instead of running it.A tag only counts once
List Tags keeps track of what it has already seen, so the same tag never starts the Zap twice. A tag that already existed when the Zap went live never fires it.
Need help automating Everhour with Zapier?
A person reads every message.



