AvantGuard - Acumbamail icon

AvantGuard - Acumbamail

AvantGuard - Acumbamail

Overview

This node integrates with the Acumbamail API to retrieve information about campaign openers. Specifically, for the "Campaigns" resource and the "Get Campaign Openers" operation, it fetches data on users who have opened a particular email campaign. This is useful for marketing teams or automation workflows that need to analyze engagement metrics or trigger follow-up actions based on campaign interaction.

Practical examples include:

  • Automatically segmenting contacts who opened a campaign for targeted follow-ups.
  • Generating reports on campaign performance.
  • Triggering notifications or other workflows when a campaign reaches a certain number of openers.

Properties

Name Meaning
Campaign Id Identifier of the campaign to retrieve opener information for. Must be provided as a number.

Output

The node outputs JSON data containing details about the campaign openers. The structure typically includes information such as user identifiers, timestamps of when they opened the campaign, and possibly metadata related to their interaction.

If the node supports binary data output (not evident from the provided code), it would represent attachments or files related to the campaign openers, but this is not indicated here.

Dependencies

  • Requires an API key credential for authenticating with the Acumbamail API.
  • The base URL for API requests is https://acumbamail.com/api/1.
  • The node uses standard HTTP headers for JSON content (Accept: application/json and Content-Type: application/json).
  • No additional external dependencies are indicated beyond the Acumbamail API and its authentication.

Troubleshooting

  • Missing or invalid Campaign Id: Ensure the Campaign Id property is set and corresponds to an existing campaign in Acumbamail.
  • Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • API connectivity issues: Check network access to https://acumbamail.com/api/1 and ensure no firewall or proxy blocks the requests.
  • Unexpected API responses: Confirm that the campaign exists and that the API endpoint supports retrieving openers for that campaign.

Common error messages might include authorization failures, resource not found, or invalid parameter errors. Resolving these usually involves verifying credentials, input parameters, and API availability.

Links and References

Discussion