Mindz icon

Mindz

Interact with Mindz API
Join our community

Actions115

Overview

The node interacts with the Mindz API to manage email campaign plans. Specifically, the List operation under the Email Campaign Plan resource retrieves a paginated list of email campaign plans associated with a specified email campaign ID. This is useful for users who want to programmatically fetch and review multiple email campaign plans, for example, to analyze campaign scheduling, monitor plan statuses, or integrate campaign data into other systems.

Practical examples include:

  • Fetching all plans related to a particular email campaign to display in a dashboard.
  • Automating reporting workflows that summarize campaign plans.
  • Integrating campaign plan data with CRM or marketing automation tools.

Properties

Name Meaning
Email Campaign ID The unique identifier of the email campaign whose plans you want to list (required).
Limit Maximum number of results to return in one request. Defaults to 50.
Offset Number of results to skip before starting to collect the output. Useful for pagination.

Output

The node outputs JSON data representing the list of email campaign plans retrieved from the Mindz API. Each item in the output array corresponds to an individual email campaign plan, typically including details such as plan identifiers, scheduling information, status, and other metadata relevant to the campaign plan.

If the API supports binary data for this resource (not indicated here), it would be summarized accordingly, but based on the provided code and properties, the output is purely JSON structured data.

Dependencies

  • Requires an active connection to the Mindz API via an OAuth2-based API key credential configured in n8n.
  • The node depends on the Mindz API endpoints for email campaign plans.
  • Proper permissions and valid credentials are necessary to access email campaign plan data.

Troubleshooting

  • Missing or invalid Email Campaign ID: Since the Email Campaign ID is required, omitting it or providing an incorrect ID will likely cause errors or empty results. Ensure the ID is correct and exists in the Mindz system.
  • API authentication errors: If the OAuth2 credential is not set up correctly or has expired, the node will fail to authenticate. Reconfigure or refresh the API credentials.
  • Pagination issues: Setting the limit too high might lead to timeouts or large payloads. Use reasonable limits and offsets to paginate through results.
  • Network or API downtime: Temporary network issues or Mindz API outages can cause failures. Retry after some time or check Mindz service status.

Links and References

Discussion