Toggl icon

Toggl

Interact with Toggl Track API
Join our community

Actions8

Overview

This node integrates with the Toggl Track API to manage clients, projects, time entries, and raw API requests. Specifically, for the Create Client operation, it allows users to create a new client within a specified workspace in Toggl Track. This is useful for automating client management workflows, such as adding new clients when onboarding or syncing client data from other systems.

Practical examples:

  • Automatically creating a new client in Toggl when a new customer is added in a CRM.
  • Adding clients programmatically during project setup to ensure accurate time tracking attribution.

Properties

Name Meaning
Client Name The name of the client to create (required).
Workspace ID The numeric ID of the workspace where the client will be created (required).
External Reference An optional external reference identifier for the client, e.g., an ID from another system.
Notes Optional notes or comments about the client.

Output

The output JSON contains the newly created client object as returned by the Toggl Track API. This typically includes fields such as the client's ID, name, workspace ID, external reference, notes, and metadata related to creation.

Example output structure (simplified):

{
  "id": 123456,
  "name": "Client Name",
  "workspace_id": 7890,
  "external_reference": "optional-external-id",
  "notes": "Optional notes",
  "at": "2024-06-01T12:00:00Z"
}

No binary data 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; thus, internet access and valid authentication are necessary.
  • The user must have appropriate permissions in the specified workspace to create clients.

Troubleshooting

  • Common issues:

    • Invalid or missing workspace ID: Ensure the workspace ID exists and the API key has access to it.
    • Missing required parameters: The client name and workspace ID must be provided.
    • API authentication errors: Verify that the API key credential is correctly set up and valid.

  • Error messages:

    • "No running time entry found" — unrelated to client creation but may appear if other operations are used incorrectly.
    • "Invalid JSON in body parameter" or "Invalid JSON in query parameters" — relevant only for raw requests, not for client creation.
    • General API errors will be passed through; check the error message for details like permission denied or invalid input.

To resolve errors, verify all required inputs, confirm API credentials, and check workspace permissions.

Links and References

Discussion