Productivity · Integration
Everhour
Add Everhour to your product for your customers, and give your AI agents governed access to it.
Everhour's API at api.everhour.com takes the key in an X-Api-Key header and answers an unauthenticated request with 403 rather than 401, so health checks written to expect 401 report it as broken. Its object model is unusual because Everhour is normally layered on top of another tracker: project and task identifiers carry a source prefix, so an Asana-backed project and a native Everhour project have visibly different ids, and code that assumes a single id format breaks the first time a customer connects a second tool. Time records are per user, per date and per task, and a running timer is a separate resource from the recorded entries, so you must stop a timer before its time appears in reports. Estimates attach to tasks and can be set either per task or per assignee, and budgets attach to projects with their own threshold and notification settings. Historical time can be written retroactively for any date, which makes correction flows straightforward. fastn holds each customer's own key, keeps it refreshed, and keeps time writes attributed to the right tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Everhour account so your product can log time against their projects without a shared key
Write a time record against a task when work completes inside your product, using the correct source-prefixed task id
Read project budgets and warn a customer's project manager when logged hours approach the threshold
Pull per-user time totals for a date range into your own invoicing or utilisation reports
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent log time against a task on a user's behalf and report the resulting entry, with each write audited per tenant against that tenant's own key
Have an agent summarise where a team's hours went last week by project and task
Allow an agent to flag tasks whose logged time has exceeded their estimate
Example prompt
How many hours did we log on the migration project last week, and who logged them?
Set up Everhour in 4 steps
- 01Enable the Everhour connector from your fastn dashboard.
- 02Have each customer authorise their own Everhour account, so calls run under their credentials rather than a shared key.
- 03Decide which work items, assignees and due dates your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Everhour integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Everhour integration without building it. Your customers connect their own Everhour account inside your product and work their work items, assignees and due dates there, with no per-customer code on your side.
- Handle the part that actually costs time: every team configures its own fields, statuses and workflow stages. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Everhour update is not your on-call problem.
- One integration serves your product and your agents. The same governed Everhour connection powers in-product features and gives AI agents scoped, audited access, so you keep work items in step with what happens in your product without wiring it twice.
Used by these teams
Compare with
Jira
Asana
ClickUpOften used alongside
Tools the same teams tend to run next to Everhour, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceEverhour integration FAQ
How do I add an Everhour integration to my product?
Enable the Everhour connector in your fastn dashboard, then let each customer authenticate their own Everhour account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Everhour client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Everhour account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Everhour account and only ever sees their own work items, assignees and due dates. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Everhour integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent log time against a task on a user's behalf and report the resulting entry, with each write audited per tenant against that tenant's own key
Who maintains the Everhour integration?
fastn does. When Everhour changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create and update work in Everhour automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in Everhour can trigger your workflows in return.
Does it adapt to each team's own Everhour setup?
Yes. However a team has configured Everhour, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.
What can I build with the Everhour integration?
A common starting point: let a customer connect their own Everhour account so your product can log time against their projects without a shared key. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Everhour integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Everhour does not change your per-connector cost. You can start free with 3 connected accounts.
Add Everhour to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.