Toggl 2.0 connector for AI agents

Tools your work management agent reaches for on Toggl 2.0, scoped per user.

CALL ANY TOOL

67 tools for work management in Toggl 2.0: tasks, subtasks, statuses, milestones, projects, clients, and tags, live timers and time entries, timesheets, goals, and time off.

togglfocus_add_project_members

Add project members

Add users and teams to a project with a given role. Returns no content on success (HTTP 204). Use to grant access to a project. Use togglfocus_remove_project_member to revoke it. Needs organization_id and workspace_id. togglfocus_get_user_settings returns current_workspace_id (and mcp_active_organization_id when set). role_id comes from togglfocus_list_organization_roles.

Parameters

Name

Type

Required

Description

organization_id

integer

Required

Numeric ID of the Toggl 2.0 organization that owns the workspace. Example: 1234567

project_id

integer

Required

Numeric ID of the project. Find it with togglfocus_list_projects. Example: 1234567

role_id

integer

Required

Numeric ID of the project role granted to the added users and teams. Find it with togglfocus_list_organization_roles. Example: 1234567

workspace_id

integer

Required

Numeric ID of the Toggl 2.0 workspace to operate in. Example: 1234567

group_ids

array

Optional

Numeric IDs of teams (user groups) to add to the project. Find them with togglfocus_list_organization_teams. Accepts a JSON array. Example: [123456, 234567]

user_ids

array

Optional

Numeric IDs of users to add to the project. Find them with togglfocus_list_organization_users. Accepts a JSON array. Example: [123456, 234567]

togglfocus_archive_project

Archive project

togglfocus_create_client

Create client

togglfocus_create_project

Create project

Create a project in a workspace. Returns the created project with its id. Use to add a project before creating tasks in it. Use togglfocus_update_project to change an existing one. Needs organization_id and workspace_id. togglfocus_get_user_settings returns current_workspace_id (and mcp_active_organization_id when set).

Parameters

Name

Type

Required

Description

name

string

Required

Name of the project. Example: Website redesign

organization_id

integer

Required

Numeric ID of the Toggl 2.0 organization that owns the workspace. Example: 1234567

workspace_id

integer

Required

Numeric ID of the Toggl 2.0 workspace to operate in. Example: 1234567

auto_compute_estimates

boolean

Optional

When true, the project's estimate is computed automatically as the sum of its task estimates. Off by default. Example: true

billable

boolean

Optional

Whether the time or work is billable. Send true or false; leave empty to keep the default inherited from the task or project. Example: true

client_id

integer

Optional

Numeric ID of the client the project belongs to. Find it with togglfocus_list_clients. Example: 1234567

color

string

Optional

Project color as a hex code, for example #06aaf5. Example: #06aaf5

completion_mode

string

Optional

How the project is marked complete: manual (a person marks it) or automatic (it completes when its work is done). Allowed values: manual, automatic. Example: manual. One of: `manual`, `automatic`.

description

string

Optional

Free-text description of the project. Example: Prepare Q4 planning

draft

boolean

Optional

When true, the project is created or kept as a draft, which is hidden from listings unless drafts are requested. Example: true

end_date

string

Optional

Project end date, formatted YYYY-MM-DD. Example: 2026-09-01

estimate_source

string

Optional

Where the project estimate comes from: manual (estimated_mins on the project) or tasks (sum of task estimates). Allowed values: manual, tasks. Example: manual. One of: `manual`, `tasks`.

estimated_mins

integer

Optional

Project estimate in minutes, for example 4800. Used when estimate_source is manual. Example: 3600

parent_project_id

integer

Optional

Numeric ID of the parent project, to create a sub-project. Example: 1234567

pinned

boolean

Optional

When true, pins the item for the current user. Example: true

private

boolean

Optional

When true, only invited people can see the item. When omitted, it inherits the parent's visibility or the workspace default. Example: true

start_date

string

Optional

Project start date, formatted YYYY-MM-DD. Example: 2026-09-01

