Resources · Make integration

Everhour Make integrationAutomate Everhour with Make.

What if your timesheets filled themselves while projects and clients stayed in sync? The Everhour Make integration offers 37 modules, including 6 triggers. This page is for teams who bill by the hour: it shows how to link your account and build a first scenario step by step.

Try the Everhour integration on MakeSee the 37 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Everhour Make integration do for you?

It lets Everhour talk to your other apps without code. In Make you build a scenario, the automation itself, from modules, the bricks that each do one job in one app. Here that means watching new clients, projects, tasks and timers, then creating, updating or deleting the matching records.

Projects that arrive organised. Watch New Projects spots each new project, and Create a Section adds the phases your team always uses, so nobody rebuilds the same structure by hand.

Hours logged where the work happens. A support agency can let Add a Time Record write the time spent on a ticket straight into Everhour, while Start a Timer and Stop a Timer follow events in another tool.

Clients kept in step with sales. When a deal closes in the CRM, Search Clients checks whether the client exists and Create a Client fills the gap; Update a Client keeps details aligned afterwards.

The Everhour documentation lists no specific limits, and it warns that its own content is AI-generated and worth double-checking. When a module is missing, Make an API Call reaches the rest of the Everhour API with the same connection. If you are still weighing platforms, the n8n vs Make comparison sets out the criteria, and Make training covers the editor from zero. Stuck on an error later? See Make troubleshooting.

Connect

How do you connect your Everhour account to Make?

  1. 01

    Copy your API key from Everhour

    Make needs an active Everhour account and its API key. In Everhour, open your profile, scroll to the bottom of the page and copy the API key shown there. Keep it at hand for the next step.

  2. 02

    Open the connection window in Make

    Add any Everhour module to your scenario and click Create a connection. A connection is your Everhour account linked to Make once, then reused by every Everhour module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when several people share the workspace. Paste the API key you copied, confirm, and Make can now read your Everhour data.

First scenario

Your first scenario: give every new Everhour project its sections

GoalWhen a project is created in Everhour, Make adds a first section to it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Add Watch New Projects

    Search for Everhour, pick Watch New Projects and choose your connection, or click Create a connection if this is your first Everhour module.

  3. 03

    Chain Create a Section

    Click the + on the right of the trigger and add Create a Section. Map the project from the bundle, the item passed on by the trigger, then fill the fields Make shows.

  4. 04

    Test with Run once

    Create a test project in Everhour, then click Run once. Open the bubble above each module to read the bundle it received and check the section in Everhour.

  5. 05

    Schedule and switch it on

    Open the clock on the first module: the default is every 15 minutes, the shortest gap on the Free plan. Save, then switch the scenario on so it keeps watching new projects.

Triggers

What can start an Everhour scenario?

6 modules start a scenario when something happens in Everhour. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Everhour as soon as it happens.

Everhour1Watch New Clients

Watch New Clients

triggerIn the docs only

Each client added in Everhour reaches your scenario as a bundle, so the billing tool, the CRM record or a shared folder can follow without anyone retyping a name.

How it fires
scheduled. Make checks Everhour on the scenario's schedule, every 15 minutes by default, so a client created just after a check waits for the next one.
When to use it
your finance team keeps the customer list in another app and wants every new Everhour client mirrored there.
Watch out
15 minutes is also the shortest gap on the Free plan, so the copy is never instant there.
Everhour2Watch New Projects

Watch New Projects

triggerIn the docs only

A new Everhour project becomes the starting signal for everything that usually follows it: sections, a kickoff message, a folder for the deliverables.

How it fires
scheduled. Make asks Everhour for new projects at the interval set on the scenario's clock, not at the moment the project appears.
When to use it
a project manager opens projects by hand in Everhour and wants the same setup applied each time, as in the first scenario above.
Watch out
a scenario that also creates projects with Create a Project will see its own projects come back through this trigger, so plan filters before you switch both on.
Everhour3Watch New Tasks

Watch New Tasks

triggerIn the docs only

Fresh tasks in Everhour can travel to the places where your team actually talks about work, such as a chat channel, a board app or a shared sheet.

How it fires
scheduled. On each run of the schedule, Make looks for tasks added since its last visit and hands each one on as a bundle.
When to use it
a designer should hear about a task assigned to the studio without opening Everhour.
Watch out
each task is its own bundle, and every module after the trigger runs once per task, which counts as one operation, the unit Make bills, each time.
Everhour4Watch New Timer Started

Watch New Timer Started

triggerIn the docs only

You learn the moment of work beginning, give or take the schedule: someone started a timer in Everhour and your scenario can react to it.

