This email component is designed for use with the Mailchimp Transactional API or custom SMTP server using SMTP URI.
The component supports two authentication and transport methods: Mandrill API and SMTP. At least one of Mandrill API Key or SMTP URI must be configured. If both are provided, SMTP URI takes precedence and emails will be sent via SMTP.
Complete the following fields in the component’s credential section:
smtp://USER:PASS@HOST:PORT or smtps://USER:PASS@HOST:PORT). Required when sending via custom SMTP server.https://mandrillapp.com/api/1.0 by default): The URL for the Mandrill API (used only with Mandrill).Please Note: For the Mandill authentication, you must create a Mailchimp account and generate an API key that will serve as part of the credentials for the Mandrill app.
The component can be configured using the following environmental variables
| Name | Mandatory | Description | Values |
|---|---|---|---|
MAX_BODY_LENGTH |
false | Maximum email message size in bytes (including attachments), defaults to 10485760 (10 MB) |
number |
For each incoming message the component sends an email message via SMTP (if SMTP URI is configured, taking precedence over Mandrill) or via Mandrill using the Send new message API resource.
false.Input message example:
{
"to": "recipient@example.com",
"cc": "manager@example.com",
"subject": "Sample Notification",
"textBody": "Hello! Thank you for subscribing.",
"htmlBody": "<p>Hello! Thank you for subscribing.</p>",
"attachments": [
{
"url": "https://example.com/files/invoice.pdf",
"name": "invoice.pdf"
}
]
}
As a result of sending, you will receive an object containing a “results” array with delivery information for each recipient:
to, cc, or bcc).OK or QUEUED on success; REJECTED or INVALID on failure).YYYY-MM-DDTHH:mm:ss.SSSSSSSZ).Message is REJECTED).0.Output message example:
{
"results": [
{
"To": "recipient@example.com",
"RecipientType": "to",
"Message": "OK",
"MessageID": "c1d10979c1ca441385f64f209d172508",
"SubmittedAt": "2026-10-16T13:10:00.0000000Z",
"ErrorCode": 0
}
]
}
When providing content for the HTML Body, keep in mind that rendering in email clients (like Gmail, Outlook, or Apple Mail) differs significantly from modern web browsers:
<style> blocks located in the <head> for security and performance reasons. For the most reliable results, inline your CSS directly into the HTML tags using the style attribute.var(--main-color)). Use literal hex codes instead.<table>) for complex multi-column layouts to ensure stability.inline_css: true, which attempts to automatically move styles from <style> blocks into element attributes. However, manual inlining is always recommended for critical designs.An HTML body example with inlined styles:
{
"to": "email@example.com",
"subject": "HTML content",
"textBody": "Hello! Thank you for subscribing.",
"htmlBody": "<body style=\"margin:0; padding:20px; font-family:Arial,sans-serif; background-color:#f4f4f4;\"><div style=\"background-color:#ffffff; padding:20px; border-radius:5px; box-shadow:0 0 10px rgba(0,0,0,0.1); max-width:600px; margin:0 auto;\"><h1 style=\"color:#333;\">Hello, Recipient!</h1><p style=\"font-size:16px; color:#666; line-height:1.5;\">Thank you for subscribing to our newsletter.</p><a href=\"https://www.example.com\" style=\"display:inline-block; padding:10px 20px; background-color:#007BFF; color:#ffffff; text-decoration:none; border-radius:5px;\">Get Started</a></div></body>"
}
Click here to learn more about the elastic.io iPaaS