Mindz icon

Mindz

Interact with Mindz API

Actions115

Overview

The node provides integration with the Mindz API, specifically allowing operations on various resources including Email Campaigns. The Duplicate operation for the Email Campaign resource enables users to create a copy of an existing email campaign by specifying its ID. This is useful when you want to reuse or modify an existing campaign without starting from scratch.

Common scenarios:

  • Quickly creating a new email campaign based on a previous one.
  • Testing variations of an email campaign while preserving the original.
  • Automating campaign cloning as part of a larger marketing workflow.

Properties

Name Meaning
Email Campaign ID The unique identifier of the email campaign to duplicate. This is required to specify which campaign to clone.

Output

The node outputs JSON data representing the duplicated email campaign. This typically includes details such as the new campaign's ID, name, status, and other metadata returned by the Mindz API after duplication.

If the node supports binary data output (not indicated here), it would represent attachments or media related to the campaign, but this is not evident from the provided code.

Dependencies

  • Requires an active connection to the Mindz API using an OAuth2-based API key credential configured in n8n.
  • The node depends on the Mindz API endpoints for email campaigns, specifically the duplication endpoint.
  • Proper permissions on the Mindz account to duplicate email campaigns are necessary.

Troubleshooting

  • Missing or invalid Email Campaign ID: Ensure the Email Campaign ID property is correctly set and corresponds to an existing campaign in Mindz.
  • Authentication errors: Verify that the OAuth2 credentials are valid and have not expired.
  • API rate limits or network issues: These can cause failures; check connectivity and Mindz API status.
  • Permission denied: The user associated with the API key must have rights to duplicate campaigns.
  • Unexpected API responses: If the Mindz API changes, the node might fail; updating the node or checking API documentation may help.

Links and References

Discussion