Connect Claude or ChatGPT to your webhooks with WPVibe
Connect Claude, ChatGPT or Cursor to Webhook Actions through WPVibe: one approval click in wp-admin, five tested recipes, and prompts you can paste.
WPVibe is a hosted connector between an AI assistant and a self-hosted WordPress site, and the route to Webhook Actions with the least setup: you install its free plugin, approve the connection once in wp-admin, and Claude, ChatGPT or Cursor can use everything Webhook Actions publishes through the WordPress Abilities API. There is no OAuth plugin to configure, no server rule to add and no password to paste into a chat. WPVibe has run 28 of those abilities on a live install and publishes five tested recipes for them. If your assistant sent you here because a recipe needs Webhook Actions, you are in the right place: it is the free plugin with the slug flowsystems-webhook-actions, and step 1 installs it.
/ Setup
- Install Webhook Actions
In wp-admin go to Plugins → Add Plugin and search for "Webhook Actions". Several results have "webhook" in the name, so check two things before you click Install Now: the full name reads "Webhook Actions – build automations and integrations with AI help", and the author is mateuszflowsystems. Then activate it — that sends nothing, because a fresh install has no webhooks. You need version 3.3.4 or newer, on WordPress 6.9 or newer. If WPVibe is already connected, you can ask your assistant to install and activate the plugin with the slug
flowsystems-webhook-actionsinstead; it asks you to confirm before it installs. - Install WPVibe
Add the free WPVibe plugin the same way: search for "WPVibe" under Plugins → Add Plugin. Check the author before you click Install Now — the plugin you want is by SeedProd, and its full name starts "WPVibe – MCP Server for WordPress". Then activate it.
- Open WPVibe and check the connection
A WPVibe entry appears in the admin sidebar. Its screen says "Not connected yet" and lists four steps, the first already ticked. Under "Check your connection", click Check site connectivity. It tests both directions — whether your site can reach WPVibe and whether WPVibe can reach your site — and the note under the button says what it sends: your site address and a temporary verification code, no passwords.
- Add WPVibe to your AI assistant
Step 3 on that screen has a button for each route. Add to Claude opens the WPVibe for WordPress listing in Claude’s connectors directory, and Add to ChatGPT opens WPVibe’s official ChatGPT app; connect it there. Cursor and other clients, Claude Code among them, add WPVibe as a custom connector with the MCP server address shown under the buttons,
https://mcp.wpvibe.ai/mcp. Whichever you use, it asks you to sign in to WPVibe: enter your email, then type in the 6-digit code WPVibe sends you. If you have no WPVibe account yet, that sign-in creates a free one. WPVibe’s client setup page has the steps for each client. - Ask the assistant to connect the site
Part B of the same step gives you a line to copy: "Connect my site at" followed by your site’s address. Paste it into the assistant. It replies with a link, which stays valid for an hour.
- Approve the connection in WordPress
Open the link in the browser where you are logged in to the site. It lands on WordPress’s own Authorize Application screen, which names the application as WPVibe followed by a date and time. Click Yes, I approve of this connection. WordPress then creates an application password for the account you are logged in with and hands it straight to WPVibe — you never type or paste a password, and nothing secret goes into the chat. That account is the one the assistant acts as, so approve as an administrator: Webhook Actions offers its abilities only to an account that could also open the plugin’s own screens. WPVibe confirms with a page headed "Connection verified".
- Check what it can see
The "Connection verified" page ends with a prompt to paste back into the chat, the same one as step 4 on WPVibe’s screen. It asks the assistant to read your site and report its name and address. Once it has answered, WPVibe’s screen in wp-admin shows the last two steps ticked: "Site connected" and "Your AI has used this site". Then ask "which Webhook Actions abilities can you use on my site?". You should get them back by name —
list-webhooks,create-webhook,get-trigger-schema,get-logsand the rest. If the list is empty, or has the read abilities but nocreate-webhook, see "If the assistant cannot find the abilities" on this page. - Say what you want built
One sentence is enough: which event, which fields, where to send them. The prompts at the end of this page are a starting point, and naming one of WPVibe’s recipes makes the assistant follow it step by step. It creates the webhook switched off, reads a real captured event rather than guessing field names, and shows you the mapping before anything is sent. If that event has never fired on your site, it asks you to fire it once — submit the form, place a test order.
- Approve the test, then switch it on
A test delivery is a real request to your endpoint, so the assistant asks first, then shows you what it sent and what came back. It asks again before turning the webhook on. From there the plugin works on its own: every delivery is queued, retried and logged on your site, whether or not an assistant is connected.
What you need
Webhook Actions 3.3.4 or newer on WordPress 6.9 or newer — that is the release the Abilities API arrived in — and PHP 8.0 or newer, with an administrator account. The site has to be reachable from the internet: WPVibe is a hosted service, so it cannot reach localhost or a site behind a login wall. On the AI side you need Claude, ChatGPT or another client that can add a remote MCP server. WPVibe’s free plan covers a daily allowance of tool calls; a build like the ones below uses roughly a dozen.
The five tested recipes
WPVibe ran each of these end to end on a live install before publishing it. Name one in the chat and the assistant follows it: Send WooCommerce orders to Zapier, Make or n8n, Send Contact Form 7 submissions to Zapier, Make or n8n, Find out why a webhook failed, Get alerted when a webhook fails and See what data your webhooks send. The first two build something; the other three only read, so they are a safe first thing to try on a site that already has webhooks.
What the assistant can and cannot do
Reading is always available: your triggers, webhooks, captured payloads, delivery logs and snippets. Building is on by default, and one switch turns it off — Webhook Actions → Settings → Let connected AI tools build webhooks — which holds every connected tool to read-only and leaves Build with AI alone. A new webhook is always created switched off. Firing a test delivery, turning a webhook on or off, sending a test alert and deleting a webhook are refused unless the call carries "confirmed": true. Be clear about what that flag is: the assistant sets it, not you, which is why the recipes make it ask you first. WPVibe adds an approval page of its own before a webhook or snippet is deleted and before a PHP snippet is attached to a webhook. Leave Dangerously bypass approvals on WPVibe’s screen unticked: with it on, WPVibe runs every change with no approval prompt. Secrets do not travel: stored credentials come back as names and masked hints, and in captured payloads and logs the value of any field named like a password, token or key reaches the assistant as [redacted].
Ask for the fields by name
What the assistant reads is scrubbed; what a webhook delivers is not. A webhook with no field mapping sends the whole event — for a WooCommerce order that includes the customer’s name, email, address and phone. So say which fields you want ("order number, total and customer email"), and the assistant maps those and drops the rest. The See what data your webhooks send recipe audits the webhooks you already have.
If the assistant cannot find the abilities
Three causes cover almost every case. WordPress older than 6.9 has no Abilities API, so there is nothing to publish — update WordPress. Webhook Actions older than 3.3.4 is too old for WPVibe’s recipes — update it. And the connection has to be made as an administrator: Webhook Actions offers its abilities only to a user who can manage the site’s options, so an assistant connected as an editor cannot use them. If the read abilities are there but create-webhook is not, building has been switched off under Webhook Actions → Settings → Let connected AI tools build webhooks.
Disconnecting
Deactivating or deleting the WPVibe plugin does not cut the connection. WPVibe reaches your site with the WordPress application password you approved, and that keeps working without the plugin. To cut access, do both things WPVibe’s own screen lists: revoke the WPVibe application password under Users → Profile → Application Passwords, and remove the site from your WPVibe account. Your webhooks are not affected either way — they run inside Webhook Actions.
WPVibe or a direct connection?
With WPVibe every request passes through WPVibe’s servers and counts against its daily allowance; in exchange you skip the server setup and get recipes that were tested on a live install. The direct routes — Claude Code or Cursor and Claude on the web — keep everything between the AI and your site, at the price of an MCP server plugin and, for claude.ai, an OAuth setup that depends on your host. All three reach the same abilities. None of them spends Build with AI credits: the model doing the work is the one you already have in Claude or ChatGPT.
/ Examples
Prompt — WooCommerce orders to n8n, Make or Zapier
My WordPress site uses Webhook Actions and WooCommerce. Send every completed order to my n8n workflow at https://example.com/webhook/orders. Send only the order number, total, currency and customer email. Create it switched off, show me the mapping, and ask me before you send a test or turn it on.
Prompt — one Contact Form 7 form to a webhook
My WordPress site uses Webhook Actions and Contact Form 7. Send every submission of my "Contact" form to my Make scenario at https://example.com/hook. Send the name, email and message, plus the form’s title. Do not send submissions of any other form.
Prompt — why did it fail?
A webhook on my site stopped delivering yesterday. Read the Webhook Actions delivery log, tell me which webhook failed and why in plain words, and suggest the fix. Change nothing and re-send nothing until I say so.
Prompt — tell me when one gives up
Alert me when any webhook on my site gives up on a delivery. Use a notification channel I already have in Webhook Actions, show me the rule before you create it, and ask me before you send a test alert.
/ Related
