🎉 Save 10% Extra on the Webequipe PDF Search Plugin Annual Plan — Use code YEARLY10 · Limited-time offer · Get discount →

Home - Webhook Manager - Documentation

Documentation

Connect WordPress events with n8n, Zapier, Make, Slack, CRM platforms, or any custom webhook endpoint.

WebEquipe Webhook Manager captures form submissions, WooCommerce events, and WordPress action hooks, then sends structured data to one or more webhook URLs.

The plugin sends data only to the endpoints you configure. Nothing is sent through a WebEquipe service.

Key Features

  • Send form submissions to external platforms.
  • Capture WooCommerce order and payment events.
  • Capture action hooks from WordPress or other plugins.
  • Connect with n8n, Zapier, Make, Slack, CRMs, or custom servers.
  • Create reusable webhook connections.
  • Send all fields or select specific fields.
  • Rename payload fields and add static values.
  • Apply field-level transformations.
  • Add conditional delivery rules using AND/OR conditions.
  • Use Bearer Token, Basic Authentication, or custom headers.
  • Secure requests with HMAC-SHA256 signing.
  • View complete request and response logs.
  • Replay failed or successful webhook deliveries.
  • Export webhook logs as CSV.
  • View delivery statistics from the dashboard.
  • Store authentication details securely in WordPress.

Use Cases

  • Send website leads directly to a CRM.
  • Send form submissions to Slack or an internal system.
  • Connect WooCommerce orders with accounting or fulfilment tools.
  • Trigger n8n, Zapier, or Make automation workflows.
  • Send membership or course events to external platforms.
  • Connect custom WordPress plugins with external applications.
  • Track webhook delivery success and failure.
  • Build automated customer follow-up processes.

Upcoming Features

  • Dedicated Elementor Forms and Bricks Forms integrations.
  • LearnDash and MemberPress integrations.
  • Ready-to-use webhook templates for n8n, Zapier, and Slack.
  • Scheduled webhook triggers using WP-Cron.

Why Choose WebEquipe Webhook Manager

Connect WordPress to your preferred automation platform without building a custom integration for every event.

The plugin supports popular forms and WooCommerce, while its generic WordPress hook option allows you to capture events from other plugins and custom functionality.

You stay in control of your data because webhook payloads are sent directly from your WordPress website to the endpoints you configure.

Privacy Policy

WebEquipe Webhook Manager may process and store information included in webhook events.

This information may include:

  • Form field values such as name, email address, phone number, and messages.
  • WooCommerce order or customer information.
  • Request URLs, headers, and request bodies.
  • Response headers, response codes, and response bodies.
  • IP address or user-agent information provided by certain triggers.
  • Authentication tokens and HMAC signing secrets.

Webhook payloads are sent only to the third-party endpoints configured by the website administrator.

Authentication tokens and signing secrets are encrypted when stored.

Delivery logs remain inside the website’s WordPress database. The website administrator can control how long logs are stored from the plugin settings.

Plugin data can be removed during uninstall by enabling the Remove all data on uninstall option before deleting the plugin.

Website owners should update their privacy policy based on the information they collect and the external services they connect with.

Configuration

Quick Start Guide

After installing and activating the plugin, follow these steps to create your first webhook.

Step 1: Create a Connection

A connection stores the destination details where webhook data will be sent.

  1. Go to Webhook Manager → Connections.
  2. Click Add Connection.
  3. Enter a name for the connection.
  4. Add the destination webhook URL.
  5. Select the required HTTP method.
  6. Configure authentication if the receiving platform requires it.
  7. Save the connection.

You can use services such as webhook testing tools or an n8n test webhook while configuring your first connection.

Step 2: Configure Connection Settings

  1. Basic Information
    1. Connection Name: Enter a clear name for your connection (e.g., “n8n Lead Workflow” or “Slack Notifications”).
    2. Destination URL: Enter the URL that will receive the webhook.
    3. HTTP Method: Select the request method required by the receiving endpoint.
    4. Content Type: Choose the data format expected by the receiving platform.
  2. Authentication
    1. Configure authentication only if required by your endpoint.
    2. Authentication Type: Choose the authentication method:
      • Bearer Token: Authenticate using a token.
      • Basic Authentication: Authenticate using a username and password.
      • Custom Request Headers: Add custom authentication or request headers.
      • HMAC Signing Secret: Sign webhook requests using a secret key.
  3. Additional Settings
    1. Request Timeout: Set how long the system should wait for a response.
    2. SSL Verification: Enable or disable SSL certificate verification.
    3. Custom Headers: Add any additional headers required by the receiving platform.
    4. Test Connection: Test the connection before using it with a live webhook.

