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
The node interacts with the Mindz API to manage email campaigns. Specifically, the Get operation for the Email Campaign resource retrieves detailed information about a specific email campaign by its unique identifier. This is useful when you want to fetch the current status, content, or metadata of an existing email campaign within your marketing automation workflows.
Common scenarios:
- Fetching details of a scheduled or sent email campaign to display in dashboards.
- Retrieving campaign data to trigger conditional logic based on campaign status.
- Integrating campaign information into CRM or reporting tools.
Practical example:
You have an automated workflow that triggers after an email campaign is sent. Using this node’s Get operation, you retrieve the campaign details to log performance metrics or update contact records accordingly.
Properties
| Name | Meaning |
|---|---|
| Email Campaign ID | The unique identifier of the email campaign you want to retrieve. This is a required string input. |
Output
The output JSON contains the detailed data of the requested email campaign as returned by the Mindz API. This typically includes fields such as campaign name, subject, content, status, send dates, recipient lists, and performance statistics.
If the node supports binary data (not indicated here), it would represent attachments or related media, but for this operation, the output is purely JSON-based campaign information.
Dependencies
- Requires an active connection to the Mindz API via an OAuth2 API credential configured in n8n.
- The node depends on the Mindz API being accessible and the provided Email Campaign ID being valid.
Troubleshooting
- Invalid Email Campaign ID: If the ID does not exist or is malformed, the API will likely return an error indicating the campaign was not found. Verify the ID before running the node.
- Authentication errors: Ensure the OAuth2 credentials are correctly set up and have sufficient permissions to access email campaign data.
- Network issues: Connectivity problems with the Mindz API endpoint can cause timeouts or failures; check network settings and API availability.
- Permission denied: If the authenticated user lacks rights to view the campaign, the API will reject the request.
Links and References
- Mindz API Documentation (hypothetical link as no real URL provided)
- n8n OAuth2 Credential Setup Guide: https://docs.n8n.io/credentials/oauth2/
- Email Marketing Best Practices: https://www.campaignmonitor.com/resources/guides/email-marketing-best-practices/