Start free
ActionActiveCampaignUpdated June 2026

What tags exist in the ActiveCampaign account?

Short answer: Drop the "ActiveCampaign → List Tags" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this actionAll 11 ActiveCampaign actions
Sample request
{}
Returns
{
  "tags": [
    {
      "id": "1",
      "tag": "customer",
      "subscriber_count": "500"
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List Tags.

Any of these apps can fire this action as part of a workflow.

Gmail → ActiveCampaign
1 Gmail triggers
Slack → ActiveCampaign
13 Slack triggers
Google Sheets → ActiveCampaign
2 Google Sheets triggers
HubSpot → ActiveCampaign
18 HubSpot triggers
FAQ

Questions about List Tags.

What does the List Tags action do in ActiveCampaign?
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.
What inputs does List Tags require?
List Tags has no required inputs. Sensible defaults are applied if you leave fields blank.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if ActiveCampaign returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does List Tags support batch operations?
Yes. Run List Tags inside a Loop node to process arrays. Tiny Command handles ActiveCampaign's rate limits automatically so you don't have to throttle manually.
More actions

Other ActiveCampaign actions.

Action
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.
Action
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.
Action
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.
Action
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.
Action
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.
Action
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.

Send list tags from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.

Try for freeRequest a demo