How it fires
scheduled. Make polls Everhour on the scenario's clock, so the reaction comes at the next check rather than the second the timer starts.
When to use it
set a status in your team chat to show who is busy on which client.
Watch out
a timer started and stopped between two checks may never be seen as running; pair it with Watch New Timer Stopped if every session matters.
Everhour5Watch New Timer Stopped

Watch New Timer Stopped

triggerIn the docs only

Finished work sessions become data you can reuse: every stopped timer in Everhour can feed a log, an invoice line or a follow-up message.

How it fires
scheduled. Make checks for stopped timers at the scenario's interval, 15 minutes unless you change the clock on the first module.
When to use it
a consultant stops the timer after a client call and the notes app should receive the session so the summary gets written.
Watch out
on the Free plan the scenario cannot check more often than every 15 minutes, so do not build anything that expects an immediate reaction.
Everhour6Watch Task Time Updated

Watch Task Time Updated

triggerIn the docs only

Budget drift shows up early: this trigger picks up tasks whose tracked time changed, so you can compare hours with what was sold.

How it fires
scheduled. Make checks Everhour on the scenario's schedule and passes on each task whose time moved since the previous check.
When to use it
an account manager wants a warning in a shared channel when a fixed-price task keeps collecting hours.
Watch out
a busy team updates time constantly, so add a filter right after the trigger to keep only the tasks that matter and save operations.
Modules

What can Make do in Everhour?

Everhour gives you 31 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Everhour1

Add a Time Record

ActionIn the docs only

Hours land in Everhour without anyone opening a timesheet: the module writes a time record from data the scenario already holds, such as a finished call or a resolved ticket.

When to use it
your support desk tracks effort per ticket and that billable time should appear in Everhour too.
Watch out
a source item that goes through twice gets its hours logged twice. Test with Run once first.
Everhour2

Create a Client

ActionIn the docs only

A signed deal opens its client in Everhour by itself, giving future projects and budgets a place to live from day one.

When to use it
an opportunity moves to won in the CRM and the delivery team needs the client ready before the kickoff meeting.
Watch out
nothing here blocks a duplicate; place Search Clients before it and let the creation run only when the search comes back empty.
Everhour3

Create a Project

ActionIn the docs only

New work gets a home in Everhour as soon as it is approved somewhere else, so hours can be tracked against it from the first session.

When to use it
a quote gets signed in your e-signature app, or an intake form confirms a new engagement.
Watch out
if another scenario runs Watch New Projects, the project created here will trigger that scenario too; check that the two do not feed each other.
Everhour4

Create a Section

ActionIn the docs only

Projects come out structured: this module adds a section inside an Everhour project, which keeps tasks grouped by phase or deliverable.

When to use it
right after Create a Project or Watch New Projects, to lay out the same stages on every engagement.
Watch out
one module adds one section, so a template with several stages needs several modules in a row, and each counts an operation per run.
Everhour5

Create a Task

ActionIn the docs only

Requests collected in another tool become Everhour tasks people can start a timer on, inside the project you choose.

When to use it
a help desk ticket, a form entry or a card on a board should turn into trackable work for the team.
Watch out
when requests belong to different clients, map the project from an earlier bundle; picking one project in the field sends every task to the same place.
Everhour6

Delete a Client Budget

ActionIn the docs only

Clients whose retainer has ended stop being measured against a cap that no longer applies, because this module removes the budget attached to them.

When to use it
a contract closes in your contract tool and the client switches to plain hourly billing.
Watch out
treat the deletion as final and keep this module behind a filter that checks the contract status before it runs.
Everhour7

Delete a Project

ActionIn the docs only

Your Everhour project list stays short without manual cleanup: the module removes a project the scenario points to.

When to use it
an opportunity marked lost in the CRM had a project opened too early, and it should leave time tracking.
Watch out
the deletion is final from Make's side; try it with Run once on a throwaway project before letting it touch real work.
Everhour8

Delete a Section

ActionIn the docs only

Project structures follow the plan when it changes, since this module takes a section out of an Everhour project.

When to use it
a phase is dropped from the revised quote and its section should disappear with it.
Watch out
identify the project and the section from an earlier module, such as Search Sections; typing an identifier by hand is where the wrong section gets removed.
Everhour9

Delete a Task

ActionIn the docs only

Cancelled requests leave Everhour at the same time as they leave the tool where they started, so nobody logs hours on dead work.

When to use it
a ticket is closed as won't fix in your help desk and its matching task should go.
Watch out
if Search Tasks upstream returns several tasks, every one of them reaches this module, so tighten the search before switching the scenario on.
Everhour10

Delete a Task Estimate

ActionIn the docs only

A task goes back to open-ended tracking: this module removes its estimate while leaving the task and its hours in place.

