Contact Tag Workflow Trigger in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Contact Tag trigger fires when a tag is added or removed from a contact in Sparkforge. Use it to automate follow-ups, segment customers, and notify your team based on contact attributes.

The Contact Tag workflow trigger fires when a tag is added to or removed from a contact. Tags are simple labels you assign to contacts to organize them and drive automation.

For example, adding a "New Customer" tag can fire a welcome email; removing a "Lead" tag can update sales notifications.

What it is good for

Automation — react to attribute changes without manual work.
Organization — keep your contact database actionable.
Targeted engagement — segment and personalize communication.
Scalability — works the same across campaigns, pipelines, and teams.

How to set it up

Go to Automations > Workflows.
Click Create Workflow and pick a blank workflow or template.
Click Add Trigger and search for Contact Tag.
Name the trigger (for example, "Tag Added — Interested").
Pick whether the trigger fires on Added or Removed.
Choose the specific tag (for example, "Interested" or "Newsletter Subscriber"). Use + Add New Tag if it does not exist yet.
Add workflow actions and save.

Naming conventions

Use clear, consistent tag names like "VIP Customer" or "Cold Lead". Sloppy tag taxonomy is the number one cause of broken tag-based automation.

Example actions

When a tag is added

Send an email or SMS — for example, when "Interested" is added, send a thank-you email referencing {{contact.first_name}}.
Notify your team — internal Slack or email: "New contact tagged as Interested needs follow-up."

When a tag is removed

Send a re-engagement message — for example, when "Newsletter Subscriber" is removed, confirm the unsubscribe and offer a one-click rejoin.
Ask for feedback — send a quick survey to learn why they unsubscribed.

Advanced patterns

Combine with Contact Created

Stack a Contact Created trigger with a Contact Tag trigger to welcome a brand-new lead and react when their status is upgraded later. Each trigger handles a different lifecycle moment.

Tag-driven pipelines

Use tags to gate workflow branches. Add a "Qualified" tag from inside one workflow, then let a separate Contact Tag trigger move the contact into a sales sequence.

Common errors

Trigger never fires — confirm the tag name matches exactly. Tags are case-sensitive in some integrations.
Trigger fires too often — check workflow re-entry settings. If a contact gets re-tagged repeatedly, you may want to limit re-entry.
Wrong contacts entering — review the Added vs. Removed setting. Many bugs come from picking the wrong direction.

Frequently Asked Questions

Can the trigger fire on both adding and removing the same tag?

Not within a single trigger. Set up two triggers — one for Added and one for Removed — or use two separate workflows if the actions differ enough.

Does the trigger fire when I bulk-tag contacts?

Yes. Bulk tagging fires the trigger for each contact that receives the tag. If you do not want that, disable the workflow before bulk tagging or apply a filter to exclude bulk operations.

Can I use multiple tags as filter conditions?

You can configure the trigger to watch a specific tag, but for multi-tag logic, use If/Else branches inside the workflow to check for additional tags before running actions.

What happens if I delete a tag that is referenced by a trigger?

The trigger will not fire for the deleted tag. Recreate the tag with the exact same name or update the trigger to reference a different tag.