Actions116
- 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
- Email Campaign Excluded Plan Actions
- Email Campaign List Actions
- Email Campaign Plan Actions
- Email List Actions
- Enroll Actions
- MindzPay Account Actions
- MindzPay Invoice Actions
- MindzPay Payment Actions
- MindzPay Subscription Actions
- Subscription Actions
- Team Actions
- User Actions
Overview
This node interacts with the Mindz API to manage "Email Campaign Excluded Course" resources. Specifically, the Get operation retrieves details about a particular course that has been excluded from an email campaign. This is useful in scenarios where you want to verify or audit which courses are excluded from receiving certain email campaigns, for example, to ensure targeted marketing or communication strategies exclude specific courses.
Practical examples:
- Fetching exclusion details before sending out an email campaign to avoid contacting students enrolled in certain courses.
- Auditing exclusions to confirm compliance with marketing rules or preferences.
- Integrating with other systems to synchronize exclusion data for reporting or analytics.
Properties
| Name | Meaning |
|---|---|
| Email Campaign ID | The unique identifier of the email campaign from which a course is excluded. |
| Course ID | The unique identifier of the excluded course whose exclusion details you want to retrieve. |
Output
The output JSON contains the details of the excluded course within the specified email campaign. This typically includes identifiers and metadata related to the exclusion record, such as the email campaign ID, course ID, and possibly timestamps or status fields depending on the API response.
If the node supports binary data output (not indicated here), it would represent any associated files or attachments related to the exclusion, but this node primarily deals with JSON data representing exclusion records.
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 that handle email campaign exclusions.
- Proper permissions on the API key to read email campaign exclusion data are necessary.
Troubleshooting
- Missing or invalid Email Campaign ID or Course ID: The node requires both IDs to be provided and valid. Errors will occur if these are missing or incorrect.
- Authentication errors: If the OAuth2 credentials are expired or misconfigured, the node will fail to connect to the Mindz API.
- API rate limits or downtime: Temporary failures may happen due to API limits or service outages; retrying later or checking API status can help.
- Not found errors: If the specified exclusion does not exist, the API may return a 404 error indicating no matching record.
To resolve common errors:
- Double-check the input IDs for correctness.
- Verify the OAuth2 credential configuration and refresh tokens if needed.
- Consult Mindz API documentation or support for specific error codes returned by the API.
Links and References
- Mindz API Documentation (hypothetical link, replace with actual if available)
- n8n OAuth2 Credential Setup Guide: https://docs.n8n.io/credentials/oauth2/
- General n8n Node Development: https://docs.n8n.io/integrations/creating-nodes/