Skip to content
TickTick logoAMPECO logo

Connect TickTick to AMPECO

Move data between TickTick 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.

TickTick triggers
1
TickTick actions
8
AMPECO triggers
1
AMPECO actions
377

Automation ideas

What you can build with TickTick and AMPECO

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

  • New Task Created in TickTick creates Custom API Call in AMPECO

    Triggers when a new task is created in a selected project.

  • New notification in AMPECO creates Create Task in TickTick

    Triggers when a webhook notification event is received from Ampeco

  • New Task Created in TickTick creates Actions - Charge Point - Change Availability in AMPECO

    Triggers when a new task is created in a selected project.

  • New notification in AMPECO creates Update Task in TickTick

    Triggers when a webhook notification event is received from Ampeco

  • New Task Created in TickTick creates Actions - Charge Point - Change Owner in AMPECO

    Triggers when a new task is created in a selected project.

  • New notification in AMPECO creates Get Task in TickTick

    Triggers when a webhook notification event is received from Ampeco

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

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