New User Approve Zapier integrationAutomate New User Approve with Zapier.
New User Approve Zapier integration: 6 triggers, 0 actions, no search step. Every registration your WordPress site holds for review, approves, auto-approves or denies can start a Zap that tells your team or updates your other tools.
Verified Trustpilot reviews · AI, automation & growth agency
What the New User Approve Zapier integration actually does
New User Approve is a WordPress plugin that takes care of the user registration process on your site: new accounts wait for a decision before they get in. With Zapier, a Zap (an automation you set up once: one trigger, then one or more actions) watches those decisions and passes each one to another tool, so nobody has to check the site to know who signed up.
Three results worth building. A review queue nobody forgets: User Pending starts the Zap when someone registers and is waiting, and a message goes to your team chat. A list of approved members kept up to date: User Approved adds a row to the spreadsheet where you track who has access. A record of refusals: User Denied logs each rejected registration, so you can look back at them later.
Three more triggers cover the automatic routes, each with (Pro) in its Zapier name: User Auto Approved via Role (Pro), User Auto Approved via Invitation Code (Pro) and User Auto Approved via Whitelist (Pro). Each one starts a Zap when a user is approved automatically by that route: a specific role, an invitation code or the whitelist.
What Zapier does not do for this app. All six triggers are polling triggers, so Zapier checks your site at regular intervals instead of hearing about a registration the moment it happens. There is no action and no search step: a Zap cannot approve, deny or look up a user in New User Approve, only react to what happened. And registrations made before the Zap was switched on are never picked up.
If you are still choosing between automation tools, see our Make vs Zapier comparison.
Zapier vocabulary in one minute
The Zapier words used on this page, each explained once in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Here: a registration that is pending, approved, auto-approved or denied.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, always in another app here.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
- Polling trigger
- A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only what it has not seen yet.
- Instant trigger
- A trigger the app reports itself, calling Zapier the moment the event happens. New User Approve has none on Zapier.
- Filter
- A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it then needs a paid plan.
What a New User Approve Zap really costs
New User Approve is not a premium app, so it works from the free plan. The triggers cost nothing; you pay for what your other tools do next.
- Free plan100 tasks a month, unlimited two-step Zaps
- TriggerNever counted as a task
- Failed actionNot counted against the plan
- Premium appNo, it works on the free plan
Zapier counts a task each time an action completes. A pending registration spotted by the trigger costs nothing, and Zapier's checks of your site cost nothing either, however often they run. An action that fails is not counted. Each successful action in a Zap counts on its own, so posting to a chat and adding a row is two tasks per registration. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger, one action. A filter or a second action needs a paid plan. All six triggers are polling triggers, so the grid below sets how often they check.
Connect New User Approve to Zapier
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your New User Approve account linked to Zapier once, then reused by every step that uses it.
- 02
Pick New User Approve
Search New User Approve in the dialog, select it and click Add connection. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 03
Sign in and grant access
Sign in in the tab that opens, then grant Zapier access to the account. The connection is then ready: the six New User Approve triggers in your next Zaps reuse it, and a trigger test brings back the three most recent items of the account.
Your first Zap: pending sign-ups flagged to your team
GoalWhen a new registration is waiting for approval and meets a condition you set, your team gets a chat message so someone reviews it.
- 01
Build: set the trigger
Create a Zap, choose New User Approve as the starting app and User Pending as the event, then pick the connection you made above.
- 02
Test the trigger
Run the test: Zapier brings back the three most recent pending registrations of the connected account. Read which fields come back before mapping any of them.
- 03
Add the filter
From the plus icon, add Filter and set its three boxes: the field to look at, the rule, the value to compare with. A filter makes the Zap multi-step, so it needs a paid plan.
- 04
Add the chat message
Add the action of your team chat that sends a message, choose the channel, and map in the registration fields that the trigger test actually returned.
- 05
Test, then publish
Test each step once and read the message that arrives. Then click Publish. From that moment, each new pending registration is checked on your plan's interval.
New User Approve triggers on Zapier
6 events start a Zap when something happens in New User Approve. Zapier checks for them at the interval your plan allows.
User Approved
Polling triggerIn Zapier“Triggers when a user is approved.”
Starts your Zap each time a user is approved on your WordPress site. It marks the moment a registration turns into a real member, and the point where your other tools can be told about it.
User Auto Approved via Role (Pro)
Polling triggerIn Zapier“Triggers when a user is auto approved via specific role.”
Runs a Zap when a user is approved automatically because of a specific role. It gives that route its own starting point, so the Zap only runs for members who came in by role.
User Denied
Polling triggerIn Zapier“Triggers when a user is denied.”
Fires a Zap whenever a user is denied. Pick it when each turned-down registration should be recorded or shared somewhere outside WordPress.
User Auto Approved via Invitation Code (Pro)
Polling triggerIn Zapier“Triggers when a user is Auto Approved via Invitation Code.”
Starts the Zap when a user is approved automatically thanks to an invitation code. Useful when codes are how you open the door to a specific group.
User Pending
Polling triggerIn Zapier“Triggers when a user Registers (Pending).”
Runs your Zap when someone registers and the account is left pending. It is the trigger to pick when new sign-ups need someone to look at them.
User Auto Approved via Whitelist (Pro)
Polling triggerIn Zapier“Triggers when a user is Auto Approved via Whitelist.”
Whitelisted users get their own trigger: a Zap starts when someone is approved automatically because they are on your whitelist. Use it to follow that route on its own, apart from the other approvals.
When a New User Approve Zap breaks
Zapier attaches no help article to New User Approve and lists no limit of its own for it. The cases below come from how Zapier works in general.
Four situations to know before you switch a Zap on. For other problems, see our Zapier troubleshooting guide.
Older registrations stay behind
A Zap only reacts to what happens after it is switched on. Users already pending, approved or denied are not picked up; moving that history is a separate job.A Zap that keeps setting itself off
As a general precaution: a Zap that writes into the very place its own trigger watches can start itself again and again, and burn through your tasks fast.A bulk import held back
When a trigger suddenly returns a huge batch, after a bulk import of users or a migration for example, Zapier's flood protection can hold it back.The same user, once
Zapier keeps track of what it has already seen on a polling trigger, so the same registration does not start the Zap twice.
Need help automating New User Approve with Zapier?
A person reads every message.
