Groundhogg Automations
How to Add a WordPress User Role When a Groundhogg Tag Is Added
If your CRM decides who is a member, your site should follow. Zapify can give a WordPress user a role the moment Groundhogg tags them, using the A tag is added to a contact trigger and the free Add a role to a user action. Groundhogg is a Zapify PRO integration.
What this automation does
The automation is one trigger plus one action:
- Trigger: A tag is added to a contact (
GROUNDHOGG_TAG_ADDED, Groundhogg) - Action: Add a role to a user (
WP_ADD_USER_ROLE, WordPress)
When the tag you choose is added to a contact that belongs to a WordPress account, Zapify adds the role to that account.
The contact needs a WordPress account
A role can only be added to a WordPress user. If the tagged contact is not linked to a WordPress account — a lead who never registered, for example — the run is skipped with the message that the action needs a user. To create an account for such contacts, see creating a WordPress user when a Groundhogg tag is added.
PRO feature
Groundhogg is a Zapify PRO integration. The Groundhogg trigger used in this automation needs an active Zapify PRO licence.
Before you start
- Groundhogg installed and active.
- The tag that means "member" already exists in Groundhogg.
- The role you want to grant, such as a custom Member role.
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 Give members their role when tagged.

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

- Choose Groundhogg as the app.

- Select the trigger A tag is added to 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 added. |
Step 3: Add the "Add a role to a user" action
- Click Add Action.

- Choose WordPress as the app.

- Select Add a role to a user.

Step 4: Configure the action
| Field | Required | What it does |
|---|---|---|
| User | No | Leave empty. The action then uses the WordPress account linked to the tagged contact. |
| Role | Yes | Pick the role to grant — the list shows the roles that exist on your site. |
| Replace existing roles | No | Off by default, so the user keeps their current roles. Turn it on only if this role should replace all others. |
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
Add the tag to a contact that belongs to a test WordPress user. Check the user's Role in Users → All Users, or open Zapify → Logs to confirm the run.
Conclusion
With the A tag is added to a contact trigger and the free Add a role to a user action, Groundhogg tags decide who gets access on your site. To reverse it, see removing a role when a Groundhogg tag is removed.
FAQs
Is this free in Zapify?
The Add a role to a user action is free, but the Groundhogg trigger is part of the Groundhogg PRO integration and needs an active Zapify PRO licence.
Why was the run skipped?
The tagged contact has no linked WordPress account. Open Zapify → Logs to see the message. Roles can only be added to users.
Does the user lose their other roles?
Not unless you turn on Replace existing roles.
Can different tags grant different roles?
Yes. Build one automation per tag, each with its own Tag and Role.
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.