The Webhooks Add-on for The Newsletter Plugin (TNP) for WordPress is designed to bridge the gap between your on-site subscriber activity and external services like CRMs (Salesforce, Hubspot), automation tools (Zapier, Make/Integromat), or custom API endpoints.
This is EXACTLY the same product as distributed by the developer. Sales Page
The add-on can trigger an HTTP callback based on three primary events:
New Subscription: Fired when a user successfully subscribes (or confirms their subscription if double opt-in is enabled).
Unsubscription: Fired when a subscriber clicks the “cancel” link or is manually removed.
Newsletter Sent (Completion): Fired once a campaign has finished sending to the entire list, allowing you to sync final stats or notify a team.
You can choose between two delivery formats for the data:
| Format | Description |
| Standard HTTP POST | Data is sent as form fields (application/x-www-form-urlencoded). Ideal for simple PHP scripts using $_POST. |
| Raw HTTP POST (JSON) | Data is sent as a JSON-encoded string in the request body. Preferred for modern APIs and automation platforms. |
When a subscriber-related event occurs, the payload includes:
id: Unique subscriber ID in the WordPress database.
email: The subscriber’s email address.
name / surname: First and last names.
sex: Gender (if collected).
list_N: Status of lists 1 through 40 (Value 1 if joined, 0 if not).
profile_N: Custom profile fields 1 through 20 (text values).
status: Current status (Confirmed, Unconfirmed, or Unsubscribed).
When a newsletter send is completed, the payload includes:
id: Internal newsletter ID.
subject: The email subject line.
message: The full HTML content of the newsletter.
stats: Total sent, open count, and click count (at the moment of completion).
Asynchronous Processing: Webhook calls are scheduled and sent via the plugin’s internal engine. This ensures that the user’s subscription process isn’t slowed down by waiting for a slow external API response.
Testing Tool: Each configured webhook includes a “Test” button that sends a dummy payload to your URL to verify the connection.
Logging & Debugging: Detailed logs are kept under Newsletter > System > Logs. If a webhook fails (e.g., 404 or 500 error), the reason is recorded there.
Security: Supports HTTPS endpoints to ensure data is encrypted during transit.
Core Plugin: Requires The Newsletter Plugin (Free or Premium version) installed on WordPress.
Add-on: This is typically part of the Premium/Professional license bundle from thenewsletterplugin.com.
Configuration Path: Found under Newsletter > Add-ons > Webhooks.
