Everhour - Atako

Let your agents log time, run timers and follow projects, tasks and clients in your Everhour team.

Connection

Authentication: API key.

Sign in at app.everhour.com → open your profile page (app.everhour.com/#/account/profile) → scroll to the bottom → copy the API key. The key acts with your own role (admin, supervisor or member); Everhour has no API scopes. API access is limited to some Everhour plans — see everhour.com/pricing.See Everhour’s documentation.

Read actions (10)

Action	Description
`get_current_timer`	Get the running timer of the key owner (status “active” with task, duration in seconds and startedAt), or an empty timer when none runs.
`get_me`	Get the user the API key belongs to: numeric id, name, email, role (admin, supervisor, member), status, capacity, permissions, time-tracking policy, timezone and team (id, name, work days, lock-time settings). The API key itself is removed from the response. No argument.
`get_project`	Fetch one project by id (string, e.g. “ev:1234567890”, from list_projects).
`list_clients`	List clients (id, name, project ids). Argument: query (string, search by client name).
`list_project_sections`	List the sections of a project (numeric section id, name, position, status). Section ids are used by create_task.
`list_project_tasks`	List tasks of a project (task id string such as “ev:9876543210”, name, section, status, tracked time). Arguments: query (string, search by name), exclude-closed (boolean), page (integer), limit (integer, 250 max).
`list_projects`	List projects the key can access. Project ids are strings prefixed by their source, e.g. “ev:1234567890” (Everhour) or “as:…” (Asana). Arguments: query (string, search by name), platform (one of as, ev, b3, b2, pv, gh, in, tr, jr — filter by integration), limit (integer), page (integer, 1-based).
`list_team_time_records`	List time records of the whole team over a date range (only the current day when from/to are omitted). Arguments: from (string YYYY-MM-DD), to (string YYYY-MM-DD, inclusive), limit (integer, 50000 max), page (integer).
`list_team_users`	List team members (including removed ones) with their numeric user id, name, email, role and status. Use it to find the user id for list_user_time_records or add_time. Arguments: query (string, filter by name or email), limit (integer).
`list_user_time_records`	List time records of one user (record id, time in seconds, date, task, comment). Arguments: user_id (integer, from list_team_users, required), from (string YYYY-MM-DD), to (string YYYY-MM-DD, inclusive), limit (integer, 50000 max), page (integer), offset (integer, takes precedence over page).

Write actions (5)

Action	Description
`add_time`	Add time on a task for a date. Upsert: one record per (user, date, task) — posting the same combination again replaces its duration. Arguments: time (integer, seconds, required — 3600 = 1 h), date (string YYYY-MM-DD, optional), task (string task id such as “ev:9876543210”, from list_project_tasks, optional), user (integer user id from list_team_users, optional), comment (string, optional).
`create_task`	Create a task in an Everhour project. Arguments: project_id (string, e.g. “ev:1234567890”, required), name (string, required), section (integer section id from list_project_sections, optional), description (string, plain text, 2000 chars max, optional), labels (array of strings, optional), status (“open” or “closed”, optional), dueOn (string YYYY-MM-DD, optional), startOn (string YYYY-MM-DD, optional), assignees (array of objects { userId: integer }, optional — ids from list_team_users).
`start_timer`	Start a timer for the key owner on a task; a timer already running on another task is stopped and saved first. Arguments: task (string task id such as “ev:9876543210”, required), userDate (string YYYY-MM-DD, optional — the user’s local date), comment (string, optional).
`stop_timer`	Stop the key owner’s running timer; the tracked duration is saved as a time record on its task and returned. Deletes nothing. No arguments.
`update_time_record`	Update one time record by id. Arguments: time_id (integer record id from list_user_time_records or list_team_time_records, required), time (integer, seconds, required), date (string YYYY-MM-DD, optional), task (string task id, optional), user (integer user id, optional), comment (string, optional).

Permissions

Every action above must be explicitly granted to an agent before it can be used. See Permissions for the grant model and Security for how credentials are protected.

Last reviewed against the provider API: September 2026.