Actions32
- Campaign Actions
- List Actions
- Media Actions
- Setting Actions
- Subscriber Actions
- Template Actions
- Transaction Actions
Overview
The node integrates with a Listmonk instance to send transactional emails. Specifically, the "Send a Transactional Email" operation allows users to dispatch templated emails to subscribers using predefined templates and subscriber information. This is useful in scenarios such as sending order confirmations, password resets, or any automated email triggered by user actions or system events.
Practical examples:
- Sending a welcome email to a new subscriber immediately after signup.
- Dispatching a receipt or invoice after a purchase.
- Notifying users about account changes or alerts.
Properties
| Name | Meaning |
|---|---|
| Template ID | The numeric identifier of the email template to use for the transactional email. |
| Subscriber ID | The numeric identifier of the subscriber who will receive the email. |
| Sender Email | The email address that will appear as the sender of the transactional email. |
| Messenger | The messenger channel to use; currently supports "email". |
| Content Type | The format of the email content. Options: HTML, Markdown, Plain text. |
| Data | Optional JSON object containing nested data to populate dynamic fields within the template. |
Output
The node outputs JSON data representing the result of the transactional email send operation. This typically includes status information such as success confirmation or error details. There is no indication of binary data output.
Dependencies
- Requires connection to a Listmonk API instance.
- Needs credentials including domain URL, username, and password for authentication.
- The node expects the Listmonk API to be accessible at the configured base URL under
/api. - Properly configured API credentials must be provided in n8n's credential manager.
Troubleshooting
- Authentication errors: Ensure the API credentials (domain, username, password) are correct and have sufficient permissions.
- Invalid Template or Subscriber IDs: Verify that the provided IDs exist in the Listmonk instance.
- Network issues: Confirm that the Listmonk server is reachable from the n8n environment.
- Malformed JSON in Data property: If providing custom JSON data, ensure it is valid JSON to avoid parsing errors.
- Unsupported Messenger: Currently, only "email" is supported; other values may cause failures.
Common error messages might include HTTP 401 Unauthorized (bad credentials), 404 Not Found (invalid template or subscriber), or 400 Bad Request (invalid input data). Resolving these involves checking credentials, verifying IDs, and validating input formats.