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 an email service API to retrieve the status of a specific email by using its unique key (referred to as "Email Key"). It is useful in scenarios where you need to programmatically check whether an email has been sent, delivered, opened, or encountered any issues. For example, marketing automation workflows can use this node to track email campaign performance or trigger follow-up actions based on email delivery status.
Properties
| Name | Meaning |
|---|---|
| Email Key | The unique identifier (password) of the email whose status you want to check. This value is required and is sent as a query parameter in the API request. |
Output
The node outputs JSON data containing the status information of the requested email. The exact structure depends on the external API response but typically includes fields such as delivery status, timestamps, error messages if any, and other metadata related to the email's lifecycle.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential for authentication with the external email service.
- The base URL for API requests is
https://acumbamail.com/api/1. - The node uses HTTP headers specifying
Accept: application/jsonandContent-Type: application/json. - The node depends on an OpenAPI specification (
openapi.json) bundled with the node for defining available operations and properties.
Troubleshooting
- Common Issues:
- Invalid or missing Email Key will likely result in an error or empty response.
- Authentication failures due to incorrect or missing API credentials.
- Network connectivity issues preventing access to the external API endpoint.
- Error Messages:
- Errors returned from the API may include unauthorized access, not found (if the email key does not exist), or rate limiting.
- Resolutions:
- Ensure the Email Key is correctly provided and corresponds to an existing email.
- Verify that the API key credential is configured properly in n8n.
- Check network settings and firewall rules to allow outbound HTTPS requests to the API domain.
Links and References
- Acumbamail API Documentation (for detailed API endpoints and response formats)
- n8n Documentation (for general guidance on creating and using custom nodes)