OpenEMM icon

OpenEMM

Consume EMM API
Join our community

Actions8

Overview

This node integrates with an Email Marketing Management (EMM) system to send mailings. Specifically, the Mailing - Send operation allows users to trigger the sending of a predefined mailing campaign through the EMM API. This is useful for automating email campaigns such as newsletters, promotional emails, or transactional messages.

Typical use cases include:

  • Sending scheduled or immediate marketing campaigns.
  • Triggering action-based mailings to specific customers.
  • Sending test or admin preview emails before full deployment.
  • Automating follow-up emails based on user behavior or status.

For example, you might configure this node to send a "Weekly Newsletter" mailing to all subscribers or send a targeted action-based email to a single customer after they complete a purchase.

Properties

Name Meaning
Authentication Method of authentication; currently supports only Basic authentication using an API key credential.
Mailing Name or ID The mailing campaign to send. Choose from a list of available mailings or specify an ID via expression.
Additional Parameters Optional parameters to customize the send action:
  Customer ID For action-based mailings, specifies the customer ID to send the mailing to a single recipient. This is the only required data in the request body for such mailings.
  Data JSON object with profile data overrides for action-based mailings. This data temporarily overrides recipient profile fields but is not saved permanently.
  Send Date ISO-8601 date-time string specifying when to send the mailing. Not needed for action-based mailings.
  Send Type Type of recipients for this send action. Options are:
- ACTION_BASED ("E")
- ADMIN ("A")
- DATE_BASED ("R")
- TEST ("T")
- WORLD ("W")
Only required when using TEST or ADMIN types.
  User Status Numeric status of the customer, used only if the user is waiting for confirmation (status 5 = Waiting-For-DOI).

Output

The node outputs a JSON array where each item corresponds to the result of sending the mailing for each input item processed. The JSON structure depends on the response from the EMM API's send endpoint and typically includes details about the send action status.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential configured in n8n for Basic authentication to access the EMM API.
  • Depends on the EMM API endpoints /send/{mailingId} for sending mailings.
  • Uses helper functions internally to make RESTful HTTP requests to the EMM API.

Troubleshooting

  • Common issues:

    • Invalid or missing mailing ID/name: Ensure the mailing exists and is selected correctly.
    • Authentication failures: Verify that the API key credential is valid and has sufficient permissions.
    • Incorrect parameter formats: For example, sendDate must be a valid ISO-8601 datetime string.
    • Using customerId without proper mailing type: customerId is only applicable for action-based mailings.

  • Error messages:

    • API errors returned from the EMM service will be propagated. Check the error message for details such as unauthorized access, invalid parameters, or mailing not found.
    • If the node is set to continue on fail, errors will appear in the output JSON under an error field.

  • Resolution tips:

    • Double-check mailing selection and IDs.
    • Confirm API credentials and permissions.
    • Validate optional parameters carefully.
    • Use test send types (TEST) to verify configuration before full sends.

Links and References

Discussion