Build WordPress-native automations with triggers, actions, filters, dynamic tags, logs, AI-assisted workflow creation, and optional specialist add-ons.
WP Webhooks
Table of contents
- Quick take
- WP Webhooks features at a glance
- Send Data turns WordPress events into outbound webhooks
- Receive Data lets external systems perform WordPress actions
- Authentication should be treated as mandatory for write actions
- Version 3.5.0 adds WordPress Abilities and MCP-ready actions
- Ability metadata helps AI clients understand risk
- WP Webhooks Pro adds workflow orchestration around the endpoints
- Integration coverage is broad but the webhook model matters more than the count
- Security changes from 3.4.x still matter in 3.5.0
- WP Webhooks Free vs Pro
- WP Webhooks pricing
- Production checklist
- WP Webhooks vs AutomatorWP, Uncanny Automator and Bit Flows
- Who should choose WP Webhooks?
- Design webhook retries to be idempotent
- PluginSuggest verdict
- WP Webhooks FAQs
Plugin Health & Stats
Historical overview
364-day WordPress.org historyQuick take
WP Webhooks is a WordPress automation and API-connection plugin for sending data out of WordPress, receiving data into WordPress, and building multi-step automation flows around those events. The current release reviewed is 3.5.0, released October 7, 2026.
The biggest recent change is support for the WordPress Abilities API. Individual WP Webhooks actions can now be exposed as registered WordPress Abilities, which means AI assistants and MCP clients can discover and run approved actions when a compatible MCP server such as MCP Adapter is installed.
Best for: developers, agencies, automation-heavy WordPress sites, and teams that need flexible webhook/API connections without building custom endpoints from scratch.
Current version: 3.5.0.
Free strength: outbound triggers, incoming actions, authentication, multiple request formats/methods, testing, and a broad integration catalog.
Pro strength: Flows, data mapping, logs, advanced security, Pro integrations/extensions, AI integrations, and deeper automation controls.
Pricing checked October 16, 2026: Pro starts at $149/year for one site.

WP Webhooks features at a glance

| Area | What it does | Availability |
|---|---|---|
| Send Data | Fire outgoing webhooks when WordPress events happen | Free + Pro |
| Receive Data | Accept incoming requests and run WordPress actions | Free + Pro |
| Authentication | Secure endpoints with API Key, Bearer Token or Basic Auth | Free + Pro |
| Request formats | JSON, XML, plain text/HTML, forms and form-urlencoded payloads | Free + Pro |
| HTTP methods | POST, GET, HEAD, PUT, DELETE, TRACE, OPTIONS and PATCH | Free + Pro |
| Flows | Chain triggers and actions into multi-step workflows | Pro |
| Data mapping | Transform incoming and outgoing payloads | Pro |
| Logs | Inspect automation execution and troubleshoot failures | Pro |
| WordPress Abilities | Expose approved actions as AI/MCP-callable WordPress abilities | 3.5.0+, WordPress 6.9+ |
| AI integrations | OpenAI, Claude, Gemini and OpenRouter inside Pro workflows | Pro |
Send Data turns WordPress events into outbound webhooks
The Send Data side of WP Webhooks watches a trigger in WordPress and forwards its payload to one or more endpoints. A form submission can be sent to a CRM, a WooCommerce order can be forwarded to another system, a user event can notify an automation platform, or a custom WordPress hook can become an external integration point.

Because it supports multiple request methods and content formats, WP Webhooks can connect with more than webhook-only services. You can structure requests for APIs that expect JSON, XML, form data, query values, or a particular HTTP method rather than a generic POST.
Receive Data lets external systems perform WordPress actions
The Receive Data side reverses the direction. An external service calls the endpoint and WP Webhooks runs an approved action inside WordPress. Core actions include creating, updating, searching or deleting users and posts, sending email, managing comments and taxonomy data, and calling custom PHP or WordPress logic where supported.

