Toggl icon

Toggl

Interact with Toggl Track API
Join our community

Actions8

Overview

This node integrates with the Toggl Track API to manage projects within a specified workspace. Specifically, the "List Projects" operation retrieves a list of projects from a given workspace, optionally including archived projects. This is useful for users who want to automate project management tasks, synchronize project data with other tools, or generate reports based on their Toggl projects.

Practical examples:

  • Automatically fetch all active projects in a workspace to display in a dashboard.
  • Retrieve both active and archived projects for auditing or migration purposes.
  • Use the project list as input for further automation workflows, such as assigning time entries or generating invoices.

Properties

Name Meaning
Workspace ID ID of the workspace to list projects from (required).
Include Archived Whether to include archived projects in the results (true or false).

Output

The output is an array of JSON objects, each representing a project retrieved from the Toggl Track API. Each project object contains details such as project name, ID, client association, color, and status (active or archived).

The node does not output binary data.

Example output structure (simplified):

[
  {
    "id": 123456,
    "name": "Project Name",
    "client_id": 78910,
    "color": "#06aaf5",
    "archived": false,
    "workspace_id": 111213
  },
  ...
]

Dependencies

  • Requires an API key credential for authenticating with the Toggl Track API.
  • The node uses HTTP requests to interact with Toggl's REST API endpoints.
  • No additional environment variables are needed beyond the API authentication setup.

Troubleshooting

  • Common issues:

    • Invalid or missing workspace ID will cause the API request to fail.
    • Network connectivity problems can prevent successful API calls.
    • Insufficient permissions on the API key may result in authorization errors.

  • Error messages:

    • "Invalid JSON in body parameter" or "Invalid JSON in query parameters" — These do not apply directly to this operation but may appear if using raw requests; ensure JSON inputs are correctly formatted.
    • "No running time entry found" — Not relevant here but appears in other operations.
    • General API errors will be returned as error messages in the output if "Continue On Fail" is enabled.

  • Resolution tips:

    • Verify that the workspace ID is correct and accessible by the API key.
    • Check network connectivity and API service status.
    • Ensure the API key has the necessary scopes/permissions for reading projects.

Links and References

Discussion