Everhour
Everhour time tracking: projects, tasks, time records, timers, timecards, timesheets, expenses, invoices, clients, schedule, time off and reports.
About
Everhour ships in the w6w first-party pack. It declares 97 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.everhour- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Productivity · Project Management · Finance & Accounting
Overview
Everhour is a time tracker that lives inside the project tools a team already uses. This app drives its REST API from a workflow: read and manage projects, sections and tasks (including task estimates and custom fields), log time or run a timer against a task, and read per-user, per-task and per-project time.
Beyond time entries it covers the rest of the Everhour account: clients and their budgets, expenses and expense categories, invoices (create, refresh from tracked time, mark draft/sent/paid, export), the resource-planner schedule, time off with its types and allocations, timecards (clock in/out), weekly timesheets with approval, project/client/user reports, and webhooks for reacting to Everhour events.
Authentication is a single personal API key sent as the X-Api-Key header. The key acts as its owner, so what a workflow can see and change follows that user’s role.
Build with Everhour
Three routes to the same 97 actions. The Workflow tab is generated from Everhour's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Create Attachment
attachment-create Upload an attachment (base64) to attach to an expense or time off.
Add Attachment To Expense
expense-attachment-add Upload an attachment (base64) directly onto an expense.
Delete Expense Category
expense-category-delete Delete an expense category, moving or deleting its expenses.
Export Invoice
invoice-export Export an invoice to the connected accounting system (Xero, QuickBooks or FreshBooks).
Refresh Invoice Line Items
invoice-refresh Rebuild an invoice's line items from the current tracked time and expenses.
Update Invoice
invoice-update Update an invoice's number, dates, notes, tax, discount or line items.
Sync Integration Project
project-sync Import a project that exists in a connected tool (Asana, Trello, ClickUp, ...) into Everhour immediately. Safe to repeat.
Create Time Off
time-off-create Create a time-off entry (goes through the resource-planner assignments endpoint).
Request Timesheet Approval
timesheet-approval-request Submit a week for approval (or approve it, for an admin).
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Everhour's real ids.
{
"manifestVersion": "2",
"name": "everhour-example",
"steps": [
{
"id": "allocation-create",
"uses": {
"app": "io.w6w.everhour",
"action": "allocation-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"startDate": "<startDate>",
"endDate": "<endDate>",
"users": "<users>"
}
}
]
}Here are some of the things you can do
-
Create Time-Off Allocation
performallocation-create -
List Time-Off Allocations
searchallocation-list -
Update Time-Off Allocation
performallocation-update -
Create Assignment
performassignment-create -
List Assignments
searchassignment-list
+92 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Everhour, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Everhour. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "allocation-create",
payload: {
startDate: "<value>",
endDate: "<value>",
// contractStartDate: "<value>",
users: "<value>",
timeOffType: "<value>",
days: "<value>",
// daysCarried: "<value>",
// accrualFrequency: "<value>",
// restrictOverAllocation: "<value>",
// completed: "<value>",
// notes: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action allocation-create --payload '{"startDate":"<value>","endDate":"<value>","users":"<value>","timeOffType":"<value>","days":"<value>"}'Give an AI agent Everhour — without giving it Everhour's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.everhour#allocation-create",
"input": {
"startDate": "<startDate>",
"endDate": "<endDate>",
"users": "<users>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Everhour connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Everhour's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Everhour itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Everhour declares its own checks, so its health is a property of the app rather than something the host guesses at.
Everhour platform status
API reachable
Unauthenticated GET https://api.everhour.com/users/me. A 403 carrying Everhour's JSON `{"code": …, "message": …}` passes — it proves the API and its auth layer are answering. Credential validity is the derived `auth:*` check's job.