Can tl;dv and Clockodo talk in both directions?

Yes. Build one flow that starts in tl;dv and acts in Clockodo, 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 tl;dv to Clockodo

Move data between tl;dv and Clockodo 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 tl;dv Explore Clockodo

tl;dv triggers: 2
tl;dv actions: 5
Clockodo triggers: 2
Clockodo actions: 33

Automation ideas

What you can build with tl;dv and Clockodo

A few flows teams run between tl;dv and Clockodo. Use one as a starting point, or build your own from scratch.

Meeting Ready in tl;dv creates Create Entry in Clockodo
Triggers when a meeting has finished processing and is ready
New Entry in Clockodo creates Upload Recording in tl;dv
Triggers when a new time entry is created
Meeting Ready in tl;dv creates Get Entry in Clockodo
Triggers when a meeting has finished processing and is ready
New Entry in Clockodo creates List Meetings in tl;dv
Triggers when a new time entry is created
Meeting Ready in tl;dv creates Get Entries in Clockodo
Triggers when a meeting has finished processing and is ready
New Entry in Clockodo creates Get Meeting in tl;dv
Triggers when a new time entry is created