Mindz icon

Mindz

Interact with Mindz API

Actions116

Overview

This node integrates with the Mindz API to manage email campaign lists. Specifically, the Email Campaign List - Create operation adds a specified list to an existing email campaign. This is useful for marketers or administrators who want to dynamically associate contact lists with email campaigns to target specific audiences.

Practical examples:

  • Adding a new subscriber list to an ongoing promotional email campaign.
  • Automating the inclusion of segmented user groups into targeted email campaigns based on external triggers.
  • Managing multiple mailing lists within a single campaign programmatically.

Properties

Name Meaning
Email Campaign ID The unique identifier of the email campaign to which the list will be added.
List ID The unique identifier of the list that should be added to the specified email campaign.

Output

The node outputs JSON data representing the result of adding the list to the email campaign. Typically, this includes confirmation details such as IDs and status of the association. The exact structure depends on the Mindz API response but generally confirms successful linkage.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the Mindz API using an OAuth2-based API key credential.
  • The node depends on proper configuration of the Mindz API credentials within n8n.
  • Network access to the Mindz API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Email Campaign ID or List ID parameters will cause the operation to fail.
    • Authentication errors if the API key credential is not set up correctly or has expired.
    • Network connectivity problems preventing communication with the Mindz API.
  • Error messages and resolutions:

    • "Unauthorized" or "Authentication failed": Verify that the API key credential is valid and properly configured.
    • "Resource not found": Check that the provided Email Campaign ID and List ID exist and are correct.
    • "Bad Request": Ensure all required parameters are provided and formatted correctly.
    • Timeouts or network errors: Confirm network connectivity and API availability.

Links and References

Discussion