user.signuppage.completedlesson.completed|Actionsadd_to_listremove_from_listadd_tagremove_tagsync_contactThe event names shown here are examples. In Meshes, event types are fully customized for each organization.
What you can do
Create the ActiveCampaign connection in Meshes with the account API URL and API key. Meshes loads the available lists and tags from that account so rules can target current ActiveCampaign objects.
ActiveCampaign works best when lifecycle state is driven by product behavior, not by a separate sync job trying to reconstruct it later. Events like page.completed or lesson.completed are often the difference between generic follow-up and well-timed automation.
Meshes keeps those routing rules in one place. An ActiveCampaign connection with an API URL and key lives in the workspace, the list or tag comes from live action data, and delivery concerns like retries and replay stay out of app code.
add_to_listStart lifecycle sequences when a signup, qualification event, or onboarding milestone means the contact should enter a new list.
remove_from_listStop the old nurture or onboarding path when product behavior shows the user has advanced or no longer belongs in that sequence.
add_tagUse product events to apply tags that downstream automation can react to immediately.
remove_tagKeep tags accurate as users complete steps, change lifecycle stage, or exit the flow the automation was built around.
sync_contactCreate or update the ActiveCampaign contact record using mapped fields only, without adding to a list or changing tags.
Common use cases
Workflows where this destination tends to matter first — the product event, the destination action, and the operational retry path living inside the same workspace.
Use page.completed to add or remove the tags and lists that ActiveCampaign automation depends on during onboarding.
Use lesson.completed to move learners into the next lifecycle path without manual exports or batch sync jobs.
Use user.signup to place new users into the onboarding list and apply the tags that segment the follow-up experience.
Let the same event layer that powers your other destinations keep ActiveCampaign tags and lists in sync as behavior changes.
How it works
A connection lives in the workspace, a rule binds the event to the action, and the delivery layer handles the last mile with retries, replay, and per-destination history.
Create the ActiveCampaign connection in Meshes with the API URL and key, then confirm the lists and tags you need appear in the action data for the connection.
Create rules for events like page.completed or lesson.completed, choose the list or tag action, and map the event fields ActiveCampaign needs to identify the contact.
Emit the product event from your application or use Send Test Event in Meshes. Meshes handles the delivery, retries failed attempts, and keeps the rule history visible.
Event example
import MeshesEventsClient from '@mesheshq/events';
const meshes = new MeshesEventsClient(
process.env.WORKSPACE_PUBLISHABLE_KEY!,
);
await meshes.emit({
event: 'page.completed',
resource: 'onboarding_page',
resource_id: 'welcome-checklist',
payload: {
email: 'alex@northstar.io',
user_id: 'usr_2048',
page_slug: 'welcome-checklist',
completed_at: '2026-03-22T10:30:00.000Z',
},
});Connection model
Create the ActiveCampaign connection in Meshes with the account API URL and API key. Meshes loads the available lists and tags from that account so rules can target current ActiveCampaign objects.
Why Meshes
ActiveCampaign sits inside the same fan-out, retry, replay, and delivery-visibility layer as every other destination — customer-connected or internal — that the workspace owns.
Meshes keeps the ActiveCampaign rule shape close to the event that matters instead of spreading list and tag logic across separate jobs.
When onboarding and education milestones land through a delivery layer with retries and replay, ActiveCampaign state stays closer to reality.
The connection can be created once in Meshes and reused across multiple event-routing rules without duplicating credentials across services.
The same Meshes event can update ActiveCampaign and other systems in parallel instead of forcing a custom behavioral sync path for each tool.
Keep exploring
Concrete patterns, supporting documentation, and build-vs-buy context that usually come up during evaluation.
Catalog
Return to the integrations catalog and compare ActiveCampaign with the rest of the lifecycle-routing surface.
Open linkDocs
ActiveCampaign setup steps, supported actions, and rule-building details.
Open linkUse Case
Example of onboarding milestones driving lifecycle automation from the product event itself.
Open linkUse Case
Example of education events updating downstream tools when users finish meaningful product steps.
Open linkGuide
Concrete Meshes pattern for driving ActiveCampaign automation from onboarding progress.
Open linkCompare
Breakdown of the cost to build list, tag, retry, and replay logic yourself for every behavioral flow.
Open linkpage.completed once, let Meshes drive the ActiveCampaign list and tag changes, and keep lifecycle automation tied to real product progress.