Toggl Track is a time tracking software designed for businesses of all sizes. It can help you streamline your work processes by providing you with insights into your daily routine as an organization. Toggl Track syncs all your entries automatically across different platforms such as a web app, a mobile app, or a browser extension.
You can replicate data from your Toggl Track account to a database, data warehouse, or file storage system using Hevo Pipelines.
Prerequisites
-
An active Toggl Track account from which data is to be ingested exists.
-
You are logged in as an Admin user to obtain the API token. You can also log in as a Manager who has Admin privileges.
-
You are assigned the Team Administrator, Team Collaborator, or Pipeline Administrator role in Hevo to create the Pipeline.
Obtaining the Workspace ID
You require a workspace ID to authenticate Hevo on your Toggl Track account.
Note: You must log in as an Admin user or as a Manager with Admin privileges to perform these steps.
Perform the following steps to retrieve your Workspace ID:
-
Log in to your Toggl Track account.
-
In the left navigation pane, under the Manage section, click Projects .
-
To get your Workspace ID, go to the address bar of your browser. Copy the 7-digit number in the URL, and save it securely like any other password. For example, in this URL: https://track.toggl.com/projects/6620119/list, the Workspace ID is 6620119. Use this ID while configuring your Hevo Pipeline.
Configuring Toggl Track as a Source
Perform the following steps to configure Toggl Track as the Source in your Pipeline:
-
Click PIPELINES in the Navigation Bar.
-
Click + CREATE PIPELINE in the Pipelines List View.
-
In the Select Source Type page, select Toggl Track.
-
In the Configure your Toggl Track Source page, specify the following:
-
Pipeline Name: A unique name for the Pipeline, not exceeding 255 characters.
-
Username: The email address used to authorize the user in Toggl Track.
-
Password: The password associated with your Toggl Track account.
-
Workspace ID: The ID of the workspace you want to ingest data from.
-
-
Click TEST & CONTINUE.
-
Proceed to configuring the data ingestion and setting up the Destination.
Data Replication
| For Teams Created | Default Ingestion Frequency | Minimum Ingestion Frequency | Maximum Ingestion Frequency | Custom Frequency Range (in Hrs) |
|---|---|---|---|---|
| Before Release 2.21 | 1 Hr | 1 Hr | 24 Hrs | 1-24 |
| After Release 2.21 | 6 Hrs | 30 Mins | 24 Hrs | 1-24 |
Note: The custom frequency must be set in hours as an integer value. For example, 1, 2, or 3 but not 1.5 or 1.75.
-
Historical Data: In the first run of the Pipeline, Hevo ingests all the existing data for the selected objects from your Toggl Track account and loads it to the Destination.
-
Incremental Data: Once the historical load is complete, all new and updated records for the Projects, Tasks, and Time Entries objects are ingested as per the ingestion frequency. The remaining objects are ingested in Full Load mode.
Schema and Primary Keys
Hevo uses the following schema to upload the records in the Destination database:
Data Model
The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:
| Object | Description |
|---|---|
| Clients | Contains the list of individuals assigned to different projects. Clients can be linked to multiple projects, but each project must be linked to an individual client. |
| Groups | Contains the details of the groups into which your users can be organized. |
| Organizations | Contains the details of the organizations into which your workspaces are segregated. |
| Projects | Contains the details of the projects associated with your Toggl Track account. |
| Tags | Contains the details of all the tags used to organize your workspaces into multiple categories. |
| Tasks | Contains the details of all the tasks assigned to users. Tasks allow you to keep track of what a user needs to do related to a project. |
| Time Entries | Contains the details of the time entries submitted by users to record the time spent on their tasks. |
| Workspaces | Contains the list of projects and tasks that are associated with the workspace. |
| Workspace Users | Contains the details of all the users that are mapped to a specific workspace. |
Additional Information
Read the detailed Hevo documentation for the following related topics:
Source Considerations
-
Rate Limit: Toggl Track imposes a limit of one API call per second. If the limit is exceeded, Hevo defers the ingestion till the limits reset.
-
The API limitations of Toggle Track prevent Hevo from ingesting data older than 90 days.
Limitations
-
Hevo currently does not support deletes. Therefore, any data deleted in the Source may continue to exist in the Destination.
-
Hevo does not provide you with the option to select the historical sync duration for loading historical data. All the historical data in your Toggl Track account is loaded.
-
Hevo does not load an Event into the Destination table if its size exceeds 128 MB, which may lead to discrepancies between your Source and Destination data. To avoid such a scenario, ensure that each row in your Source objects contains less than 100 MB of data.
Revision History
Refer to the following table for the list of key updates made to this page:
| Date | Release | Description of Change |
|---|---|---|
| Jan-07-2025 | NA | Updated the Limitations section to add information on Event size. |
| Mar-05-2024 | 2.21 | Updated the ingestion frequency table in the Data Replication section. |
| Dec-08-2022 | NA | Updated section, Source Considerations to mention about ingesting data older than 90 days. |
| Sep-21-2022 | 1.98 | New document. |