Fix the timer, safely.

Unofficial integration

Timer for Toggl Track is operated by Brian Semrau. It is an unofficial third-party integration and is not affiliated with or endorsed by Toggl, CORSAIR, or Elgato.

Contact the operator through the support method on the Marketplace or distribution listing. There is no separate email address published here.

Start with polling

1. Confirm a compatible version of iCUE is running and the XENEON EDGE appears in iCUE.
2. Import the widget from the iCUE Widgets panel and add it to the XENEON EDGE.
3. On the physical widget, select Set up token and enter the API token from the bottom of the Toggl Track Profile page. Read the hosted-service disclosure before saving. The token is encrypted locally; one-time key registration requires the service to be online.
4. Leave Webhook updates off initially and select a safety refresh of 10, 15, or 30 minutes. The default is 10 minutes.
5. Select Refresh. After polling works, optionally enable Webhook updates.

If Toggl rejects the token, copy the current token from the Toggl Profile page and select Change token on the widget. If the old encrypted token is missing, a replacement token for the same Toggl user can recover the installation. When Webhook updates are enabled, the new token must also be able to confirm the widget's exact existing Toggl webhooks. To switch to a different Toggl account, disable Webhook updates with the old token first. If encryption is unavailable in the iCUE runtime, setup stops without saving the token; contact support rather than using a plaintext setting.

Start, Refresh, and Stop

Start begins a timer immediately in your Toggl default workspace and then opens its editor. Canceling the editor leaves it running. If Start was not confirmed, wait briefly and Refresh before trying again.

Refresh asks the hosted service for the authoritative current timer. Use it after a network interruption, a change made in another Toggl client, or a message that the displayed state may be stale.

Stop stops only the running entry shown by the widget. If Toggl reports that the entry changed elsewhere, refresh before retrying. The elapsed display advances locally; it does not generate a network request every second.

Change the current entry or its times

1. Tap the running entry name or project/client line.
2. Change the description or billable setting. Search for and select a project, or choose No project to clear it.
3. Select Save changes. The widget updates only the current running entry.

If the timer changes or stops in another Toggl client while the editor is open, the widget replaces the editor title with the conflict message, disables Save, and preserves your unsaved changes. Review the refreshed timer, then reopen the editor if the change is still appropriate.

Tap elapsed time to edit the running entry's start time or set an end time. The fields use your device's local time zone; setting an end time stops that entry. Previously completed entries cannot be edited here. Invalid, future, and ambiguous daylight-saving times are rejected.

Optional and not instantaneous

Polling is the default. Webhook updates are optional and off by default. Enabling the setting asks the service to create installation-owned webhook subscriptions; disabling it asks the service to remove and confirm them.

Webhook delivery may be delayed, interrupted, or limited by Toggl permissions or quota. Safety polling continues in every mode. Use Refresh to reconcile immediately when the latest state is uncertain.

If setup or cleanup remains pending, restore the required Toggl permission or quota and retry. Do not remove the widget during uncertain cleanup: the hosted service retains the minimum encrypted retry material so it can confirm remote deletion safely.

If Toggl's enabled-webhook limit blocks setup and old widget-owned subscriptions are confirmed, a dialog asks whether to remove only those old Toggl webhooks and retry. Not now leaves them untouched and safety polling active. This does not erase another installation's hosted records. If recognition fails, inspect Toggl Track → Integrations → Webhooks manually. Refresh retries degraded setup without deleting webhooks automatically.

Check your plan's limits

Toggl's plan-dependent API and webhook limits can affect this widget. If Webhook updates show Degraded or cannot be enabled, check how many webhooks already exist in Toggl Track → Integrations → Webhooks; a previous installation may still occupy a slot. If timer reads, project search, or edits fail after frequent requests from this or other Toggl integrations, you may have reached an API request limit.

Check Toggl's current API and webhook limits for your plan. Wait for Toggl's limit to reset or reduce other integration traffic, then use Refresh. Changing the widget's safety-refresh interval may reduce its requests; enabling webhooks does not bypass API limits. Do not repeatedly retry while Toggl is limiting requests.

Use the confirmation carefully

If the result is uncertain or cleanup cannot be confirmed, the widget keeps the session and the service keeps the minimum retry material. Restore connectivity or permissions and retry Delete data. Do not treat an error as a successful deletion.

After confirmed deletion, the widget clears its local installation session and encrypted token. If you used an older version with a native iCUE token setting, remove that old configuration separately. Delete data does not delete Toggl time entries.

What is safe to share

When requesting help through the Marketplace or distribution listing, it is safe to share:

• widget version and iCUE version;
• the displayed status or safe error category;
• the approximate time of the failure;
• a non-secret request ID shown with an error;
• whether polling or Webhook updates were selected; and
• whether the problem affected Start, Refresh, entry/time editing, Stop, webhook recovery, or Delete data.

Read the privacy notice for the complete data flow and the terms for license and service boundaries.