# Toggl Track setup for PopMCP

You paste one value into PopMCP: the API token at the bottom of your Toggl Track profile. PopMCP then lists the workspaces it reaches and you pick the one this connection is for.

- Auth: API credentials
- Setup time: 1 min
- API base URL: https://api.track.toggl.com/api/v9
- Credentials screen: https://track.toggl.com/profile
- Provider docs: https://engineering.toggl.com/docs/track/authentication/

## Before you begin

- A Toggl Track account, on any plan including the free one
- No OAuth app, redirect URL or review is needed: the token is the whole setup
- This guide is for Toggl Track at track.toggl.com. The newer Toggl 2.0 app has separate accounts and keys, and its keys do not work here

## Get your credentials

### 1. Sign in to Toggl Track

Open [track.toggl.com](https://track.toggl.com) and sign in with the account the AI should work as. The token carries your own permissions, so use an admin's account if the AI should manage members, workspace settings or billing.

Screen: https://track.toggl.com/timer

### 2. Open your profile

Click your profile icon in the lower left corner of Toggl Track and open your profile. The link above goes straight there.

Screen: https://track.toggl.com/profile

### 3. Copy your API token

Scroll to the bottom of the page to API Token. Reveal it and copy the whole token, one long string of letters and digits. Do not reset it unless you mean to: resetting stops everything that uses the old token.

Screen: https://track.toggl.com/profile

### 4. Paste the token into PopMCP and pick the workspace

In PopMCP, paste the token into API token and connect. PopMCP checks it, then lists every workspace it reaches. Choose the workspace for this connection; to connect another one too, put it in a PopMCP workspace of its own.

## Fields PopMCP asks for

- API token (apiToken) [required]: In Toggl Track open your Profile and scroll to the bottom. Click to reveal the API Token and copy it. Stored encrypted and used only on our servers.

## Verify

PopMCP marks the Toggl Track connection Verified with the workspace's name. Asking the AI what timer is running, or how many hours were tracked last week by project, returns them from that workspace.

## Troubleshooting

### "Toggl Track did not accept this API token. Copy it again from the bottom of your Toggl Track Profile page. If you reset it there, the old one stopped working."

Cause: The token was copied only in part, or it was reset on the profile page.

Fix: Open your profile, copy the whole token again and paste it.

### "That is a Toggl 2.0 key. This connector is for Toggl Track: copy the API token from the bottom of your Toggl Track Profile page."

Cause: A key starting toggl_sk_ belongs to the separate Toggl 2.0 app.

Fix: Sign in at track.toggl.com and copy the API token from your profile there.

### "Toggl Track's hourly request limit for your account has been reached."

Cause: This account has used its requests for the hour, often through another integration using the same token.

Fix: Try again once the hour's count clears. A higher Toggl plan raises the limit.

### "This API token no longer reaches the workspace chosen for this connection."

Cause: You were removed from the workspace, or it was deleted.

Fix: Check your membership in Toggl Track, then connect again and pick a workspace you can reach.

### The AI says a request was refused because of the plan, with status 402

Cause: Toggl uses 402 both for a used-up hourly limit and for a feature your plan does not include.

Fix: Ask the AI to check the API quota. If there is room left, the feature needs a higher Toggl plan.

### Member, workspace or billing changes are refused with status 403

Cause: These need a workspace or organization admin, and the token belongs to a member.

Fix: Have an admin make the change, or connect with an admin's token.

---

Source: https://www.docs.popmcp.com/docs/integrations/toggl-track/