WebEquipe Webhook Manager

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.
   • 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.
3. 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.