Step 3: Create Your First Webhook

  1. Go to Webhook Manager → Webhooks.
  2. Click Add Webhook.
  3. Enter a name for the webhook.
  4. Continue to the trigger selection.
  5. Configure the payload and conditions.
  6. Select one or more connections.
  7. Enable and save the webhook.

Step 4: Choose a Trigger

Select the WordPress event that should send the webhook.

  1. Form Submission
    • Supported form plugins include:
      • Contact Form 7
      • WPForms
      • Fluent Forms
      • Formidable Forms
      • Ninja Forms
    • Select the form plugin and the relevant form where available.
  2. WooCommerce Event
    • Choose the WooCommerce event that should trigger the webhook, such as an order, payment, refund, or order-status change.
  3. WordPress Action Hook
    • Use this option to capture an event from WordPress, another plugin, or custom functionality.
    • You can search active plugins to find available WordPress action hooks.
  4. Manual Trigger
    • Use a manual trigger when the webhook should be started directly from the plugin instead of waiting for a website event.

Step 5: Configure the Payload

The payload controls the information sent to the receiving endpoint.

You can:

  • Send all available fields.
  • Select only the fields you need.
  • Rename field keys.
  • Add static fields or labels.
  • Apply supported field transformations.
  • Remove unnecessary plugin or security fields.

Use clear field names so the receiving workflow can understand the data easily.

Step 6: Add Delivery Conditions

Conditions allow the webhook to run only when specific field values match your rules.

For example:

  • Send only when the order total is above a specific value.
  • Send only when a selected form option equals “Sales.”
  • Skip the webhook when a required value is empty.
  • Send only when an order reaches a specific status.

Multiple conditions can be combined using:

  • AND: Every condition must match.
  • OR: At least one condition must match.

Conditions are optional. Without conditions, the webhook will run every time the selected trigger fires.

Step 7: Select Connections

Select one or more saved connections where the webhook should be delivered.

The same event can be sent to multiple destinations. For example, a new form submission can be sent to both n8n and Slack.

Make sure at least one connection is selected before enabling the webhook.

Step 8: Save and Test

  1. Enable the webhook.
  2. Click Save.
  3. Use Send Test if available.
  4. Alternatively, perform the real website action, such as submitting the selected form.
  5. Go to Webhook Manager → Logs.
  6. Confirm that the request was delivered successfully.
  7. Review the response from the receiving endpoint.

Managing Connections

Go to Webhook Manager → Connections to view all saved destinations.

From this page, you can:

  • Add a new connection.
  • Edit an existing connection.
  • Test a connection.
  • Update authentication details.
  • Change the destination URL.
  • Disable or remove a connection.

Before removing a connection, confirm that it is not being used by an active webhook.

List and Edit Webhooks

Go to Webhook Manager → Webhooks to view all configured webhooks.

From the webhook list, you can:

  • View the webhook name and trigger.
  • Check whether the webhook is enabled.
  • Edit webhook settings.
  • Change the selected connections.
  • Update payload fields.
  • Add or change conditions.
  • Send a test delivery.
  • Disable or delete the webhook.

Changes can be made at any time. Always test the webhook again after changing its trigger, connection, authentication, or payload settings.

Viewing and Managing Logs

Go to Webhook Manager → Logs to review webhook deliveries.

Each log can include:

  • Delivery date and time.
  • Webhook name.
  • Trigger or source.
  • Selected connection.
  • Delivery status.
  • HTTP response code.
  • Request URL.
  • Request headers.
  • Request body.
  • Response headers.
  • Response body.

Available actions may include:

  • View the complete log.
  • Copy request or response data.
  • Replay a webhook delivery.
  • Filter logs by webhook, connection, status, or date.
  • Export log information as CSV.

A successful delivery normally displays a successful HTTP response status. Failed deliveries should be reviewed to identify connection, authentication, payload, or server issues.

Dashboard

The Webhook Manager dashboard provides a quick overview of webhook activity.

It can display:

  • Total webhook deliveries.
  • Successful deliveries.
  • Failed deliveries.
  • Skipped deliveries.
  • Recent webhook activity.
  • Delivery performance over recent days.

Use the dashboard to identify repeated failures or unexpected changes in webhook activity.

Settings

Go to Webhook Manager → Settings to manage general plugin behaviour.

Available settings may include:

  • Enable asynchronous webhook delivery.
  • Configure delivery timeout.
  • Set the log retention period.
  • Control whether plugin data is removed during uninstall.
  • Manage other delivery and storage preferences.

