Can AddEvent and Village talk in both directions?

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

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

AddEvent triggers: 2
AddEvent actions: 9
Village triggers: 0
Village actions: 40

Automation ideas

What you can build with AddEvent and Village

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

New Calendar Subscriber in AddEvent creates Get App Information in Village
Triggers when a new subscriber is added to your AddEvent calendar. Leave the calendar blank to watch all of them.
New Calendar Subscriber in AddEvent creates Check Company Paths in Village
Triggers when a new subscriber is added to your AddEvent calendar. Leave the calendar blank to watch all of them.
New Calendar Subscriber in AddEvent creates Refresh Companies in Village
Triggers when a new subscriber is added to your AddEvent calendar. Leave the calendar blank to watch all of them.
New RSVP Attendee in AddEvent creates Get App Information in Village
Triggers when a new attendee RSVPs to your AddEvent event.