What it does
The WPClientHub app for Zapier connects your sites to the thousands of apps Zapier works with — page your on-call phone when a site goes down, post failed backups to a Slack channel, open a ticket from a form, or start a backup when something happens elsewhere. It is built on the public API and needs the Scale plan.
Invite-only for now. Zapier lists a new app in its directory only after it has reviewed it and seen it in use, so ours is private until then. Ask us at hello@wpclienthub.com and we’ll send you the invite. Once you accept, WPClientHub shows up in Zapier’s app search for your account only. Settings → API keys has the same link.
Set it up
- In WPClientHub, go to Settings → API keys and press Create a Zapier key (owners and admins). The Zapier preset has exactly the scopes the app uses. Copy the key — it is shown once.
- Open the invite link and accept it with your Zapier account.
- In Zapier, create a Zap and search for WPClientHub. When it asks you to connect an account, paste the key. Zapier checks it with
GET /api/v1/meand names the connection after your organization and the key. - Pick a trigger or an action (below), test it, and turn the Zap on.
Triggers
| Trigger | Fires when |
|---|---|
| New Site Down | A site is down — confirmed by a recheck about 3 minutes after its uptime check first failed, the same rule as the downtime email. |
| Site Back Up | A site that was reported down answers again. |
| Backup Failed | A backup doesn’t finish, with the reason. |
| Updates Finished | An update batch finishes, with each update’s result and the visual check. |
| New Vulnerability | A site runs a plugin, theme or WordPress version with a known vulnerability. |
| New Ticket | A help desk ticket is opened (needs the client help desk, which Scale includes). |
Triggers are instant. Turning a Zap on adds a webhook endpoint for its event in WPClientHub — you’ll see it under Settings → Webhooks marked via API, with its delivery log — and turning the Zap off removes it. While you build a Zap, Zapier loads recent real examples (your latest incidents, failed backups and so on) to map fields from.
Actions and search
| Action | What it does |
|---|---|
| Start Backup | Backs a site up now. Refused (and the Zap step says why) while a backup or a restore is already running. |
| Run Update Check | Asks a site to check WordPress.org for core, plugin and theme updates. |
| Create Ticket | Opens a help desk ticket for a client, optionally for one of its sites, with a priority. Written as the person who created the key; the automatic check runs unless you switch it off. |
| Find Site by URL (search) | Finds a site by its address — acme.com, https://www.acme.com/ and http://acme.com all match. Use its result as the site for an action. |
Starting safe updates isn’t a Zapier action on purpose — it goes through your approval queue and visual checks, which are better handled in WPClientHub. The API can do it.
Ideas
- New Site Down → SMS or PagerDuty to whoever is on call, with the site name, the cause and a link to it in WPClientHub.
- Backup Failed → a message in your team’s Slack channel and a task in your project tool.
- A form in Typeform, Gravity Forms or Google Forms → Find Site by URL → Create Ticket for that site’s client.
- New Vulnerability with severity high or critical → an email to the account manager.
Plans and keys
The Zapier app needs the Scale plan; it isn’t part of the Agency trial. If your organization leaves Scale, Zaps stop with “available on the Scale plan” and the key and subscriptions are kept for when it’s back. Revoking the key in Settings → API keys disconnects Zapier at once and switches off the webhook endpoints its Zaps created — Zapier then asks you to reconnect with a new key.
What Zapier can see
Only what the key’s scopes allow, for your organization only — the same data as the API. Events carry site names and addresses, client names, ticket titles and messages (never internal notes), backup and update results. Zapier keeps task history according to its own retention settings; WPClientHub keeps its delivery log for 30 days.