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 configures an SMTP webhook by sending a set of event indicators and a callback URL to a specified endpoint. It is useful for integrating email event tracking into workflows, such as monitoring delivery status, bounces, complaints, opens, clicks, and active events related to emails sent via SMTP.
Typical use cases include:
- Setting up webhooks to receive real-time notifications about email delivery and engagement.
- Automating responses or logging based on email event statuses.
- Integrating with third-party services that require webhook configuration for SMTP events.
For example, you might configure this node to send a callback URL along with flags indicating which email events (delivered, hard bounce, soft bounce, etc.) should trigger webhook calls, enabling your workflow to react accordingly.
Properties
| Name | Meaning |
|---|---|
| Callback Url | The URL for the webhook callback where event data will be sent. |
| Delivered | Indicator for delivered emails (numeric flag). |
| Hard Bounce | Indicator for hard bounce events (numeric flag). |
| Soft Bounce | Indicator for soft bounce events (numeric flag). |
| Complain | Indicator for complaint events (numeric flag). |
| Open | Indicator for open events (numeric flag). |
| Click | Indicator for click events (numeric flag). |
| Active | Indicator for active events (numeric flag). |
Each numeric indicator likely acts as a boolean flag (0 or 1) to enable or disable the corresponding event type in the webhook configuration.
Output
The node outputs JSON data representing the response from the webhook configuration request. This typically includes confirmation of the webhook setup or any error messages returned by the target service.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authentication with the Acumbamail API service.
- The node uses the Acumbamail API base URL
https://acumbamail.com/api/1. - Proper network access to the callback URL and Acumbamail API endpoints is necessary.
Troubleshooting
- Invalid Callback URL: Ensure the callback URL is correctly formatted and accessible from the internet.
- Authentication Errors: Verify that the API key credential is valid and has sufficient permissions.
- Event Flags Not Working: Confirm that numeric flags are set correctly (usually 0 or 1).
- Network Issues: Check connectivity to both the Acumbamail API and the callback URL.
- API Response Errors: Review the JSON output for error messages from the API to diagnose issues.
Links and References
- Acumbamail API Documentation (for detailed webhook configuration and event types)
- n8n Documentation on Webhook Nodes (general webhook usage guidance)