Dynamic Webhook Automator for MemberPress helps WordPress membership sites connect MemberPress activity with the other tools their business depends on.

When something important happens in MemberPress, this plugin can automatically send the right information to another system. For example, you can send new member details to a CRM, notify your team about failed payments, update a reporting system after a transaction, or trigger an automation platform when a subscription changes.

The plugin adds a Webhook Automations area to each MemberPress Membership. From there, you can create one or more webhook rules that decide when data should be sent, where it should go, what information should be included, and how failed deliveries should be handled.

You do not need the MemberPress Developer Tools add-on to use this plugin.

Built for MemberPress membership automation

MemberPress is powerful for selling and managing memberships. Many businesses also need membership data to move into other systems, including:

CRM platforms
Email marketing tools
Automation platforms
Internal dashboards
Reporting systems
Accounting workflows
Support and onboarding tools
Custom business applications

Dynamic Webhook Automator for MemberPress gives you a structured way to send that data without hard-coding every integration.

Create multiple webhook rules per membership

Each MemberPress Membership can have multiple independent webhook rules.

For example, one membership can:

Send new member details to a CRM.
Send completed payment details to a reporting tool.
Notify an internal workflow when a recurring payment fails.
Trigger an automation when a subscription is paused or resumed.

Each rule has its own event, endpoint URL, payload fields, authentication settings, retry policy, and logging preferences.

Choose the MemberPress events that matter

Create webhook automations for important membership activity, such as:

Member added
Member signup completed
Transaction completed
Transaction status complete
Renewal transaction completed
Recurring transaction completed
Recurring transaction failed
Transaction refunded
Subscription created
Subscription paused
Subscription resumed
Subscription stopped
Subscription expired

This helps your external systems stay updated when members join, pay, renew, cancel, pause, resume, or run into billing issues.

Transaction status complete is a separate MemberPress hook. Do not configure it alongside Transaction completed for the same receiver unless you need one delivery from each trigger.

Send exactly the data the receiving app needs

Every webhook rule includes payload mapping. This means you choose the fields that should be sent and where each value should come from.

You can include data such as:

Member name
Member email
User ID
Membership ID
Membership title
Transaction ID
Transaction status
Transaction total
Subscription status
Event name
Event ID
Site name
Site URL
Static values that you type yourself
Dates and date/time values
Tags or fixed labels

This gives non-technical administrators a clearer way to shape webhook data for CRMs, automation tools, and business systems.

Static values, dates, and custom labels

Not every field needs to come from MemberPress. You can also send static values.

Examples include:

Campaign name
Department
Internal source label
CRM tag
Fixed status value
Custom date
Custom date and time

Static values are useful when the receiving app needs extra context that does not already exist in MemberPress.

Transform values before sending

Some receiving systems require data in a specific format. The plugin supports value transformations so your webhook payload can be cleaner and more useful.

Examples include:

Trim extra spaces
Convert text to lowercase
Convert text to uppercase
Convert comma-separated text into a list
Convert a list into comma-separated text
Format dates
Convert values into numbers
Convert values into true or false
Add a prefix or suffix
Normalize phone numbers
Hash a value with SHA-256

Decide what happens when data is missing

Sometimes a value may not be available for a specific MemberPress event. For each payload field, you can choose how the plugin should handle missing data.

Options include:

Skip the field
Send an empty value
Send null
Use a default value
Stop the webhook because the value is required

This helps prevent incomplete or incorrect data from being sent by mistake.

Start faster with webhook presets

Webhook presets provide a ready-made starting point for common workflows.

Instead of starting with a blank webhook rule, you can choose a preset, review its guidance, and customize it for your site.

You can still create a blank webhook rule whenever you want full control.

Secure webhook authentication

Different receiving systems require different authentication methods. The plugin supports common webhook authentication options, including:

No authentication
HMAC SHA-256 signing
Bearer token
Basic authentication
Custom secret header
Custom request headers

Saved secrets are not shown back in the admin screen. Rules store secret references instead of plain text secrets.

HMAC signed webhook requests

For systems that need to confirm a webhook really came from your WordPress site, the plugin can sign requests using HMAC SHA-256.

This helps the receiving system reject fake, modified, or untrusted requests.

Test webhook rules before using them live

You can send a test webhook from the admin area.

Testing helps confirm that:

The endpoint URL is correct.
Authentication is configured correctly.
The payload contains the expected fields.
The receiving app accepts the request.

Test deliveries are marked separately from normal live webhook deliveries.

Background delivery that protects checkout performance

Webhook requests are sent in the background.

The plugin does not make remote webhook requests directly inside sensitive MemberPress checkout, payment, or event requests. Instead, it stores a delivery record and processes the webhook through a queue.

This helps avoid slowing down the member checkout experience.

Retry temporary failures automatically

If a webhook fails because of a temporary problem, the plugin can retry it.

Temporary problems can include:

Network errors
Timeouts
Rate limits
Temporary server errors from the receiving app

The plugin does not retry forever. After the retry limit is reached, the delivery can be reviewed.

Duplicate protection

The plugin includes duplicate protection so the same event and webhook rule combination is not accidentally processed multiple times as a new delivery.

Webhook requests also include an idempotency key, which helps receiving systems avoid duplicate processing.

Delivery logs for visibility

Delivery logs help administrators understand what happened.

Logs can help answer:

Was the webhook sent?
Which rule sent it?
Did the receiving app accept it?
What status code came back?
Did the request fail temporarily or permanently?

Sensitive information such as tokens, signatures, authorization headers, cookies, passwords, and secrets should be redacted from logs.

Designed with security and privacy in mind

Webhook automation can involve personal data and external requests, so the plugin is designed with practical safety controls.

Security-focused behavior includes:

HTTPS-first webhook URLs
Safer URL validation
Protection against unsafe local and private network destinations
Limited redirects
Bounded request timeouts
Secret references instead of plain text rule secrets
Redaction of sensitive values in logs and errors
Dedicated permissions for managing settings, logs, secrets, tests, and retries

Site owners should still review their privacy obligations and disclose any external data sharing where required.

Who should use this plugin?

Dynamic Webhook Automator for MemberPress is useful for:

Membership site owners
Agencies building MemberPress websites
Operations teams
Marketing teams
CRM administrators
Developers who want a structured webhook system for MemberPress

Example use cases

Send new members to a CRM:

When someone signs up, send their name, email address, membership name, and signup event ID to your CRM.

Notify your team about failed payments:

When a recurring payment fails, send the member email, subscription status, and membership name to an internal workflow.

Update an external reporting system:

When a transaction is completed, send the transaction ID, total, membership ID, and member email to a reporting tool.

Trigger an automation platform:

When a subscription is paused or resumed, send the event details to an automation platform so it can update tags, send emails, or start a workflow.

Add fixed business context:

Send static values such as campaign name, source label, department, tags, custom dates, or fixed status values along with MemberPress data.

Privacy

This plugin does not send data to a service controlled by the plugin author.
Administrators can configure webhook endpoints operated by third parties. Depending on the configured payload, webhook requests may include personal data such as names, email addresses, membership information, transaction information, subscription information, and user metadata.
No webhook data is transmitted until an administrator creates and enables a webhook rule. Site owners are responsible for reviewing the privacy policies and data-processing requirements of their configured webhook recipients.
The plugin may retain delivery records and response metadata in the WordPress database. Sensitive headers and configured secrets are redacted from logs.