Toggl icon

Toggl

Interact with Toggl Track API

Actions8

Overview

This node integrates with the Toggl Track API to manage time tracking data. Specifically, the Start Time Entry operation allows users to start a new time entry in Toggl Track, which is useful for logging work periods automatically or manually from within an n8n workflow.

Common scenarios include:

  • Automatically starting a timer when a task begins.
  • Logging billable hours with descriptions and project associations.
  • Tagging time entries for categorization and reporting.

For example, a user can start a time entry with a description "Design meeting", assign it to a specific project by its ID, add relevant tags like "meeting,design", and specify the workspace where this time entry should be created.

Properties

Name Meaning
Description Text description of the time entry (e.g., "Client call", "Development work").
Project ID Numeric ID of the project to associate the time entry with.
Tags Comma-separated list of tags to categorize the time entry (e.g., "urgent,clientA").
Workspace ID Numeric ID of the workspace where the time entry will be created. This is required.

Output

The output JSON contains the newly created time entry object as returned by the Toggl Track API. This includes details such as:

  • id: Unique identifier of the time entry.
  • description: The description provided.
  • project_id: Associated project ID if specified.
  • tags: Array of tags assigned.
  • start: Timestamp when the time entry started.
  • duration: Duration of the time entry (initially set to -1 indicating running).
  • Other metadata fields related to the time entry.

No binary data is output by this operation.

Dependencies

  • Requires an active Toggl Track account.
  • Needs an API key credential configured in n8n for authenticating requests to the Toggl Track API.
  • The node uses the Toggl Track REST API endpoint /workspaces/{workspaceId}/time_entries to create the time entry.

Troubleshooting

  • Error: No running time entry found — This error occurs if attempting to stop a time entry but none is currently running. Ensure a time entry is started before stopping.
  • Invalid JSON in body parameter — When using raw requests, ensure JSON inputs are correctly formatted.
  • Missing required Workspace ID — The workspace ID must be provided; otherwise, the API request will fail.
  • Network or authentication errors may occur if the API key is invalid or missing.

To resolve issues:

  • Verify the API key credential is correctly set up.
  • Confirm workspace and project IDs exist and belong to your Toggl account.
  • Check that all required parameters are provided and valid.

Links and References

Discussion