The detailed argument documentation is valuable because webhook automation usually fails at the data-contract layer, not at the HTTP layer. Knowing the expected field name, type, accepted values and response structure reduces trial and error when connecting another app.
Authentication should be treated as mandatory for write actions
WP Webhooks supports API Key, Bearer Token and Basic Auth authentication. That matters because incoming endpoints can create or update WordPress data. Publicly exposing an unauthenticated endpoint that can create users, posts, orders or files would be a serious security mistake.

Pro adds more controls such as IP whitelisting, access tokens and webhook URL action whitelists. For production integrations, I would combine authentication with least-privilege WordPress permissions and avoid giving external systems more actions than they actually need.
Version 3.5.0 adds WordPress Abilities and MCP-ready actions
WP Webhooks 3.5.0 integrates with the WordPress Abilities API introduced for modern tool-based automation. An administrator can enable a WP Webhooks action as a WordPress Ability from the Receive Data screen. The plugin registers an input schema, output schema and permission callback for that action.

With an MCP server such as MCP Adapter, that ability can become a tool available to clients like Claude or Cursor. Nothing is exposed automatically. Each action must be enabled individually, and the administrator chooses the required WordPress capability.
Ability metadata helps AI clients understand risk
The ability screen shows the registered name, required capability and safety-related annotations. Version 3.5.0 also asks for confirmation before exposing an action that is not read-only and attaches read-only, destructive and idempotent annotations where appropriate.

This does not make every action safe to expose. A create-post action and a delete-user action have very different blast radiuses. The useful part is that WP Webhooks now provides an explicit permission and metadata layer instead of presenting every action as an undifferentiated remote command.
WP Webhooks Pro adds workflow orchestration around the endpoints
Free is primarily about sending and receiving data. Pro turns those endpoints into a larger automation platform. Flows can chain multiple triggers and actions, and Pro adds conditionals, scheduling/delay tools, data mapping, data manipulation, logs, premium integrations and extensions.
Pro also includes AI integrations for Claude, OpenAI, Google Gemini and OpenRouter. These can be used as workflow steps for tasks such as summarizing submissions, generating content, extracting structured information or creating media. The model API keys and usage remain separate from the WP Webhooks license.
Integration coverage is broad but the webhook model matters more than the count

