Actions115
- Course Actions
- Bundle Actions
- Course Grade Actions
- Course Grade Detail Actions
- Course Teacher Actions
- Email Actions
- Email Campaign Actions
- Email Campaign Course Actions
- Email Campaign Excluded Course Actions
- Email Campaign Excluded List Actions
- Enroll Actions
- Email Campaign Excluded Plan Actions
- Email Campaign List Actions
- Email Campaign Plan Actions
- Email List Actions
- MindzPay Account Actions
- MindzPay Invoice Actions
- MindzPay Payment Actions
- MindzPay Subscription Actions
- Subscription Actions
- Team Actions
- User Actions
Overview
The node integrates with the Mindz API to manage and retrieve data related to email campaigns. Specifically, for the Email Campaign resource and the Stats operation, it fetches statistical information about a particular email campaign identified by its ID. This is useful for marketing teams or automation workflows that need to monitor the performance of their email campaigns, such as tracking open rates, click rates, or other engagement metrics.
Practical examples:
- Automatically retrieving campaign statistics after sending an email campaign to update dashboards.
- Triggering follow-up actions based on campaign performance (e.g., resending to non-openers).
- Integrating campaign stats into CRM or reporting tools for comprehensive analytics.
Properties
| Name | Meaning |
|---|---|
| Email Campaign ID | The unique identifier of the email campaign for which statistics are requested. |
Output
The node outputs JSON data containing the statistics of the specified email campaign. While the exact structure depends on the Mindz API response, typical fields may include:
- Number of emails sent
- Open rate
- Click rate
- Bounce count
- Unsubscribe count
- Other engagement metrics relevant to the campaign's performance
If the node supports binary data output (not indicated here), it would typically represent attachments or reports related to the campaign stats, but this is not evident from the provided code.
Dependencies
- Requires an active connection to the Mindz API via an OAuth2-based API credential.
- The user must configure the node with valid Mindz API credentials to authenticate requests.
- Network access to Mindz API endpoints is necessary.
Troubleshooting
Common issues:
- Invalid or missing Email Campaign ID will cause the API call to fail.
- Expired or invalid API credentials will result in authentication errors.
- Network connectivity problems can prevent successful API communication.
Error messages and resolutions:
- "Unauthorized" or "Authentication failed": Check and refresh the API credentials.
- "Campaign not found": Verify that the Email Campaign ID is correct and exists in the Mindz system.
- Timeout or network errors: Ensure stable internet connection and that Mindz API endpoints are reachable.
Links and References
- Mindz API Documentation (Replace with actual URL)
- n8n OAuth2 Credential Setup Guide: https://docs.n8n.io/credentials/oauth2/
- General n8n Node Development: https://docs.n8n.io/integrations/creating-nodes/