Can Toggl Track and Village talk in both directions?

Yes. Build one flow that starts in Toggl Track and acts in Village, 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 Village

Move data between Toggl Track and Village 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 Village

Toggl Track triggers: 7
Toggl Track actions: 13
Village triggers: 0
Village actions: 40

Automation ideas

What you can build with Toggl Track and Village

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

New Client in Toggl Track creates Get App Information in Village
Fires when a new client is created in a workspace.
New Client in Toggl Track creates Check Company Paths in Village
Fires when a new client is created in a workspace.
New Client in Toggl Track creates Refresh Companies in Village
Fires when a new client is created in a workspace.
New or Updated Workspace in Toggl Track creates Get App Information in Village
Fires when a workspace is created or updated (Toggl only supports workspace updated events).