WP Webhooks lists more than 100 integrations across WordPress, WooCommerce, forms, LMS tools, membership plugins, CRMs, automation platforms and utilities. Examples include WooCommerce, Gravity Forms, Fluent Forms, WPForms, LearnDash, Paid Memberships Pro, FluentCRM, SureCart, WP All Import, WP Fusion, Make, Zapier, Pabbly Connect, n8n and Microsoft Power Automate.
The real strength is that the plugin is not limited to prebuilt integrations. If an external service exposes a compatible API or webhook, WP Webhooks can often connect to it directly through generic requests, authentication and data mapping.
Security changes from 3.4.x still matter in 3.5.0
Version 3.4.3 added a trigger payload policy that lets administrators strip sensitive user fields from outgoing data. New webhook configurations remove sensitive fields by default, while older webhooks require review so existing workflows are not silently broken.
Earlier 3.4.x and 3.3.x releases also addressed security issues around file handling and object injection. That history is a reminder to keep an automation plugin updated because it sits directly on data flows that can cross the WordPress boundary.
WP Webhooks Free vs Pro
Free gives you the fundamental integration engine: unlimited webhook action URLs and triggers, send/receive workflows, authentication, testing, supported request methods and formats, and many core WordPress/plugin integrations. It is enough for developers who primarily need robust endpoints.
Pro is the better fit when the workflow should be built and managed inside WordPress rather than delegated to another automation platform. It adds unlimited Flows, conditionals, delays/scheduling, logs, data mapping/manipulation, advanced security features, premium extensions and the full Pro integration set.
WP Webhooks pricing
Pricing checked October 16, 2026. Starter costs $149/year for one site. Business costs $249/year for 10 sites and adds priority support. Agency costs $499/year for 75 sites and adds early release access, priority integration requests and on-page support. The pricing page lists a 14-day money-back guarantee, with taxes excluded.
The plugin does not charge per webhook execution, which can make it cost-predictable for high-volume sites compared with cloud automation platforms that meter every task.
Production checklist
- Authenticate every incoming endpoint that can change WordPress data.
- Use the least-privileged WordPress capability for exposed Abilities and MCP tools.
- Test webhook payloads with representative data, not only empty demo calls.
- Strip sensitive fields before sending user or order payloads to external services.
- Log and monitor failures for business-critical webhooks.
- Confirm retries do not create duplicate users, orders, posts or payments.
- Keep WP Webhooks updated because automation endpoints expand the site’s attack surface.
WP Webhooks vs AutomatorWP, Uncanny Automator and Bit Flows
AutomatorWP and Uncanny Automator are more recipe-centric for WordPress users who want prebuilt plugin triggers and actions. Bit Flows provides a more visual multi-step automation canvas with routers, loops, parsers and agent tooling.
WP Webhooks is strongest when the core requirement is API/webhook flexibility and developer-grade control over payloads, authentication and remote actions. Its new Abilities support also makes it particularly relevant for teams building AI/MCP access to WordPress functions.
Who should choose WP Webhooks?
Choose WP Webhooks when your main requirement is controlled data exchange between WordPress and other systems. It is especially suitable when you need custom payloads, authenticated endpoints, several HTTP methods, external APIs, or remote WordPress actions that do not fit neatly into a prebuilt recipe. The new Abilities support also makes it a logical choice when you are deliberately exposing a small set of WordPress capabilities to AI or MCP clients.
If your team is non-technical and the workflows mostly connect popular WordPress plugins, a recipe-first automator can be easier to understand. WP Webhooks rewards teams that are comfortable thinking in requests, payloads, authentication, permissions, and data contracts. That flexibility is its advantage, but it also means more responsibility for testing and security.
Design webhook retries to be idempotent
Retries are useful only when repeating a request is safe. A failed request that creates an order, user, payment record, or post can produce duplicates if the remote system completed the first request but the response was lost. For critical workflows, pass a stable external identifier or idempotency key where the destination supports it, and check for an existing record before creating another one. The same principle applies to MCP-exposed write actions: confirmation and permissions reduce risk, but the underlying action should still behave predictably if a client retries it.
PluginSuggest verdict
WP Webhooks is one of the strongest WordPress choices when you need to treat the site as an automation endpoint rather than only connect a few named plugins. The send/receive model is clear, authentication is built in, request formats are flexible, and Pro adds enough orchestration to build complete workflows locally.
Version 3.5.0 makes the plugin more important for AI tooling by turning approved actions into WordPress Abilities that can be surfaced through MCP. I would shortlist it for technical teams, agencies and integration-heavy sites, while simpler business users may prefer a more opinionated recipe builder.
WP Webhooks FAQs
Is WP Webhooks free?
Yes. The free plugin provides the core send/receive webhook engine, authentication, testing, multiple request methods and formats, and many WordPress actions and triggers.
What is the current WP Webhooks version?
The current WordPress.org release reviewed here is WP Webhooks 3.5.0, released October 7, 2026.
Can WP Webhooks receive data from Zapier, Make or n8n?
Yes. Incoming action URLs can accept requests from external automation platforms and APIs, subject to the action and authentication you configure.
Can WP Webhooks expose actions to AI assistants through MCP?
Yes. Version 3.5.0 can register selected actions as WordPress Abilities. With a compatible MCP server, approved abilities can become tools for MCP clients.
How can WP Webhooks endpoints be secured?
The plugin supports API Key, Bearer Token and Basic Auth. Pro adds additional controls such as IP whitelisting and access-token-related features.
Does WP Webhooks charge per automation run?
No per-execution task pricing is listed. The paid product is licensed by site count.
How much does WP Webhooks Pro cost?
As checked October 16, 2026, Starter is $149/year for one site, Business is $249/year for 10 sites, and Agency is $499/year for 75 sites.
Compare before you install
Similar Plugins
Connect WordPress plugins and external apps with no-code recipes, AI-assisted site tasks, advanced workflow logic, and an AI-first page builder.
Build multi-step WordPress automations with a visual workflow canvas, AI Agent, routers, APIs, webhooks, MCP, human approvals, logs, and hundreds…