Integration

Timely integration

Timely is an automatic time tracking and planning tool for teams. With this API an agent can log, edit, time and bulk-import time entries, manage projects, clients, tags, teams, users (invite, update, remove), planned tasks, project and time entry states, linked work items from other tools and webhooks, lock days, and read reports, utilisation insights, capacities, permissions and compliance. The OAuth management routes, avatar upload, the bulk project reassignment and bulk tag routes (their operation values are undocumented) and the duplicate team PUT and day-lock PUT routes are not exposed. Authentication is OAuth 2.0 with scope manage; the account id is the number in your Timely web address (app.timelyapp.com/<account id>/...).

Connect Timely How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Timely.Built from the 77 Timely tools below, on the connection you add once.

What you can do with Timely

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

User, 7 operations

delete_userDelete userDELETEDelete/remove user from account. Requires delete permission for the user.
get_current_userGet current userGETReturns the connected user: id, name, email, role and settings in this account. Use it to find your own user id.
get_userGet userGETGet specific user details. Requires read permission for the user.
invite_userInvite userPOSTInvites a person to the account by email (name, email and role_id required); if the email already exists the person is re-invited with the new settings. Needs an active or trial subscription with a free seat.
list_usersList usersGETLists users in the account. Requires global user read permission or project update permission.
search_usersSearch usersGETSearch users. Requires create or update project permission.
update_userUpdate userPUTChanges a user. The vendor requires name and email on every update (email is ignored): read the user with get_user first and send name back unchanged with your change.

Linked work item, 6 operations

create_linked_work_itemCreate linked work itemPOSTCreates a linked work item (an issue or ticket from another tool that time can be logged against). title and external_id are required.
delete_linked_work_itemDelete linked work itemDELETEDelete a linked work item from the account. Existing time entries linked to the item keep rendering its metadata.
get_linked_work_itemGet linked work itemGETRetrieve a specific linked work item by ID.
list_linked_work_itemsList linked work itemsGETRetrieve linked work items for the account. Supports filtering by search query, status, project, assigned user and external_id, plus limit/offset pagination.
update_linked_work_itemUpdate linked work itemPUTUpdate an existing linked work item. All fields are optional for partial updates.
upsert_linked_work_itemUpsert linked work itemPUTCreates or updates a linked work item keyed on your own external_id: creates it (title then required) when none exists, revives a deleted one, otherwise updates it. The path external_id wins over the body.

Project, 6 operations

create_projectCreate projectPOSTCreates a project. name and rate_type are required; set the client with client_id (or new_company to create one) and the rates and members with hour_rate, users or team_ids. Users not assigned cannot log time on it.
delete_projectDelete projectDELETEDelete a project. This will permanently remove the project from the account.
get_projectGet projectGETRetrieve details for a specific project.
list_projectsList projectsGETList all projects in the Timely account. The projects will be returned in a paginated format.
pin_projectPin projectPOSTPins a project for the connected user (up to 50 per account). Pinning it again is allowed.
update_projectUpdate projectPUTChanges a project; only the fields sent are updated. If you send users, it is the full member list: anyone left out loses access to log time (their past entries stay).

Task, 6 operations

create_taskCreate taskPOSTCreates a task (a planned piece of work) on a project for a date range. title, from, to and project_id are required. Needs the Planning feature on the account.
delete_taskDelete taskDELETEDelete a task.
get_taskGet taskGETRetrieve details for a specific task.
list_tasksList tasksGETList all tasks in the account. Tasks are returned in a paginated format with optional filtering by date range, user, project, and completion status.
summarize_tasksSummarize tasksGETGet task summaries grouped by resource type (users or projects). Returns aggregate counts and duration totals.
update_taskUpdate taskPATCHChanges a task; only the fields sent are updated. Set completed_at to mark it done.

Team, 6 operations

create_teamCreate teamPOSTCreates a team. Only name is required; users lists the members as objects {user_id, lead, hide_hours}.
delete_teamDelete teamDELETEDeletes a team. delete_project_users also removes its members from the team's projects.
get_teamGet teamGETTeam details including users and project IDs
list_teamsList teamsGETLists teams in alphabetical order (first 100 by default); limit, offset and order page through them, and filter=mine keeps your own teams.
search_teamsSearch teamsGETSearches teams by name; paginated with page and per_page.
update_teamUpdate teamPATCHChanges a team. If you send users it is the full member list: a person left out is taken off the team (send {user_id, deleted: true} to remove an agent).

Time entry, 6 operations

bulk_change_time_entriesBulk change time entriesPOSTCreates, updates and deletes many time entries in one request (create: entry objects, update: objects with id, delete: entry ids). Partial success is possible: errors are listed per record.
create_time_entryCreate time entryPOSTLogs time on a project for a day. project_id and day are required; give the duration as hours/minutes/seconds or as from and to. The user must be a member of the project (422 otherwise).
delete_time_entryDelete time entryDELETEDeletes a time entry. Locked or invoiced entries cannot be deleted.
get_time_entryGet time entryGETRetrieve details for a specific time entry.
list_time_entriesList time entriesGETLists time entries for one day (day, default today) or a range (since and upto, both needed), filtered by project, user or task. Paginated: page and per_page (max 5000).
update_time_entryUpdate time entryPUTChanges a time entry; only the fields sent are updated. A billed or locked entry cannot be edited.

Tag, 5 operations

