Toggl Track ACTION
Get Project Task Time Summary
Get how much time was tracked on each task of one Toggl Track project over a date range, with task names, plus the time tracked on the project without a task. Use it when a user asks how much time each task of a project took, e.g. "how long did each task on Website Redesign take last week?". Use List Workspace Projects first to get the project ID. For per-user or per-project totals use Get Time Entry Summary, and for the individual time entries use Search Detailed Time Entries; both accept a project filter. A date range is required: either a Date Preset (resolved in the connected user's Toggl timezone and first day of week) or both Start Date and End Date. Returns
dateRange, totalSeconds, tasks (each with taskId, taskName and seconds, most time first) and untaskedSeconds. Example: workspaceId=1234567, projectId=123456789, datePreset="last_week" → each task's tracked seconds for last week. 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 Get Project Task Time Summary 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-get-project-task-time-summary",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
toggl: { authProvisionId: "apn_xxxxxxx" },
workspaceId: 10,
projectId: 10,
},
})
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-get-project-task-time-summary",
"configured_props": {
"toggl": { "authProvisionId": "apn_xxxxxxx" },
"workspaceId": 10,
"projectId": 10
}
}'// 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-get-project-task-time-summary",
arguments: {
workspaceId: 10,
projectId: 10,
},
})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 |
projectId Project ID | integer | The Toggl Track project ID, e.g. 123456789. Use List Workspace Projects to find it (the id field). The project must belong to the given workspace. Required |
datePreset Date Preset | string | Optional report range resolved using the connected user's Toggl timezone and first day of week, e.g. last_month. For all-user reports, Toggl evaluates dates in each time entry creator's profile timezone. Optional |
startDate Start Date | string | Inclusive report start date in YYYY-MM-DD format, e.g. 2026-09-01. Required with End Date when Date Preset is not used. Optional |
endDate End Date | string | Inclusive report end date in YYYY-MM-DD format, e.g. 2026-09-30. It may be the same as Start Date. Optional |
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-get-project-task-time-summary
- Version
- 0.0.1
- App
- Toggl Track
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