When to use it
the client changes the scope and the original estimate no longer means anything.
Watch out
to adjust the figure rather than drop it, Update a Task Estimate is the right module; to remove the whole task, use Delete a Task.
Everhour11

Delete a Time Record

ActionIn the docs only

Timesheets get corrected at scale: the module removes a time record, which helps when entries were logged against the wrong task.

When to use it
after Search Time Records finds entries an earlier scenario created by mistake.
Watch out
hours deleted this way do not come back through Make, so run the search alone first with Run once and read every bundle.
Everhour12

Get a Client

ActionIn the docs only

The complete client record arrives in your scenario, so later modules can use its details instead of the few values a trigger passed on.

When to use it
you already know which client is involved, from a trigger or a previous module, and an email or invoice needs the rest.
Watch out
it reads one client you point to; when you do not know which one yet, start with Search Clients.
Everhour13

Get a Project

ActionIn the docs only

Everything Everhour holds about one project becomes available to the next modules, ready to map into a report or a message.

When to use it
Watch Task Time Updated tells you a task moved, and you want its parent project's details in the alert.
Watch out
the module needs to know which project to read, so map it from a bundle rather than hard-coding a single project.
Everhour14

Get a Running Timer

ActionIn the docs only

Your scenario can find out whether a timer is running in Everhour right now, and what it is attached to.

When to use it
before Start a Timer, to avoid launching a second session on top of one already in progress.
Watch out
plan for the case where nobody is tracking time, and add a filter so the next modules handle both outcomes.
Everhour15

Get a Section

ActionIn the docs only

One section's details come back from Everhour, which gives messages and reports the right phase name instead of a bare reference.

When to use it
a task alert should say which stage of the project the task sits in.
Watch out
like the other Get modules, it reads a single known section; Search Sections is the one to use when you have to find it first.
Everhour16

Get a Task

ActionIn the docs only

A task's full record comes into the scenario, so a notification or a sync can carry more than the little a trigger delivers.

When to use it
Watch New Timer Stopped reports a session, and the message to the client should name the task that was worked on.
Watch out
each call reads one task and costs one operation, so avoid placing it after a search that already returns the details you need.
Everhour17

List Users

SearchIn the docs only

The people in your Everhour team come out as a list, one bundle per user, ready to drive reminders or team reports.

When to use it
a timesheet reminder has to reach every team member through email or chat.
Watch out
every module placed after it runs once per person, so the operation count grows with the team; filter the list before sending anything.
Everhour18

Make an API Call

ActionIn the docs only

Anything the other modules leave out stays within reach, because this module calls the Everhour API directly with the connection you already set up.

When to use it
you need an Everhour feature that none of the listed modules covers.
Watch out
you write the request yourself, so know which endpoint you need before you start, and check the response with Run once.
Everhour19

Search Clients

SearchIn the docs only

Your scenario checks whether a client already exists before doing anything, which is the simplest guard against duplicates in Everhour.

When to use it
in front of Create a Client, when deals from the CRM might concern a customer the team already works with.
Watch out
a search can return zero, one or several clients; with zero results the modules after it do not run, so plan the creation path accordingly.
Everhour20

Search Projects

SearchIn the docs only

Finding the right Everhour project becomes automatic, so a task, an entry or a message lands in the correct place.

When to use it
an incoming request mentions a project by name and the scenario must locate it before adding work.
Watch out
several projects can match; each match becomes its own bundle and the next modules run for every one, so narrow the search or keep only the first result.
Everhour21

Search Sections

SearchIn the docs only

The sections of your projects become easy to locate, which lets a scenario place a new task in the right phase.

When to use it
requests arrive tagged design or development and should go into the matching section of the project.
Watch out
projects built from the same template share section names, so combine the search with the project, or you may pick a section from the wrong client.
Everhour22

Search Tasks

SearchIn the docs only

Existing work is found before new work is created, keeping Everhour free of the same task entered twice.

When to use it
a ticket gets updated in the help desk and the scenario must find its Everhour task to update or close it.
Watch out
the results feed every module after the search, one run per task found; a vague search can therefore touch far more tasks than you meant.
Everhour23

Search Time Records

SearchIn the docs only

Tracked hours become raw material for reports, invoices or checks, because the module pulls the matching time records out of Everhour.

When to use it
before an invoice goes out, to gather the entries of one client and send them to a spreadsheet.
Watch out
each record is a separate bundle; to build one invoice or one sheet row from them, add an aggregator after the search.
Everhour24

Start a Timer

ActionIn the docs only

Time tracking begins at the right moment without anyone remembering to press the button in Everhour.

