Can Campaign Monitor and Tarvent talk in both directions?

Yes. Build one flow that starts in Campaign Monitor and acts in Tarvent, 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 Campaign Monitor to Tarvent

Move data between Campaign Monitor and Tarvent 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 Campaign Monitor Explore Tarvent

Campaign Monitor triggers: 3
Campaign Monitor actions: 4
Tarvent triggers: 17
Tarvent actions: 27

Automation ideas

What you can build with Campaign Monitor and Tarvent

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

New Subscriber Added in Campaign Monitor creates Create/Update Contact in Tarvent
Triggered when a new subscriber is added to a list.
Contact Added in Tarvent creates Add Subscriber in Campaign Monitor
Triggers when a contact is added to the selected audience.
New Subscriber Added in Campaign Monitor creates Update Contact in Tarvent
Triggered when a new subscriber is added to a list.
Contact Added in Tarvent creates Update Subscriber in Campaign Monitor
Triggers when a contact is added to the selected audience.
New Subscriber Added in Campaign Monitor creates Find Contact in Tarvent
Triggered when a new subscriber is added to a list.
Contact Added in Tarvent creates Unsubscribe Subscriber in Campaign Monitor
Triggers when a contact is added to the selected audience.