Toggl icon

Toggl

Interact with Toggl Track API
Join our community

Actions8

Overview

This node allows users to interact with the Toggl Track API, specifically supporting a "Raw Request" operation that lets you make arbitrary HTTP requests to any Toggl API endpoint. This is useful when you want to perform actions or retrieve data not covered by predefined operations in the node.

Typical use cases include:

  • Accessing new or less common Toggl API endpoints without waiting for node updates.
  • Performing custom queries or commands by specifying HTTP method, endpoint, query parameters, and request body manually.
  • Quickly testing Toggl API calls within an n8n workflow.

For example, you could send a GET request to /me to retrieve your user profile or POST to /workspaces/{workspace_id}/projects to create a project with custom parameters.

Properties

Name Meaning
HTTP Method The HTTP method to use for the request. Options: GET, POST, PUT, DELETE
Endpoint The API endpoint path to call (e.g., /me, /workspaces, /time_entries). Required.
Body JSON object representing the request body. Only used for POST and PUT methods.
Query Parameters JSON object representing query parameters to append to the URL.

Output

The node outputs the raw JSON response from the Toggl API call under the json property of each item.

  • If the API returns an array, each element is output as a separate item.
  • If the API returns a single object, it is output as one item.
  • No binary data output is produced by this operation.

Dependencies

  • Requires an active Toggl API credential configured in n8n to authenticate requests.
  • Uses the Toggl Track API base URL implicitly via helper functions.
  • The node depends on correct JSON formatting for the "Body" and "Query Parameters" inputs.

Troubleshooting

  • Invalid JSON in body parameter: If the "Body" input contains malformed JSON, the node will throw an error. Ensure the JSON syntax is correct.
  • Invalid JSON in query parameters: Similarly, malformed JSON in "Query Parameters" will cause an error.
  • No running time entry found: Not applicable here but seen in other operations; ensure the requested resource exists.
  • HTTP errors from Toggl API: Check that the endpoint and method are correct and that your API credentials have sufficient permissions.
  • Empty or missing endpoint: The "Endpoint" property is required; leaving it empty will cause an error.

Links and References

Discussion