Skip to content
AddEvent logoMicrosoft Excel 365 logo

Connect AddEvent to Microsoft Excel 365

Move data between AddEvent and Microsoft Excel 365 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.

AddEvent triggers
2
AddEvent actions
9
Microsoft Excel 365 triggers
4
Microsoft Excel 365 actions
33

Automation ideas

What you can build with AddEvent and Microsoft Excel 365

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

  • New Calendar Subscriber in AddEvent creates Append Row to Worksheet in Microsoft Excel 365

    Triggers when a new subscriber is added to your AddEvent calendar. Leave the calendar blank to watch all of them.

  • New Row in Microsoft Excel 365 creates Create Event in AddEvent

    Trigger when a new row is added, and it can include existing rows as well.

  • New Calendar Subscriber in AddEvent creates Append Multiple Rows in Microsoft Excel 365

    Triggers when a new subscriber is added to your AddEvent calendar. Leave the calendar blank to watch all of them.

  • New Row in Microsoft Excel 365 creates Update Event in AddEvent

    Trigger when a new row is added, and it can include existing rows as well.

  • New Calendar Subscriber in AddEvent creates Get Worksheets in Microsoft Excel 365

    Triggers when a new subscriber is added to your AddEvent calendar. Leave the calendar blank to watch all of them.

  • New Row in Microsoft Excel 365 creates Delete Event in AddEvent

    Trigger when a new row is added, and it can include existing rows as well.

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 AddEvent and acts in Microsoft Excel 365, 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.