Groundhogg Automations
How to Send an Email When a Tag Is Removed From a Groundhogg Contact
Losing a tag often means losing something that matters — a subscription lapsed, a customer was moved out of a programme, a lead went cold. Zapify can notify you the moment it happens, using the A tag is removed from a contact trigger and the Send an email action. Groundhogg is a Zapify PRO integration.
What this automation does
The automation is one trigger plus one action:
- Trigger: A tag is removed from a contact (
GROUNDHOGG_TAG_REMOVED, Groundhogg) - Action: Send an email (
WP_SEND_EMAIL, WordPress)
Whenever the tag you choose is removed from a contact, Zapify sends the email with that contact's details.
PRO feature
Groundhogg is a Zapify PRO integration. The Groundhogg trigger used in this automation needs an active Zapify PRO licence.
No Connection needed
Groundhogg runs on your own site rather than somebody else's server. There is no API key to paste and nothing to set up under Settings → Connections — the integration only needs Groundhogg installed and active.
Before you start
- Groundhogg installed and active.
- The tag you want to watch already exists in Groundhogg.
- A working mail setup so WordPress can send email.
How to build the automation
Step 1: Create a new automation
- In the WordPress admin, go to Zapify → Automations.
- Click Add New to open the builder.
- Name it clearly, such as Alert me when the member tag is removed.

Step 2: Add the "A tag is removed from a contact" trigger
- Click Add Trigger.

- Choose Groundhogg as the app.

- Select the trigger A tag is removed from a contact.

- Configure the trigger:
| Field | Required | What it does |
|---|---|---|
| Tag | Yes | Pick the tag to watch, or leave it on Any tag to run whenever any tag is removed. |
Step 3: Add the "Send an email" action
- Click Add Action.

- Choose WordPress as the app.

- Select Send an email.

Step 4: Configure the email

In the To field, type your team's address. Insert the Contact email token only if the message is meant for the contact.
For example:
- Subject:
{Contact email} lost the {Tag name} tag - Body:
{Contact first name} {Contact last name} ({Contact email}) no longer has the {Tag name} tag in Groundhogg. - Format: HTML or Plain text
Use the {} token button beside a field to insert the values — Zapify fills them in for each contact when the automation runs.
Step 5: Set the steps Live and save
Each trigger and action has its own Live / Off / Draft switch. A new automation starts as a Draft and does nothing until its steps are Live.
- Set the trigger and every action to Live.
- Click Save.

Step 6: Test it
Remove the tag from a test contact in Groundhogg → Contacts. Check the inbox, or open Zapify → Logs to confirm the run.
Tokens you can use
The A tag is removed from a contact trigger exposes these tokens for the email fields:
| Token | What it holds |
|---|---|
| Contact ID | The contact's Groundhogg ID. |
| Contact email | The contact's email address. |
| Contact first name / Contact last name | The contact's name parts, if set. |
| Contact phone | The contact's phone number, if set. |
| Contact owner ID | The ID of the WordPress user who owns the contact in Groundhogg. |
| Tag ID | The ID of the tag that was added or removed. |
| Tag name | The tag's name. |
Conclusion
With the A tag is removed from a contact trigger and the Send an email action, you hear about lost tags as they happen. To take a WordPress role away at the same time, see removing a role when a Groundhogg tag is removed.
FAQs
Is this free in Zapify?
The Send an email action is free, but the Groundhogg trigger is part of the Groundhogg PRO integration and needs an active Zapify PRO licence.
Does it fire if the tag was never on the contact?
No. It runs when a tag is actually removed from a contact that had it.
Can I watch any tag?
Yes. Leave Tag on Any tag, and use the Tag name token in the email to say which one.
Does Zapify's own tag action start this automation again?
No, not by default. Zapify ignores events caused by its own actions, so an automation that adds a tag does not trigger a tag automation in the same request. This is what stops an automation looping back on itself. Tags added by Groundhogg's own funnels, by you, or by another plugin do start it.
Do I need to write any code?
No. Everything is configured visually.