Asynchronous delivery can prevent the webhook request from delaying the original WordPress action. However, it depends on WP-Cron running correctly on the website.

Testing Your Setup

Before using a webhook on a live website:

  1. Test the connection: Confirm that the destination URL is correct and reachable.
  2. Test authentication: Check Bearer Tokens, Basic Authentication, and custom headers.
  3. Test the trigger: Perform the real form, WooCommerce, or WordPress action.
  4. Check the payload: Confirm that all required fields are included.
  5. Review conditions: Verify that the webhook runs or skips correctly.
  6. Check the logs: Review the request, response, and HTTP status.
  7. Test failed delivery: Temporarily use an invalid endpoint to confirm that failures appear in the logs.
  8. Test replay: Replay a delivery and confirm that it reaches the destination.
  9. Test on staging: Complete testing on a staging website before enabling important production workflows.

Troubleshooting

Test Says “Could Not Reach the Server”

  • Confirm that the destination URL is correct.
  • Check whether the receiving server is online.
  • Confirm that the endpoint can be reached from your WordPress server.
  • Review authentication details.
  • Check the response information in the Logs screen.
  • Confirm that SSL verification is compatible with the endpoint.

No Log Entries Appear

  • Confirm that the webhook is enabled.
  • Make sure the correct trigger is selected.
  • Confirm that the selected form, WooCommerce event, or action hook matches the event being tested.
  • Make sure at least one connection is selected.
  • Check whether the delivery conditions are causing the webhook to be skipped.
  • Review the WordPress error log if the issue continues.

GET Request Does Not Include a Body

GET and HEAD requests normally do not send a request body.

Use POST, PUT, or PATCH when the receiving endpoint requires payload data in the request body.

Authentication Fails

  • Confirm that the token, username, or password is correct.
  • Check whether “Bearer” is required before the token.
  • Confirm that custom header names match the receiving platform’s requirements.
  • Make sure the secret has not expired.
  • Test the endpoint outside the live workflow where possible.

Webhook Is Skipped

  • Review the configured delivery conditions.
  • Confirm that the event includes the fields used in the conditions.
  • Check whether AND/OR logic is configured correctly.
  • Review the log to identify which condition did not match.

Deliveries Are Slow

  • Reduce the connection timeout.
  • Enable asynchronous delivery from the plugin settings.
  • Confirm that WP-Cron is working correctly.
  • Check whether the receiving endpoint is responding slowly.
  • Review server performance and external API response times.

HMAC Verification Fails

When an HMAC signing secret is configured, the plugin sends a signature header similar to:

X-WEWM-Signature: t=<unix>, v1=<hex>

The receiving system should:

  1. Read the timestamp from t.
  2. Read the received raw request body.
  3. Create the signed value using timestamp.rawBody.
  4. Generate the SHA-256 HMAC using the shared signing secret.
  5. Compare the generated signature with v1 using a secure constant-time comparison.

Make sure the receiving platform uses the raw body before JSON parsing or formatting changes.

Third-Party Services

WebEquipe Webhook Manager does not automatically connect with or send information to any predefined third-party service.

Data is transmitted only to webhook endpoint URLs configured by the website administrator.

The website administrator is responsible for reviewing the terms, security requirements, and privacy policy of services such as:

  • n8n
  • Zapier
  • Make
  • Slack
  • CRM systems
  • Email-marketing platforms
  • Custom APIs or servers

Frequently Asked Questions

Which form plugins are supported?

The plugin supports Contact Form 7, WPForms, Fluent Forms, Formidable Forms, and Ninja Forms.

WooCommerce events and WordPress action hooks are also supported.

Does it work with other WordPress plugins?

Yes. When another plugin fires a standard WordPress action hook, you can use the generic WordPress hook trigger to capture that event.

Does the plugin send my data anywhere by default?

No. The plugin sends data only to the endpoint URLs configured by the website administrator.

Nothing is automatically sent to WebEquipe.

Where are delivery logs stored?

Delivery logs are stored in the website’s own WordPress database.

The administrator can configure the log retention period from the plugin settings.

Does it provide shortcodes or blocks?

No shortcode or front-end block is required. Webhooks are configured and managed from the WordPress admin dashboard.

Can one webhook send data to multiple destinations?

Yes. One webhook can be connected to one or more saved connections.

Can failed webhooks be sent again?

Yes. Delivery logs include an option to replay webhook requests.

Product: WebEquipe Webhook Manager

Documentation URL: /webhook-manager/doc/

Last Updated: July 27, 2026