Toggl Track
Turn requests and orders into Toggl Track work, and keep status in step across your tools.
18 ways to read, 11 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Toggl Track, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create clientApproval by rule
- Create projectApproval by rule
- Detailed reportRead
Example flow
- Toggl Track · Detailed reportDone
- Toggl Track · Create clientNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Toggl Track.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Toggl Track
- Toggl Track's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Read and write Toggl Track projects, clients, tasks, tags and time entries; read workspaces, members and groups, and run summary and detailed reports.
Toggl OÜ API docs- Source actions
- 18
- Destination actions
- 11
- Data types
- 14
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Clients4
- Create clientDestinationNot retried automaticallyApproval before production
Creates a client in the configured workspace.
- Get clientSource
One workspace client.
- List clientsSource
Workspace clients.
- Update clientDestinationProvider duplicate protectionApproval before production
Updates a client's name, notes or external reference.
Current time entry1
- Get running time entrySource
The token owner's running timer, if any.
Detailed report1
- Detailed reportSource
Reports API v3 detailed report: every time entry in the workspace for a date range, for all users the token can see.
Groups1
- List workspace groupsSource
User groups of the configured workspace with their members.
Me1
- Get current userSource
The token owner with default workspace and time zone.
Project users1
- List project membersSource
Project memberships with manager flag and member rates.
Projects4
- Create projectDestinationNot retried automaticallyApproval before production
Creates a project in the configured workspace.
- Get projectSource
One workspace project.
- List projectsSourceIncremental
Workspace projects, active and archived by default.
- Update projectDestinationProvider duplicate protectionApproval before production
Updates supplied project fields.
Running time entries1
- Stop running timerDestinationProvider duplicate protectionApproval before production
Stops a running time entry at the current time.
Summary report1
- Summary reportSource
Reports API v3 summary for the workspace: tracked seconds per group and sub-group (for example per project and user).
Tags3
- Create tagDestinationNot retried automaticallyApproval before production
Creates a workspace tag.
- List tagsSource
Workspace tags.
- Rename tagDestinationProvider duplicate protectionApproval before production
Renames a workspace tag.
Tasks4
- Create taskDestinationNot retried automaticallyApproval before production
Creates a task in a project.
- Get taskSource
One project task.
- List tasksSourceIncremental
Project tasks across the workspace (paid plans).
- Update taskDestinationProvider duplicate protectionApproval before production
Updates supplied task fields.
Time entries4
- Create time entryDestinationNot retried automaticallyApproval before production
Creates a time entry in the configured workspace.
- Get my time entrySource
One of the token owner's time entries by ID.
- List my time entriesSourceIncremental
The token owner's time entries, by start date range or modified since a timestamp.
- Update time entryDestinationProvider duplicate protectionApproval before production
Updates supplied fields on a time entry.
Users1
- List workspace usersSource
Members of the configured workspace.
Workspaces2
- Get workspaceSource
The configured workspace with its plan, rounding and rate defaults.
- List workspacesSource
Workspaces the token owner belongs to.
Access and limits
- 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).
- Pagination
- page and per_page (up to 200) for projects, tasks and tags; time entries are date-bounded; detailed reports use X-Next-ID and X-Next-Row-Number headers.
- Provider events
- Toggl Track Webhooks API with HMAC-signed event subscriptions. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
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 uses the Reports API v3 on the same host (api.track.toggl.com/reports/api/v3). Its response bodies are not fully documented: detailed report rows are flattened to one record per time entry, and summary groups to one record per sub-group, following the published request schema and observed shapes.
- Detailed reports page with the X-Next-ID and X-Next-Row-Number headers (50 rows per page by default) and are limited by Nexra to one-year ranges.
- Report exports (PDF, CSV, XLSX), saved reports, rates, approvals and alerts are not implemented.
- Deleting projects, clients, tasks, tags or time entries and archiving clients are intentionally excluded. Workspace API tokens and calendar URLs are never returned.
- 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.
Developer reference
- Create the Toggl OÜ credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Toggl Track, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/toggl-track and the Connections API.