create_tagCreate tagPOSTCreate a new label (tag) for the account. Labels can be hierarchical by specifying a parent_id.
delete_tagDelete tagDELETEDelete a label from the account. This will permanently remove the label.
get_tagGet tagGETRetrieve a specific label by ID. The response includes child labels if any exist.
list_tagsList tagsGETRetrieve all labels (tags) for the specified account. Labels help classify work, group related tasks, and require certain information for events.
update_tagUpdate tagPUTUpdate an existing label. All fields are optional for partial updates. Set active to false to archive a label.

Webhook, 5 operations

create_webhookCreate webhookPOSTSubscribes an HTTPS URL to events (hours, projects, labels or forecasts, each :created, :updated or :deleted). With secret_token set, each delivery carries an X-Signature header, an HMAC-SHA256 of the body.
delete_webhookDelete webhookDELETEDelete a webhook. This will permanently remove the webhook and stop all future notifications.
get_webhookGet webhookGETRetrieve details for a specific webhook.
list_webhooksList webhooksGETRetrieve all webhooks configured for the account. Webhooks allow you to receive HTTP POST notifications when events occur.
update_webhookUpdate webhookPUTChanges a webhook's URL, events, secret, headers or active state; only the fields sent are updated.

Client, 4 operations

create_clientCreate clientPOSTCreates a client (a customer projects belong to). Only name is required; returns the new client with its id.
get_clientGet clientGETClient details and project counts
list_clientsList clientsGETLists the account's clients in alphabetical order (first 10000 by default); show filters active or archived ones, limit and offset page through them.
update_clientUpdate clientPUTChanges a client's name, active state, color or external references; send only what changes.

Permission, 4 operations

delete_state_permissionsDelete state permissionsDELETEDeletes all permissions of a project state (the id is not used to pick one). Admin only.
list_current_user_permissionsList current user permissionsGETRetrieve all resource permissions for the currently authenticated user.
list_user_permissionsList user permissionsGETRetrieve all resource permissions for a specific user. Requires read access to users.
set_state_permissionsSet state permissionsPOSTSets which roles, team leads and project leads may use a project state. Admin only; system-managed states cannot be changed.

Project state, 4 operations

create_stateCreate statePOSTCreates a project state (a status a project can be in). Admin only.
delete_stateDelete stateDELETEDelete a state. Only admin users can delete states and system-managed states cannot be deleted.
list_statesList statesGETRetrieve all states for the specified account, including their permissions.
update_stateUpdate statePUTUpdate an existing state. Only admin users can update states.

Time entry state, 4 operations

create_time_entry_stateCreate time entry statePOSTCreates a time entry state (a status such as approved that an entry can be in). Admin only.
delete_time_entry_stateDelete time entry stateDELETEDelete a time entry state. Only admin users can delete states and system-managed states cannot be deleted.
list_time_entry_statesList time entry statesGETList all available time entry states for the account.
update_time_entry_stateUpdate time entry statePUTUpdate an existing time entry state. Only admin users can update states.

Capacity, 2 operations

list_user_capacitiesList user capacitiesGETRetrieve capacity configurations for a specific user. Capacities define a user's working hours, working days, and daily/weekly hour limits.
list_users_capacitiesList users capacitiesGETRetrieve capacity configurations for multiple users in the account. Supports filtering by user IDs and date range.

Day lock, 2 operations

list_day_locksList day locksGETLists locked or unlocked days per user, for a date range (since, until) or specific dates.
set_day_locksSet day locksPOSTLocks or unlocks days for the given users so their time entries for those dates cannot (or can again) be created, changed or deleted. Needs admin or manager rights.

Report, 2 operations

filter_reportsFilter reportsGETReturns the individual time entries that match report filters (users, projects, clients, tags, teams, states, billed status) over a date range, with their cost and profit fields. For aggregated totals per client and project use get_report_totals.
get_report_totalsGet report totalsGETRetrieve report totals grouped by clients and projects. This endpoint provides aggregated time tracking data including durations, costs, and billing information.

Timer, 2 operations

start_timerStart timerPUTStarts the timer on an existing time entry (create one with create_time_entry first) and returns the entry.
stop_timerStop timerPUTStops the running timer on a time entry and returns the entry with its updated duration.

Avatar, 1 operation

remove_user_avatarRemove user avatarDELETERemove the user's avatar so the Gravatar fallback is shown. Requires update permission for the user.

Compliance, 1 operation

list_user_complianceList user complianceGETReturns per-user time-tracking compliance metrics for a configurable date window.

Insight, 1 operation

get_insightsGet insightsGETBillable utilisation against a target, the billable/non-billable split and where time went (by tag and project), in MINUTES, for view mine, team or organisation. If timed_out is true every figure is meaningless.

Insights settings, 1 operation

update_insights_settingsUpdate insights settingsPUTAdmin only. Changes the Insights page for everyone on the account: naming individuals, the headline metric and target, and the smallest team shown. Send only the settings to change, at least one.

Role, 1 operation

list_rolesList rolesGETRetrieve all roles available in the account. Roles define permissions and access levels for users, including admin, manager, employee, and team lead roles.

Timesheet reminder, 1 operation

send_timesheet_remindersSend timesheet remindersPOSTSends the given users a reminder to complete their timesheets (a notification to each person). Needs the User Notify permission or to lead teams containing every recipient.

Use Timely from Claude Code, Cursor or Codex

Connect Timely in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Timely operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Timely

Create your workspace
Sign up free. Nothing to install.
Connect Timely once
Add your Timely connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.