Can Toggl Track and 0CodeKit talk in both directions?

Yes. Build one flow that starts in Toggl Track and acts in 0CodeKit, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.

Connect Toggl Track to 0CodeKit

Move data between Toggl Track and 0CodeKit the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Start building Explore Toggl Track Explore 0CodeKit

Toggl Track triggers: 7
Toggl Track actions: 13
0CodeKit triggers: 0
0CodeKit actions: 34

Automation ideas

What you can build with Toggl Track and 0CodeKit

A few flows teams run between Toggl Track and 0CodeKit. Use one as a starting point, or build your own from scratch.

New Client in Toggl Track creates Current Month in 0CodeKit
Fires when a new client is created in a workspace.
New Client in Toggl Track creates Specific Month and Year in 0CodeKit
Fires when a new client is created in a workspace.
New Client in Toggl Track creates Current Week in 0CodeKit
Fires when a new client is created in a workspace.
New or Updated Workspace in Toggl Track creates Current Month in 0CodeKit
Fires when a workspace is created or updated (Toggl only supports workspace updated events).