ActiveCampaign
ActiveCampaign contact and deal lifecycle, automated
ActiveCampaign is the marketing-automation tool that built its growth on better deliverability and better automation logic than the average email tool. Five triggers cover the lifecycle: Contact Added, Contact Added to List, Tag Added to Contact (a key signal for ActiveCampaign's segmentation model), Deal Created, Deal Updated. Eleven actions cover writes and reads: Create Contact, Add Contact to List, Add Tag to Contact, Delete Contact, plus the read endpoints for contacts, tags, lists, and automations. The integration uses an ActiveCampaign API key + account URL from your account settings. Common patterns: a Typeform Response Submitted fires Create Contact with the form answers as custom fields, an AI step classifies intent and the result fires Add Tag to Contact, and the new tag triggers an ActiveCampaign automation that sends the right nurture sequence. ActiveCampaign's tag-based segmentation makes the tag actions disproportionately useful, most workflow logic resolves to "add this tag, let the automation handle the rest."
Workflows start when ActiveCampaign does.
5 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Fires when a new contact lands in ActiveCampaign from any source — form submission, API import, manual entry, or CRM sync. Payload includes the full contact record plus the source attribution. The base hook for "new lead in AC → fan out to slack/sheet/CRM" workflows; pair with a downstream filter on tag or list for tighter targeting.
Fires when an existing contact is added to a specific ActiveCampaign list (manually or via automation). Differs from Contact Added in that it tracks list-membership changes rather than contact creation — useful when your funnel structure is "list = segment" and you care about the moment of segment entry.
Fires when a new deal is created in the ActiveCampaign CRM, either manually or via automation. Payload includes deal value, currency, pipeline, stage, owner, and the associated contact. The opportunity-creation hook for "log deal to finance sheet, ping owner in Slack, notify the BDR" fan-out workflows.
Fires on any change to an existing deal — stage transition, value change, owner reassignment, custom-field edit. For stage-specific reactions (e.g., only fire on "moved to Negotiation"), the workflow needs to inspect the payload's stage field and short-circuit when the change doesn't match.
Fires whenever a tag is added to a contact — by automation, by manual edit, or by API. The cleanest signal for behaviour-driven workflows since ActiveCampaign's tag system is the typical place where qualification status, engagement level, or product interest gets recorded. Configure the trigger to a specific tag for tight scoping.
Do anything ActiveCampaign can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Add Contact to List | Subscribes an existing contact to a specific list. If the contact isn't in the system, this fails — use Create Contact first or the upsert pattern. List membership drives campaign targeting in ActiveCampaign, so this is how cross-app workflows hand off leads into AC's nurture flows. |
| Add Tag to Contact | Applies a tag to a contact — auto-creates the tag if it doesn't exist yet, which makes it forgiving for workflow setup but easy to fragment your tag taxonomy. Maintain a canonical tag list (in a Notion doc or workflow constant) to avoid "Customer", "customer", "Customers" all coexisting. |
| Create Contact | Creates a new contact with email, name, phone, and any configured custom fields. ActiveCampaign treats email as the dedupe key — repeated creates with the same email update the existing record. For "auto-add new leads from upstream" workflows, this is the entry point. |
| Delete Contact | Hard-deletes the contact and all associated history (campaign engagement, automation state, list memberships). Irreversible — for GDPR right-to-erasure workflows or compliance cleanups. For soft removal (suppress without erasing history), use Unsubscribe or remove from all lists instead. |
| Get Contact | Returns the full contact record by ID — standard fields, custom fields, current tags, list memberships, and recent activity if requested. The standard lookup before Update Contact or for enrichment workflows that need a snapshot of AC state for downstream decisions. |
| List Automations | Returns every automation in the connected ActiveCampaign account with name, status (active, paused, draft), and the contact count currently in each. Useful for "where are my leads right now" audit workflows and for resolving automation IDs at workflow-build time. |
| List Contacts | Paginated contact retrieval with filters for email, list membership, tag, status, and recently-modified time. For bulk-sync workflows that mirror AC into a warehouse or another CRM, use the timestamp filter to incrementally pull only the contacts touched since the last sync. |
| List Tags | Returns every tag in the connected account with the count of contacts currently carrying each. Useful for populating tag-pickers in workflow setup and for governance audits ("which tags are barely used and can be retired?"). Tags are workspace-wide; renaming in AC propagates to the API. |
| Remove Tag from Contact | Removes a single tag from a contact's tag set. Useful for "qualification expired", "campaign complete", "no longer interested" state transitions where the tag is the membership signal and removal is the exit. |
| Track Event | Pushes a custom behavioural event into ActiveCampaign's event store, where automation triggers can react to it. Requires Event Tracking to be enabled in the AC account. Useful for "user did X in our product → start the X-completed nurture flow" patterns where the event happens outside AC's native form/email tracking. |
| Update Contact | Updates standard fields and custom fields on an existing contact by ID. Partial updates supported — only the passed fields change, others stay untouched. For "enrichment from external source → write back to AC" workflows where you're augmenting with firmographic data after the initial signup. |
Pre-built ActiveCampaign workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
AI-triage every ActiveCampaign event, ping the right channel only when it matters.
Every event matching a filter, appended to a running spreadsheet.
Turn ActiveCampaign into a Notion-backed source of truth, auto-tagged.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect ActiveCampaign once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every ActiveCampaign field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the ActiveCampaign integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect ActiveCampaign to Tiny Command?
What ActiveCampaign triggers does Tiny Command support?
What ActiveCampaign actions can I run from a workflow?
Is the ActiveCampaign integration real-time?
Do I need to write code to use ActiveCampaign with Tiny Command?
How much does the ActiveCampaign integration cost?
More crm & sales apps people connect.
Same category as ActiveCampaign, ordered by how often teams pair them. Hover the carousel to pause.
Do more with ActiveCampaign.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
