Title: WebEquipe Webhook Manager
Author: WebEquipe
Published: July 24, 2026
Last modified: July 24, 2026
---
Search plugins
# WebEquipe Webhook Manager
By [WebEquipe](https://profiles.wordpress.org/webequipe/)
[Download](https://downloads.wordpress.org/plugin/webequipe-webhook-manager.1.0.2.zip)
* [Details](https://wordpress.org/plugins/webequipe-webhook-manager/#description)
* [Reviews](https://wordpress.org/plugins/webequipe-webhook-manager/#reviews)
* [Installation](https://wordpress.org/plugins/webequipe-webhook-manager/#installation)
* [Development](https://wordpress.org/plugins/webequipe-webhook-manager/#developers)
[Support](https://wordpress.org/support/plugin/webequipe-webhook-manager/)
## Description
WebEquipe Webhook Manager captures events from forms, WooCommerce, and any WordPress
action hook, then delivers normalized JSON (or form-encoded) payloads to one or
more webhook endpoints you define.
It is built around two concepts:
* **Connections** — reusable destinations (URL, HTTP method, content type, authentication,
custom headers, timeout, SSL verification, optional HMAC signing secret).
* **Webhooks** — rules that map a trigger (a form submission, a WooCommerce event,
or a WordPress action hook) to one or more connections, with optional payload
shaping and conditions.
**Key features**
* Triggers: form submissions (Contact Form 7, WPForms, Fluent Forms, Formidable
Forms, Ninja Forms), WooCommerce events, and any WordPress action hook (with
an on-demand hook picker).
* Payload shaping: send all fields, pick a subset, or remap field keys; inject
static fields; apply per-field transforms.
* Conditional delivery: only send when field conditions match (AND/OR).
* Authentication: Bearer token, Basic auth, custom headers, and HMAC-SHA256 request
signing.
* Delivery logging with request/response capture, replay, and CSV export.
* Dashboard with delivery stats and recent activity.
* Secrets (auth tokens, signing secrets) are encrypted at rest.
This plugin does not connect to any WebEquipe service. It only sends data to the
endpoints **you** configure.
### Getting Started
1. **Create a connection.** Webhook Manager Connections Add Connection. Enter a
name and the destination URL. For testing you can use a service such as a request-
bin endpoint. Add authentication only if your endpoint requires it.
2. **Create a webhook.** Webhook Manager Webhooks Add Webhook.
3. * Step 1: name the webhook.
* Step 2: choose a trigger (Form submission, WooCommerce event, WordPress action
hook, or Manual). For action hooks you can search active plugins for available
hooks.
* Step 3–5: optionally shape the payload, add static fields/transforms, and add
delivery conditions.
* Choose one or more connections and enable the webhook.
4. **Test it.** Use **Send Test** on the webhook, or perform the real action, then
review **Logs**.
### Troubleshooting
* **Test says “could not reach the server”.** Verify the URL is correct and reachable
from your server, and that any required authentication is set. Check the Logs
screen for the captured response.
* **No log entries appear.** Confirm the webhook is enabled, the trigger/source
matches the event, and at least one connection is selected.
* **GET requests.** A request body is not sent with GET/HEAD requests; use POST/
PUT/PATCH to send a body.
* **Deliveries are slow.** Reduce the connection timeout, or enable asynchronous
delivery in Settings.
### Privacy
This plugin stores and transmits data that may include personal information:
* **Delivery logs** may contain submitted form field values (which can include
names, email addresses, and other personal data), the request URL, request/response
headers, and request/response bodies. Some triggers (for example Contact Form
7) may include the submitter’s IP address and user agent.
* **Outbound payloads** are sent to the third-party endpoints you configure. The
contents and the receiving party are entirely under your control.
* **Stored secrets** (authentication tokens and HMAC signing secrets) are encrypted
at rest.
You control retention via the log retention setting, and you can permanently remove
all plugin data on uninstall by enabling “Remove all data on uninstall” in Settings
before deleting the plugin. Because payloads are delivered to external services
that you choose, review those services’ privacy practices and disclose them in your
own site’s privacy policy as needed.
### Third-Party Services
This plugin does not bundle or call any predefined third-party service. It transmits
data only to the webhook endpoint URLs that the site administrator configures. You
are responsible for the terms and privacy policy of any endpoint you send data to.
## Screenshots
[⌊Dashboard with delivery stats and recent activity.⌉⌊Dashboard with delivery stats
and recent activity.⌉[
Dashboard with delivery stats and recent activity.
[⌊Connections list.⌉⌊Connections list.⌉[
Connections list.
[⌊Webhook editor.⌉⌊Webhook editor.⌉[
Webhook editor.
[⌊Logs with replay and CSV export.⌉⌊Logs with replay and CSV export.⌉[
Logs with replay and CSV export.
## Installation
1. Upload the plugin to `/wp-content/plugins/` or install it from the Plugins screen,
then activate it.
2. Go to **Webhook Manager Connections** and add a connection (the destination URL
and any authentication).
3. Go to **Webhook Manager Webhooks** and add a webhook: choose a trigger, select
the connection(s), and (optionally) shape the payload.
4. Use the **Test Connection** / **Send Test** buttons to confirm delivery.
5. Trigger the real event and confirm a success entry under **Webhook Manager Logs**.
## FAQ
### Which form plugins are supported?
Contact Form 7, WPForms, Fluent Forms, Formidable Forms, and Ninja Forms. WooCommerce
events and arbitrary WordPress action hooks are also supported.
### How do I verify the HMAC signature on the receiving end?
When a signing secret is set, requests include a header `X-WEWM-Signature: t=, v1=`. Recompute `hash_hmac('sha256', "$t.$rawBody", $secret)` and compare
it to `v1` using a constant-time comparison.
### Does the plugin send my data anywhere by default?
No. Payloads are sent only to the connection URLs you configure. Nothing is sent
to the plugin author.
### Where are delivery logs stored?
In custom database tables in your own WordPress database. You can set a retention
period and export or replay logs from the Logs screen.
### Does it provide shortcodes or blocks?
No. The plugin is configured entirely from the WordPress admin and does not register
shortcodes or blocks.
## Reviews
There are no reviews for this plugin.
## Contributors & Developers
“WebEquipe Webhook Manager” is open source software. The following people have contributed
to this plugin.
Contributors
* [ WebEquipe ](https://profiles.wordpress.org/webequipe/)
[Translate “WebEquipe Webhook Manager” into your language.](https://translate.wordpress.org/projects/wp-plugins/webequipe-webhook-manager)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/webequipe-webhook-manager/),
check out the [SVN repository](https://plugins.svn.wordpress.org/webequipe-webhook-manager/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/webequipe-webhook-manager/)
by [RSS](https://plugins.trac.wordpress.org/log/webequipe-webhook-manager/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 1.0.2
* Security: file publishing (URL file mode) enforces a MIME/extension allowlist
before copying uploads to the public uploads folder; unknown types and executable/
script files (php, phtml, phar, exe, js, svg, html, …) are rejected.
* Fix: Logs list and detail always query the database directly (no stale object-
cache empty lists).
* Fix: action-hook logs match hook-name filters; list queries no longer depend
on a JOIN to wewm_webhooks.
* Fix: default Logs list uses a direct paginated DB query (same reliability as
log detail view).
* Fix: webhook detail Logs tab uses direct webhook_id queries instead of the complex
filter SQL.
* Fix: delivery logging auto-recovers when enable logging was accidentally stored
off on new installs.
* Admin warning on the Logs screen when delivery logging is disabled in Settings.
#### 1.0.1
* Form save validation for webhooks and connections (server-side and client-side).
* Admin error notices when required fields are missing on save.
* Manual trigger label updated to “Manual” (was “Manual / test”).
* Delivery logs redact sensitive request/response headers (Authorization, X-WEWM-
Signature, API keys).
* Log settings now enforced: enable logging, payload snapshots, and response snippets.
* WordPress.org compliance: conditional asset loading, no inline admin CSS, sanitized
webhook validation input.
* Fix: delivery logging no longer silently stops when enable logging was stored
off before 1.0.1; connection tests now create log entries.
* Fix: fresh installs auto-create log tables, correct logging checkbox saves, and
show pending log rows for async deliveries.
#### 1.0.0
* Initial release.
## Meta
* Version **1.0.2**
* Last updated **19 hours ago**
* Active installations **Fewer than 10**
* WordPress version ** 6.0 or higher **
* Tested up to **7.0.2**
* PHP version ** 7.4 or higher **
* Tags
* [automation](https://wordpress.org/plugins/tags/automation/)[forms](https://wordpress.org/plugins/tags/forms/)
[integration](https://wordpress.org/plugins/tags/integration/)[webhook](https://wordpress.org/plugins/tags/webhook/)
[woocommerce](https://wordpress.org/plugins/tags/woocommerce/)
* [Advanced View](https://wordpress.org/plugins/webequipe-webhook-manager/advanced/)
## Ratings
No reviews have been submitted yet.
[Your review](https://wordpress.org/support/plugin/webequipe-webhook-manager/reviews/#new-post)
[See all reviews](https://wordpress.org/support/plugin/webequipe-webhook-manager/reviews/)
## Contributors
* [ WebEquipe ](https://profiles.wordpress.org/webequipe/)
## Support
Got something to say? Need help?
[View support forum](https://wordpress.org/support/plugin/webequipe-webhook-manager/)