Actions8
Send Transactional Email
AI-generatedOverview
The node provides an interface to interact with Listmonk, a self-hosted email marketing tool. Specifically, the Send Transactional Email operation allows sending one-off transactional emails using predefined templates. This is useful for scenarios where you want to send personalized or triggered emails such as order confirmations, password resets, or notifications without creating a full campaign.
Practical examples include:
- Sending a welcome email immediately after user registration.
- Dispatching a receipt or invoice after a purchase.
- Notifying users about account activity or alerts.
Properties
| Name | Meaning |
|---|---|
| Content Type | The format of the email content. Options: HTML, Plain Text, Markdown, Rich Text |
| Template ID | Numeric ID of the email template to use for the transactional email |
| Recipient Email | Email address of the recipient (must be a valid email) |
| From Email (Optional) | Optional sender email address; if not provided, default sender configured in Listmonk will be used |
| Template Data (JSON) | JSON object containing data to populate dynamic fields in the email template |
Output
The node outputs the response from the Listmonk API call to send the transactional email. The output is a JSON object that typically contains information about the success or failure of the request, such as status codes and messages.
No binary data is produced by this operation.
Dependencies
- Requires access to a Listmonk instance with API enabled.
- Needs credentials including domain URL, username, and password for authentication.
- The node uses HTTP Basic Authentication to communicate with the Listmonk API.
- Properly configured API credentials must be set up in n8n before using this node.
Troubleshooting
- Invalid Email Address Error: If the recipient or sender email does not match the required regex pattern, the node will reject the input. Ensure emails are correctly formatted.
- Authentication Failures: Incorrect or missing API credentials will cause authorization errors. Verify the API username, password, and domain URL.
- Template Not Found: Using a non-existent template ID may result in an error from the API. Confirm the template ID exists in your Listmonk instance.
- Malformed JSON in Template Data: The
templateDataproperty must be valid JSON. Invalid JSON will cause parsing errors. - API Connectivity Issues: Network problems or incorrect base URL configuration can prevent the node from reaching the Listmonk API.