tag_ids

array

Optional

Numeric IDs of tags to apply to the project. Find them with togglfocus_list_tags. Accepts a JSON array. Example: [123456, 234567]

togglfocus_create_tag

Create tag

togglfocus_create_task_time_entry

Create task time entry

Create a logged or planned time entry on a task. Returns the created time entry with its id. Use to log or plan time against a known task. Use togglfocus_create_time_entry for time without a task. Needs organization_id and workspace_id. togglfocus_get_user_settings returns current_workspace_id (and mcp_active_organization_id when set).

Parameters

Name

Type

Required

Description

organization_id

integer

Required

Numeric ID of the Toggl 2.0 organization that owns the workspace. Example: 1234567

task_id

integer

Required

Numeric ID of the task. Find it with togglfocus_list_tasks. Example: 1234567

type

string

Required

Kind of entry: activity (work) or break. Allowed values: activity, break. Example: activity. One of: `activity`, `break`.

workspace_id

integer

Required

Numeric ID of the Toggl 2.0 workspace to operate in. Example: 1234567

billable

boolean

Optional

Whether the time or work is billable. Send true or false; leave empty to keep the default inherited from the task or project. Example: true

description

string

Optional

What the time was spent on. Example: Prepare Q4 planning

duration

integer

Optional

Tracked length in seconds, for logged time. For example 3600 for one hour. Example: 3600

planned_at

string

Optional

Timestamp (RFC 3339) of the planned slot, for planned time. Leave empty for logged time. Example: 2026-09-01T09:00:00Z

planned_duration

integer

Optional

Planned length in seconds, for planned time. For example 3600 for one hour. Example: 3600

planned_start

string

Optional

Start of the planned slot (RFC 3339), for time planned on the calendar. Example: 2026-09-01T09:00:00Z

project_id

integer

Optional

Numeric ID of the project, overriding the task's project. Find it with togglfocus_list_projects. Example: 1234567

start

string

Optional

Start of the tracked time (RFC 3339), for logged time. Leave empty for planned-only entries. Example: 2026-09-01T09:00:00Z

tag_ids

array

Optional

Numeric IDs of tags to apply to the entry. Find them with togglfocus_list_tags. Accepts a JSON array. Example: [123456, 234567]

tracked_at

string

Optional

Timestamp (RFC 3339) the time was tracked at. Usually left empty so the server sets it. Example: 2026-09-01T09:00:00Z

user_id

integer

Optional

Numeric ID of the user the entry is for. Omit to use the authenticated user; other users need the manage_time_entries permission. Example: 1234567

togglfocus_delete_client

Delete client

togglfocus_delete_project

Delete project

togglfocus_delete_tag

Delete tag

togglfocus_get_client

Get client

togglfocus_get_milestone

Get milestone

togglfocus_get_status

Get status

togglfocus_get_task

Get task

togglfocus_get_time_entry

Get time entry

togglfocus_list_clients

List clients

togglfocus_list_milestones

List milestones

togglfocus_list_organization_teams

List organization teams

togglfocus_list_projects

List projects

List projects in a workspace, with filters for name, client, tags, archived, completed and date range. Returns data (array of projects) plus page, per_page, total and task counts. Use to browse or find a project id. Use togglfocus_get_project for one project. Needs organization_id and workspace_id. togglfocus_get_user_settings returns current_workspace_id (and mcp_active_organization_id when set).

Parameters

Name

Type

Required

Description

organization_id

integer

Required

Numeric ID of the Toggl 2.0 organization that owns the workspace. Example: 1234567

workspace_id

integer

Required

Numeric ID of the Toggl 2.0 workspace to operate in. Example: 1234567

archived

boolean

Optional

Filter by archived state (true = archived only, false = active only, omit = active only, empty = all projects). Example: true

assignee_user_id

array

Optional

Filter by assignee user IDs; pass empty value (?assignee_user_id=) to include projects without user assignees. Accepts a JSON array. Example: [123456, 234567]

