Toggl Track
Read and write Toggl Track projects, clients, tasks, tags and time entries in a workspace.
Feed tracked time into billing, payroll and project reporting without manual exports.
Source actions
8
Destination actions
10
Data types
8
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
clients
- Create clientDestinationNot retried automatically
Creates a client in the configured workspace.
- List clientsSource
Workspace clients.
- Update clientDestinationDuplicate protected
Updates a client's name, notes or external reference.
me
- Get current userSource
The token owner with default workspace and time zone.
projects
- Create projectDestinationNot retried automatically
Creates a project in the configured workspace.
- List projectsSourceIncremental
Workspace projects, active and archived by default.
- Update projectDestinationDuplicate protected
Updates supplied project fields.
tags
- Create tagDestinationNot retried automatically
Creates a workspace tag.
- List tagsSource
Workspace tags.
- Rename tagDestinationDuplicate protected
Renames a workspace tag.
tasks
- Create taskDestinationNot retried automatically
Creates a task in a project.
- List tasksSourceIncremental
Project tasks across the workspace (paid plans).
- Update taskDestinationDuplicate protected
Updates supplied task fields.
time entries
- Create time entryDestinationNot retried automatically
Creates a time entry in the configured workspace.
- List my time entriesSourceIncremental
The token owner's time entries, by start date range or modified since a timestamp.
- Update time entryDestinationDuplicate protected
Updates supplied fields on a time entry.
users
- List workspace usersSource
Members of the configured workspace.
workspaces
- List workspacesSource
Workspaces the token owner belongs to.
Authentication
API token (HTTP Basic with the literal password api token)
Plans and access
All plans; hourly quota is 30 requests on Free, 240 on Starter and 600 on Premium per user per organisation. The API token acts as its user. Billable flags, rates and tasks require paid plans; managing projects and clients may require workspace admin rights.
Test environment
Use a free Toggl Track workspace for testing; Toggl has no separate sandbox.
Rate limits
Hourly per-user quota by plan (HTTP 402 when exhausted, see X-Toggl-Quota-Remaining) and a leaky bucket of about 1 request per second (HTTP 429).
Provider events
Toggl Track Webhooks API with HMAC-signed event subscriptions. Nexra event triggers are not yet available; flows run on demand or on a schedule.
Before you build a flow
- Time entries are read for the token owner only (/me/time_entries) and are not paginated; use a date range or since to keep each read under 2,000 entries.
- Workspace-wide time history needs the Reports API v3, whose response schema is not fully documented; it is not implemented.
- HTTP 402 means the hourly quota is exhausted or the feature needs a higher plan; Nexra reports it as a rejected request rather than waiting.
- Creates have no idempotency key; uncertain writes are not repeated automatically.