When to use it
a meeting starts in your calendar app, or a support agent picks up a ticket, and the clock should run on the matching task.
Watch out
check first with Get a Running Timer, because starting a new session while another runs can leave the timesheet in a state nobody expected.
Everhour25

Stop a Timer

ActionIn the docs only

Sessions close cleanly even when people forget, since the module stops the running timer in Everhour for you.

When to use it
a call ends in your meeting tool, or a ticket gets marked solved, and the tracking should end with it.
Watch out
the timer stops when the scenario runs, not when the event happened, so with a scheduled trigger upstream expect the gap of the schedule.
Everhour26

Update a Client

ActionIn the docs only

Client details stay the same in Everhour and in the tool where sales maintain them, without copy and paste.

When to use it
a company renames itself or changes contact in the CRM, and the time tracker should reflect it.
Watch out
leaving a field empty in the module may overwrite a value you wanted to keep; test on one client with Run once and compare.
Everhour27

Update a Project

ActionIn the docs only

Project information follows decisions made elsewhere, so the team sees the current state in Everhour without anyone editing it.

When to use it
a project changes owner or status in your project board and Everhour should match.
Watch out
a scenario that watches projects and updates them can react to its own change; keep a filter between trigger and update.
Everhour28

Update a Section

ActionIn the docs only

Section names and details keep up with the plan, useful when phases get renamed after the kickoff.

When to use it
the quote is revised, a stage called draft becomes review, and the section in Everhour should say so.
Watch out
point to the section from Search Sections or Get a Section; mapping the wrong bundle renames a phase in another project.
Everhour29

Update a Task

ActionIn the docs only

Tasks in Everhour mirror what changes in the tool where the work is discussed, from the name to the details your team relies on.

When to use it
a card changes title or assignee on your board and the Everhour task should follow.
Watch out
run Search Tasks first to find the task; when the search returns nothing, nothing gets updated and the change is silently lost.
Everhour30

Update a Task Estimate

ActionIn the docs only

Estimates stay honest: the module changes the estimate on a task, so progress reports compare hours with the latest agreement.

When to use it
a change request is approved and the extra hours sold should appear on the task.
Watch out
this module adjusts an estimate; if the task should have none at all, Delete a Task Estimate is the one to place instead.
Everhour31

Update a Time Record

ActionIn the docs only

Time entries get corrected without reopening every timesheet, which keeps invoices built on the right hours.

When to use it
entries were logged on the wrong task, and Search Time Records has found them for you.
Watch out
change one record with Run once and check it in Everhour before letting the scenario rewrite a whole batch of entries.
Need help

Need help automating Everhour with Make?

A person reads every message.

FAQ

Everhour and Make: frequently asked questions

01Is the Everhour Make integration free?
Yes, on the Make side. Everhour is a standard app, available from the Free plan. That plan allows 2 active scenarios, 15 minutes minimum between two scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans go down to a 1 minute interval with unlimited active scenarios. You still need an active Everhour account, whose subscription follows the Everhour pricing page. An operation, one module run on one bundle, is what Make counts on your plan, so keep an eye on how many modules each run triggers.
02What do you need to connect Everhour to Make?
An active Everhour account and its API key. In Everhour, open your profile, scroll to the bottom of the page and copy the key. In Make, add an Everhour module, click Create a connection, give it a name if you like, and paste the key. The connection is then reused by all Everhour modules in your scenarios. If a scenario later loses access, a likely cause is a key that changed on the Everhour side, since the connection relies on it; paste the new one into the same connection.
03Do Everhour triggers in Make react in real time?
No. The six Everhour triggers are presented here as scheduled: Make checks Everhour on the scenario's schedule, every 15 minutes by default, and never faster than every 15 minutes on the Free plan. The Make directory was unavailable when this page was written, so check the badge on the module in your editor: a clock means scheduled, a lightning bolt means instant. For the same reason, a scenario built on these triggers suits follow-ups and syncs better than anything that needs an answer within seconds.
04What if an Everhour module is missing in Make?
Use Make an API Call. It is part of the Everhour app in Make and lets a scenario call any endpoint of the Everhour API with the same connection as the other modules. The Everhour documentation lists no specific limits, but it notes that its content is AI-generated and should be verified, so test each call with Run once. Once the call works, you can map its result into the next modules exactly like the output of any other Everhour module.
05Should you use Make or n8n for Everhour?
It depends on your criteria, not on a winner. On the Make side, Everhour comes with 37 modules, 6 of them triggers, plus Make an API Call for the rest, all usable from the Free plan. Whether an n8n node exists for Everhour is not covered here, so check it directly before you choose, and compare the two platforms on the features you actually need. Test your use case with Run once either way, then decide.
Same platform

Other docs you might need on this stack.

Browse all integrations