client_id

array

Optional

Filter by client IDs. Accepts a JSON array. Example: [123456, 234567]

completed

boolean

Optional

Filter by completion state (true = completed only, false = non-completed only, empty = all projects, omit = non-completed only, or all projects when archived=true). Example: true

creator_id

array

Optional

Filter by project creator id. Accepts a JSON array. Example: [123456, 234567]

end_date

string

Optional

Filter projects overlapping date range (end). Used with start_date to find projects where project.start_date <= end_date AND project.end_date >= start_date. Format: YYYY-MM-DD. Example: 2026-09-01

include_drafts

boolean

Optional

Include draft projects in the response (default false hides them; requires view_draft_projects permission). Example: true

include_rates

boolean

Optional

Includes the projects' rate data. Example: true

member_only

boolean

Optional

Only projects where the caller has an active project role, directly or through a team; normal visibility and lifecycle filters still apply. Example: true

name

string

Optional

Filter by project name or client name. Example: Website redesign

order_by

array

Optional

Order by. Also accepts cf_<id> / -cf_<id> to sort by any active workspace custom field. Multi_select and users CF types sort by their canonicalized (sorted) value array, so projects sharing the same set cluster together. Accepts a JSON array. Example: ["value"]

page

integer

Optional

Page number. Example: 1

per_page

integer

Optional

Results per page. Example: 50

pinned

boolean

Optional

Filter by only pinned tasks. Example: true

private

boolean

Optional

Filter by project privacy (true for private, false for public). Example: true

project_id

array

Optional

Filter by project IDs. Accepts a JSON array. Example: [123456, 234567]

start_date

string

Optional

Filter projects overlapping date range (start). Used with end_date to find projects where project.start_date <= end_date AND project.end_date >= start_date. Format: YYYY-MM-DD. Example: 2026-09-01

tag_id

array

Optional

Filter by tag IDs. Accepts a JSON array. Example: [123456, 234567]

user_id

array

Optional

Return only projects accessible by the given users (requires manage workspace users when inspecting another user). Incompatible with only_me. Accepts a JSON array. Example: [123456, 234567]

togglfocus_list_subtasks

List subtasks

togglfocus_list_tasks

List tasks

List tasks in a workspace, with filters for project, assignee, state, status, tags, dates and name. Returns data (array of tasks) plus page, per_page and total. Use to browse or find a task id. Use togglfocus_get_task for one task. Needs organization_id and workspace_id. togglfocus_get_user_settings returns current_workspace_id (and mcp_active_organization_id when set).

Parameters

Name

Type

Required

Description

organization_id

integer

Required

Numeric ID of the Toggl 2.0 organization that owns the workspace. Example: 1234567

workspace_id

integer

Required

Numeric ID of the Toggl 2.0 workspace to operate in. Example: 1234567

archived

boolean

Optional

Filter in/out archived tasks. Example: true

assignee_team_id

array

Optional

Filter in tasks assigned to these teams, without expanding the teams to their members. Accepts a JSON array. Example: [123456, 234567]

assignee_user_id

array

Optional

Filter in tasks by assignee's user IDs. Accepts a JSON array. Example: [123456, 234567]

client_id

array

Optional

Filter by client ids. `?client_id=` will include tasks with no client. Accepts a JSON array. Example: [123456, 234567]

end_date

string

Optional

Filter tasks overlapping date range (end). Used with start_date to find tasks where task.start_date <= end_date AND task.end_date >= start_date. Format: YYYY-MM-DD. Example: 2026-09-01

estimated_mins_max

integer

Optional

Filter by estimated mins max. Example: 1234567

estimated_mins_min

integer

Optional

Filter by estimated mins min. Example: 1234567

has_time_entries

boolean

Optional

Filter tasks if it has time entries. Example: true

include_assignees

boolean

Optional

Includes the unified user and team assignees. Example: true

name

string

Optional

Filter tasks by task name, project name, or client name. Example: Website redesign

