Can Retable and Clockodo talk in both directions?

Yes. Build one flow that starts in Retable 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 Retable to Clockodo

Move data between Retable 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 Retable Explore Clockodo

Retable triggers: 0
Retable actions: 7
Clockodo triggers: 2
Clockodo actions: 33

Automation ideas

What you can build with Retable and Clockodo

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

New Entry in Clockodo creates Create Retable Record in Retable
Triggers when a new time entry is created
New Entry in Clockodo creates Get Workspaces in Retable
Triggers when a new time entry is created
New Entry in Clockodo creates Get Projects in Retable
Triggers when a new time entry is created
New Absence Enquiry in Clockodo creates Create Retable Record in Retable
Triggers when a new absence enquiry is created