Skip to content
Microsoft 365 Planner logoAMPECO logo

Connect Microsoft 365 Planner to AMPECO

Move data between Microsoft 365 Planner 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.

Microsoft 365 Planner triggers
3
Microsoft 365 Planner actions
12
AMPECO triggers
1
AMPECO actions
377

Automation ideas

What you can build with Microsoft 365 Planner and AMPECO

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

  • New Plan Created in Microsoft 365 Planner creates Custom API Call in AMPECO

    Triggers when a new Plan is created in Microsoft 365 Planner.

  • New notification in AMPECO creates Create Plan in Microsoft 365 Planner

    Triggers when a webhook notification event is received from Ampeco

  • New Plan Created in Microsoft 365 Planner creates Actions - Charge Point - Change Availability in AMPECO

    Triggers when a new Plan is created in Microsoft 365 Planner.

  • New notification in AMPECO creates Create Bucket in Microsoft 365 Planner

    Triggers when a webhook notification event is received from Ampeco

  • New Plan Created in Microsoft 365 Planner creates Actions - Charge Point - Change Owner in AMPECO

    Triggers when a new Plan is created in Microsoft 365 Planner.

  • New notification in AMPECO creates Create Task in Microsoft 365 Planner

    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 Microsoft 365 Planner 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.