order_by

array

Optional

Order by. tag_ids and assignees order by the canonicalized (sorted) array, so tasks with the same set of tags or assignees cluster together regardless of storage order. Also accepts pcf_<id> / -pcf_<id> to sort tasks by the named custom field on the task's parent project, and cf_<id> / -cf_<id> to sort by the task's own custom field. Multi_select and users CF types use the same canonicalized-array semantics. sub_tasks_grouped orders top-level tasks by name (direction applies) with each task's subtasks directly after it in position order; it cannot be combined with other order_by values. Accepts a JSON array. Example: ["value"]

page

integer

Optional

Page number. Example: 1

parent_task_id

array

Optional

Filter by parent task ids. `?parent_task_id=` will include tasks with no parent. Accepts a JSON array. Example: [123456, 234567]

per_page

integer

Optional

Results per page. Example: 50

pinned

boolean

Optional

Filter by pinned state. Example: true

priority

array

Optional

Filter by priority. Accepts a JSON array. Example: ["value"]

private

boolean

Optional

Filter tasks by private state. Example: true

project_id

array

Optional

Filter by project ids. `?project_id=` will include tasks with no project. Accepts a JSON array. Example: [123456, 234567]

source

array

Optional

Filter by sources. Accepts a JSON array. Example: ["value"]

start_date

string

Optional

Filter tasks overlapping date range (start). Used with end_date to find tasks where task.start_date <= end_date AND task.end_date >= start_date. Format: YYYY-MM-DD. Example: 2026-09-01

state

array

Optional

Filter by state. Accepts a JSON array. Example: ["value"]

status_id

array

Optional

Filter in tasks by status' IDs. Accepts a JSON array. Example: [123456, 234567]

tag_id

array

Optional

Filter in tasks by tag IDs. Accepts a JSON array. Example: [123456, 234567]

togglfocus_list_timeoff_entries

List timeoff entries

togglfocus_log_planned_time_entry

Log planned time entry

togglfocus_remove_project_member

Remove project member

togglfocus_search

togglfocus_start_tracking

Start tracking

togglfocus_stop_tracking

Stop tracking

togglfocus_unarchive_project

Unarchive project

togglfocus_update_client

Update client

togglfocus_update_project

Update project

Update fields of an existing project; only the fields you send change. Returns no content on success (HTTP 204). Use to rename, recolor, reschedule or re-assign a project. Use togglfocus_archive_project to archive it. Needs organization_id and workspace_id. togglfocus_get_user_settings returns current_workspace_id (and mcp_active_organization_id when set).

Parameters

Name

Type

Required

Description

organization_id

integer

Required

Numeric ID of the Toggl 2.0 organization that owns the workspace. Example: 1234567

project_id

integer

Required

Numeric ID of the project. Find it with togglfocus_list_projects. Example: 1234567

workspace_id

integer

Required

Numeric ID of the Toggl 2.0 workspace to operate in. Example: 1234567

auto_compute_estimates

boolean

Optional

When true, the project's estimate is computed automatically as the sum of its task estimates. Off by default. Example: true

billable

boolean

Optional

Whether the time or work is billable. Send true or false; leave empty to keep the default inherited from the task or project. Example: true

client_id

integer

Optional

Numeric ID of the client the project belongs to. Find it with togglfocus_list_clients. Example: 1234567

color

string

Optional

Project color as a hex code, for example #06aaf5. Example: #06aaf5

completion_mode

string

Optional

How the project is marked complete: manual (a person marks it) or automatic (it completes when its work is done). Allowed values: manual, automatic. Example: manual. One of: `manual`, `automatic`.

description

string

Optional

Free-text description of the project. Example: Prepare Q4 planning

draft

boolean

Optional

When true, the project is created or kept as a draft, which is hidden from listings unless drafts are requested. Example: true

end_date

string

Optional

Project end date, formatted YYYY-MM-DD. Example: 2026-09-01

estimate_source

string

Optional

