Can Clockify and AMPECO talk in both directions?

Yes. Build one flow that starts in Clockify and acts in AMPECO, 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 Clockify to AMPECO

Move data between Clockify and AMPECO 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 Clockify Explore AMPECO

Clockify triggers: 3
Clockify actions: 8
AMPECO triggers: 1
AMPECO actions: 377

Automation ideas

What you can build with Clockify and AMPECO

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

New Task in Clockify creates Custom API Call in AMPECO
Triggers when a new task is created in specified project.
New notification in AMPECO creates Create Task in Clockify
Triggers when a webhook notification event is received from Ampeco
New Task in Clockify creates Actions - Charge Point - Change Availability in AMPECO
Triggers when a new task is created in specified project.
New notification in AMPECO creates Create Time Entry in Clockify
Triggers when a webhook notification event is received from Ampeco
New Task in Clockify creates Actions - Charge Point - Change Owner in AMPECO
Triggers when a new task is created in specified project.
New notification in AMPECO creates Start Timer in Clockify
Triggers when a webhook notification event is received from Ampeco