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
This node interacts with the Mindz API to manage "Email Campaign Excluded Plans." Specifically, the Get operation retrieves details about a specific plan that has been excluded from an email campaign. This is useful when you want to verify or audit which plans are excluded from receiving certain email campaigns, for example, to ensure targeted marketing or communication strategies.
Practical examples:
- Fetching details of a particular plan excluded from an email campaign before sending out communications.
- Auditing excluded plans to adjust campaign targeting.
- Integrating with other workflows that depend on exclusion data for email campaigns.
Properties
| Name | Meaning |
|---|---|
| Email Campaign ID | The unique identifier of the email campaign from which a plan is excluded. |
| Plan ID | The unique identifier of the excluded plan whose details you want to retrieve. |
Output
The output JSON contains the details of the excluded plan associated with the specified email campaign. This typically includes identifiers and metadata describing the exclusion status and possibly related plan information.
If the node supports binary data output (not indicated here), it would represent any file or media content returned by the API, but in this case, the output is purely JSON data representing the excluded plan entity.
Dependencies
- Requires an active connection to the Mindz API via 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 Plan ID parameters will cause the API call to fail.
- Authentication errors if the API key credential is not set up correctly or expired.
- Network connectivity problems preventing access to the Mindz API.
Error messages and resolutions:
- "Unauthorized" or "Authentication failed": Check and refresh the API authentication token or credentials.
- "Resource not found": Verify that the provided Email Campaign ID and Plan ID exist and are correct.
- "Missing required parameter": Ensure both Email Campaign ID and Plan ID are provided and non-empty.
Links and References
- Mindz API Documentation (hypothetical link)
- n8n OAuth2 Credential Setup Guide: https://docs.n8n.io/credentials/oauth2/
- n8n Node Development Documentation: https://docs.n8n.io/integrations/creating-nodes/