AvantGuard - Acumbamail icon

AvantGuard - Acumbamail

AvantGuard - Acumbamail

Actions42

Overview

This node allows sending a single email via SMTP using the AvantGuard Acumbamail service. It is designed for scenarios where you want to programmatically send transactional or notification emails from workflows, such as order confirmations, password resets, or alerts.

Typical use cases include:

  • Sending a custom email to a specific recipient with a defined subject and body.
  • Using an email template with merge tags to personalize content dynamically.
  • Scheduling an email to be sent at a future date/time.
  • Adding CC or BCC recipients for broader distribution.

Properties

Name Meaning
From Email The sender's email address.
To Email The recipient's email address.
Subject The subject line of the email.
Additional Body Fields Optional fields including:
- Cc Email Email addresses to send a carbon copy (optional).
- Bcc Email Email addresses to send a blind carbon copy (optional).
- Body The main content of the email (use this or Template Id).
- Template Id ID of the email template to use (optional; mutually exclusive with Body).
- Merge Tags JSON dictionary of key-value pairs to replace placeholders in the template (optional).
- Category A category label for the email (optional).
- Program Date Scheduled date and time to send the email (optional; format: DD/MM/YYYY HH:MM).

Output

The node outputs JSON data representing the result of the email sending operation. This typically includes status information confirming whether the email was successfully sent or if there were errors. No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard Acumbamail service.
  • The node uses the Acumbamail API endpoint https://acumbamail.com/api/1.
  • Proper configuration of the API key credential within n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Incorrect email addresses may lead to delivery errors.
    • Providing both body and template_id simultaneously might cause conflicts; only one should be used.
    • Improperly formatted program_date can prevent scheduling.

  • Error messages:

    • Authentication errors usually indicate invalid or missing credentials; verify API key setup.
    • Validation errors on email fields suggest incorrect formatting; ensure valid email syntax.
    • Template-related errors may occur if the template ID does not exist or merge tags are malformed; check template availability and JSON structure.

Links and References

Discussion