Groundhogg Automations
How to Create a WordPress User When a Groundhogg Tag Is Added
Some contacts become members later — they paid, were approved, or reached a stage in a funnel. Zapify can create their WordPress account the moment Groundhogg tags them, using the A tag is added to a contact trigger and the free Create 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: Create a user (
WP_CREATE_USER, WordPress)
When the tag you choose is added to a contact, Zapify creates a WordPress account using the contact's email and name, gives it the role you pick, and can email the new user a link to set a password.
Duplicate emails fail
The action fails if a WordPress account with that email already exists — it does not update the existing account. Contacts who already have an account are not a problem for the other guides here, but they will show as a failed run in Zapify → Logs for this one.
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 "give this contact an account" already exists.
- Decide the role the new accounts should get.
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 Create an account when a contact is tagged member.

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 "Create a user" action
- Click Add Action.

- Choose WordPress as the app.

- Select Create a user.

Step 4: Configure the action
| Field | Required | What it does |
|---|---|---|
| Yes | Insert the Contact email token. | |
| Username | No | Leave empty to use the email address. |
| Password | No | Leave empty — Zapify generates a strong one. |
| First name / Last name | No | Insert the Contact first name and Contact last name tokens. |
| Role | No | Leave empty for your site's default role, or pick one such as Member. |
| Email the new user | No | On by default. Sends WordPress's welcome email with a link to set a password. |

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 test contact in Groundhogg → Contacts, using an email that has no WordPress account. Check Users for the new account, or open Zapify → Logs to see why a run failed.
Tokens this action makes available
| Token | What it holds |
|---|---|
| Created user ID | The ID of the account that was created. |
| Created user email | The email address it was created with. |
| Created username | The username it was created with. |
Add further actions after this one — such as sending a welcome email — and they can use these tokens.
Conclusion
With the A tag is added to a contact trigger and the Create a user action, a Groundhogg tag becomes a WordPress account with the right role. Combine it with adding a role when a tag is added for contacts who already have accounts.
FAQs
Is this free in Zapify?
The Create a user action is free, but the Groundhogg trigger is part of the Groundhogg PRO integration and needs an active Zapify PRO licence.
Does the new user get a password?
Zapify generates a strong one if you leave Password empty. With Email the new user on, WordPress sends a link so they can set their own.
What if the contact already has an account?
The action fails because the email is taken. Use adding a role when a tag is added for those contacts instead.
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.