Actions42
- Campaigns Actions
- Create Campaign
- Create Template
- Duplicate Template
- Get Campaign Basic Information
- Get Campaign Clicks
- Get Campaigns
- Get Campaign Information By ISP
- Get Campaign Links
- Get Campaign Openers
- Get Campaign Openers By Browser
- Get Campaign Openers By Countries
- Get Campaign Openers By Os
- Get Campaign Soft Bounces
- Get Campaign Total Information
- Get Stats By Date
- Send Template Campaign
- Subscribers Actions
- SMS Actions
- SMTP Actions
- Webhooks Actions
Overview
This node allows sending transactional emails via an SMTP service by providing a list of message objects. It is useful in scenarios where automated, programmatic email delivery is required, such as sending order confirmations, password resets, notifications, or any other type of transactional communication. Users can specify multiple messages in one execution to send batch emails.
Properties
| Name | Meaning |
|---|---|
| Messages | A JSON array of message objects representing the emails to be sent. Each object defines the content and recipients of an individual email. |
Output
The node outputs the response from the SMTP service for each message sent in the json output field. This typically includes status information about the email delivery attempt(s). If binary data is returned (e.g., attachments or raw email data), it would be included accordingly, but this node primarily focuses on JSON responses related to email sending results.
Dependencies
- Requires an API key credential for authenticating with the SMTP or transactional email service.
- The node depends on an external SMTP or transactional email API endpoint to send emails.
- Proper configuration of the API base URL and headers is necessary (e.g., setting
AcceptandContent-Typetoapplication/json). - No additional environment variables are explicitly required beyond the API authentication credentials.
Troubleshooting
- Invalid JSON in Messages: Since the
Messagesproperty expects valid JSON, malformed JSON input will cause errors. Ensure the JSON array and objects are correctly formatted. - Authentication Errors: Missing or incorrect API credentials will result in authorization failures. Verify that the API key or token is correctly configured.
- API Endpoint Issues: Network problems or incorrect base URLs can cause request failures. Confirm the endpoint URL and network connectivity.
- Message Format Errors: If the message objects do not conform to the expected schema of the SMTP service, the API may reject them. Validate message structure according to the service's documentation.
- Rate Limits or Quotas: Sending too many emails in a short time might trigger rate limiting. Check service limits and adjust usage accordingly.
Links and References
- Refer to your SMTP or transactional email provider’s API documentation for detailed message object structure and supported features.
- General JSON formatting guides to help construct valid message arrays.
- n8n documentation on using JSON input properties and handling API credentials.