Can AddEvent and Clockodo talk in both directions?

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

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

AddEvent triggers: 2
AddEvent actions: 9
Clockodo triggers: 2
Clockodo actions: 33

Automation ideas

What you can build with AddEvent and Clockodo

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

New Calendar Subscriber in AddEvent creates Create Entry in Clockodo
Triggers when a new subscriber is added to your AddEvent calendar. Leave the calendar blank to watch all of them.
New Entry in Clockodo creates Create Event in AddEvent
Triggers when a new time entry is created
New Calendar Subscriber in AddEvent creates Get Entry in Clockodo
Triggers when a new subscriber is added to your AddEvent calendar. Leave the calendar blank to watch all of them.
New Entry in Clockodo creates Update Event in AddEvent
Triggers when a new time entry is created
New Calendar Subscriber in AddEvent creates Get Entries in Clockodo
Triggers when a new subscriber is added to your AddEvent calendar. Leave the calendar blank to watch all of them.
New Entry in Clockodo creates Delete Event in AddEvent
Triggers when a new time entry is created