Toggl icon

Toggl

Interact with Toggl Track API
Join our community

Actions8

Overview

This node integrates with the Toggl Track API to manage projects, time entries, clients, and raw API requests. Specifically, for the Create Project operation under the Project resource, it allows users to create a new project within a specified workspace in Toggl Track. This is useful for automating project setup workflows, organizing workspaces, or integrating Toggl project creation into larger automation pipelines.

Practical examples include:

  • Automatically creating a new project when a new client is onboarded.
  • Setting up projects programmatically based on external triggers or data sources.
  • Assigning projects to specific clients and customizing their appearance with colors.

Properties

Name Meaning
Project Name The name of the project to create.
Workspace ID The numeric ID of the workspace where the project will be created.
Client ID (Optional) The numeric ID of the client to assign the project to.
Color Hex color code representing the project's color in Toggl Track (e.g., #06aaf5).

Output

The output is a JSON object representing the newly created project as returned by the Toggl Track API. It typically includes details such as the project ID, name, color, client assignment, workspace association, and other metadata.

If multiple items are processed, each output item corresponds to one created project.

No binary data output is produced by this operation.

Dependencies

  • Requires an active Toggl Track API key credential configured in n8n.
  • The node uses the Toggl Track REST API endpoints for project management.
  • Network access to Toggl Track API endpoints is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing workspace ID: Ensure the workspace ID exists and is accessible with your API credentials.
    • Invalid client ID: If provided, the client ID must belong to the same workspace.
    • Incorrect color format: The color must be a valid hex code (e.g., #FFFFFF).
    • API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.

  • Error messages:

    • "Invalid JSON in body parameter": Not applicable here since the node builds the request body internally.
    • API errors from Toggl (e.g., 400 Bad Request, 401 Unauthorized): Check credentials and input parameters.
    • "No running time entry found": Not relevant for this operation but may appear if mixing operations.

To resolve errors, verify all required fields, ensure correct workspace and client IDs, and confirm API credentials.

Links and References

Discussion