Actions42
- Campaigns Actions
- Create Campaign
- Create Template
- Duplicate Template
- Get Campaign Basic Information
- Get Campaign Clicks
- Get Campaigns
- Get Campaign Information By ISP
- Get Campaign Links
- Get Campaign Openers
- Get Campaign Openers By Browser
- Get Campaign Openers By Countries
- Get Campaign Openers By Os
- Get Campaign Soft Bounces
- Get Campaign Total Information
- Get Stats By Date
- Send Template Campaign
- Subscribers Actions
- SMS Actions
- SMTP Actions
- Webhooks Actions
Overview
This node integrates with the Acumbamail API to configure webhook settings related to mailing list events. Specifically, the "Config List Webhook" operation under the "Webhooks" resource allows users to set up a callback URL and specify which subscriber-related events should trigger webhook notifications.
Common scenarios for this node include:
- Automatically updating external systems when subscribers perform actions such as subscribing, unsubscribing, or when emails bounce.
- Tracking user engagement by receiving notifications on email opens and clicks.
- Handling complaint events to maintain mailing list hygiene.
For example, a marketing automation workflow could use this node to register a webhook that notifies the system whenever a subscriber opens an email or clicks a link, enabling real-time engagement tracking.
Properties
| Name | Meaning |
|---|---|
| Callback Url | The URL where webhook event data will be sent (the webhook callback endpoint). |
| Subscriber | Indicator (0 or 1) whether to receive notifications for new subscriber events. |
| Unsubscribe | Indicator (0 or 1) whether to receive notifications for unsubscribe events. |
| Hard Bounce | Indicator (0 or 1) whether to receive notifications for hard bounce email events. |
| Soft Bounce | Indicator (0 or 1) whether to receive notifications for soft bounce email events. |
| Complain | Indicator (0 or 1) whether to receive notifications for complaint events (e.g., spam). |
| Open | Indicator (0 or 1) whether to receive notifications for email open events. |
| Click | Indicator (0 or 1) whether to receive notifications for click events on links in emails. |
| Active | Indicator (0 or 1) whether to receive notifications for active subscriber events. |
Each indicator is a numeric flag (typically 0 or 1) specifying if the corresponding event type should trigger the webhook.
Output
The node outputs JSON data representing the response from the Acumbamail API after configuring the webhook. This typically includes confirmation of the webhook setup and details about the configured event indicators.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Acumbamail API.
- The node sends HTTP requests to
https://acumbamail.com/api/1. - Proper network connectivity to Acumbamail's API endpoint is necessary.
- The user must provide a valid callback URL accessible by Acumbamail to receive webhook events.
Troubleshooting
- Invalid Callback URL: If the callback URL is malformed or unreachable, the webhook configuration may fail. Ensure the URL is correct and publicly accessible.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly configured.
- Event Indicators Not Set Correctly: Using values other than 0 or 1 for event indicators might lead to unexpected behavior. Use only 0 (disable) or 1 (enable).
- API Rate Limits or Downtime: Temporary issues with Acumbamail's API can cause errors. Retry after some time or check Acumbamail's status page.
Error messages returned by the API are passed through; reading the message content usually helps identify the issue.
Links and References
- Acumbamail API Documentation
- Webhook Concepts and Best Practices
- n8n Documentation on Creating Custom Nodes