Can AddEvent and Copper talk in both directions?

Yes. Build one flow that starts in AddEvent and acts in Copper, 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 Copper

Move data between AddEvent and Copper 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 Copper

AddEvent triggers: 2
AddEvent actions: 9
Copper triggers: 11
Copper actions: 20

Automation ideas

What you can build with AddEvent and Copper

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

New Calendar Subscriber in AddEvent creates Create Person in Copper
Triggers when a new subscriber is added to your AddEvent calendar. Leave the calendar blank to watch all of them.
New Activity in Copper creates Create Event in AddEvent
Triggers when a new activity is logged
New Calendar Subscriber in AddEvent creates Update Person in Copper
Triggers when a new subscriber is added to your AddEvent calendar. Leave the calendar blank to watch all of them.
New Activity in Copper creates Update Event in AddEvent
Triggers when a new activity is logged
New Calendar Subscriber in AddEvent creates Create Lead in Copper
Triggers when a new subscriber is added to your AddEvent calendar. Leave the calendar blank to watch all of them.
New Activity in Copper creates Delete Event in AddEvent
Triggers when a new activity is logged