Where the project estimate comes from: manual (estimated_mins on the project) or tasks (sum of task estimates). Allowed values: manual, tasks. Example: manual. One of: `manual`, `tasks`.

estimated_mins

integer

Optional

Project estimate in minutes, for example 4800. Used when estimate_source is manual. Example: 3600

name

string

Optional

Name of the project. Example: Website redesign

parent_project_id

integer

Optional

Numeric ID of the parent project, to create a sub-project. Example: 1234567

pinned

boolean

Optional

When true, pins the item for the current user. Example: true

private

boolean

Optional

When true, only invited people can see the item. When omitted, it inherits the parent's visibility or the workspace default. Example: true

start_date

string

Optional

Project start date, formatted YYYY-MM-DD. Example: 2026-09-01

tag_ids

array

Optional

Numeric IDs of tags to apply to the project. Find them with togglfocus_list_tags. Accepts a JSON array. Example: [123456, 234567]

togglfocus_update_tag

Update tag

For more tools, view docs.

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Toggl 2.0 tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["togglfocus"], toolNames: [
    "togglfocus_list_tasks",
    "togglfocus_start_tracking",
    "togglfocus_stop_tracking"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Start tracking time on the Draft Q4 report task" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["togglfocus"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Start tracking time on the Draft Q4 report task" }],
  tools,
});

// Execute the tool call with the user's vaulted Toggl 2.0 access token
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["togglfocus"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Start tracking time on the Draft Q4 report task" }],
  tools,
});

// Tool call runs with the user's vaulted Toggl 2.0 access token
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["togglfocus"] }, pageSize: 100,
});

const agent = new Agent({
  name: "work_agent",
  model: "gemini-2.5-pro",
  instruction: "Toggl 2.0 tools scoped to this user",
  tools,
});

await agent.run("Start tracking time on the Draft Q4 report task");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Toggl 2.0 tool. Click to copy, paste into your agent, done.

Tasks

Copy the prompt

Copied

Create a task called Draft Q4 report in the Planning project assigned to me.

Copy the prompt

Copied

List my open tasks due this week.

Copy the prompt

Copied

Create a milestone for the beta launch due November 30.

Time

Copy the prompt

Copied

Start tracking time on the Draft Q4 report task.

Copy the prompt

Copied

Stop my running timer.

Copy the prompt

Copied

Log 90 minutes on the Client onboarding task for yesterday afternoon.

Team

Copy the prompt

Copied

Who is out this week?

Copy the prompt

Copied

Show the time accounting report for October.

Copy the prompt

Copied

List the timesheets for last week.

SEE HOW AUTH WORKS

Each user connects their own Toggl 2.0 access token once, and Scalekit sends it with every call. Access tokens stay vaulted, every call is scope checked, and every action is logged.

Authorize

Your user connects

Toggl 2.0

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Toggl 2.0

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Toggl 2.0

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Toggl 2.0

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other time tracking and project management connectors.

Engineering Teams

Engineering standup agent

Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.

Engineering Teams

Slack triage

Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Toggl 2.0 access token looks fine in a demo. In production every timer and task update looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Toggl 2.0 today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Toggl 2.0 as the user or through a shared token?

As the user. Each user connects their own Toggl 2.0 access token once, and Scalekit sends it with every call. Timers, tasks, and time entries the agent creates are attributed to that user in your audit trail, not a shared service account.

Where is the Toggl 2.0 access token stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new access token. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in Toggl 2.0?

Yes. Filter by tool name in listScopedTools to expose only what you want, for example the list and timer tools without togglfocus_delete_task or togglfocus_delete_project. The archive tools hide items without deleting them. Scalekit also enforces scope checks before every API call.

What happens when a user revokes Toggl 2.0 access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent start a timer from a plain task name?

Yes. togglfocus_start_tracking_from_description resolves a task from a name, project name, and tags, creating it if needed, then starts a timer or logs a completed entry. togglfocus_start_tracking starts a timer when the agent already has the task or project ID.