Toggl Track ACTION
List Workspace Projects
List the projects in a Toggl Track workspace, optionally filtered by active status or a name fragment. Use it to find a project ID before calling List Project Tasks or Get Project Task Time Summary, or to answer "what projects do we have". To find a workspace ID, use List Workspace ID Options; this action does not return time entries or tracked hours (use Get Time Entry Summary or Search Detailed Time Entries with a project filter for those). Returns at most 1000 projects, each with
id plus the selected fields (default: name, client_id, active, billable, color, start_date, end_date, created_at). Example: workspaceId=1234567, name="Website", active="true" → matching projects with id, name, client_id, active, billable. See the documentation- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Toggl Track account once, then configure and run List Workspace Projects from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "toggl-list-workspace-projects",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
toggl: { authProvisionId: "apn_xxxxxxx" },
workspaceId: 10,
active: "Active",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "toggl-list-workspace-projects",
"configured_props": {
"toggl": { "authProvisionId": "apn_xxxxxxx" },
"workspaceId": 10,
"active": "Active"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "toggl",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "toggl-list-workspace-projects",
arguments: {
workspaceId: 10,
active: "Active",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
workspaceId Workspace ID | integer | The Toggl Track workspace ID, e.g. 1234567. Use List Workspace ID Options to find it (the value field). Required |
active Active | string | Which projects to list: true for active projects only, false for archived projects only, both for all, e.g. true. Required |
name Name | string | Optional case-insensitive name fragment to filter projects by, e.g. Website. Optional |
fields Fields | string[] | Project fields to return besides id, e.g. ["name", "client_id"]. Defaults to name, client_id, active, billable, color, start_date, end_date and created_at. Select All Fields for the complete rows. Required |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- toggl-list-workspace-projects
- Version
- 0.0.1
- App
- Toggl Track
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