Start free
ActionActiveCampaignUpdated June 2026

How do I remove a tag from a contact in ActiveCampaign?

Short answer: You can remove tag from contact in ActiveCampaign by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the ActiveCampaign Remove Tag from Contact action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this actionAll 11 ActiveCampaign actions
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Contact-Tag ID
contact_tag_id
stringRequiredThe ID of the contact-tag association (not the tag ID itself)
Sample request
{
  "contact_tag_id": "e.g. 789"
}
Returns
{
  "success": true
}

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

Triggered by

Apps that pair well as the trigger for Remove Tag from Contact.

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 Remove Tag from Contact.

What does the Remove Tag from Contact action do in ActiveCampaign?
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.
What inputs does Remove Tag from Contact require?
Required: Contact-Tag ID. Every input accepts a static value or a variable from any upstream node in your workflow.
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 Remove Tag from Contact support batch operations?
Yes. Run Remove Tag from Contact inside a Loop node to process arrays. TinyCommand 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.