Actions13
- Chats Actions
- Companies Actions
- Email Campaign Trackers Actions
- Files Actions
- Sales Actions
Overview
The node interacts with the MagicDoor API to retrieve the latest email campaign trackers associated with a specific company. This operation is useful for marketing teams or CRM systems that need to monitor and analyze recent email campaign activities, such as tracking opens, clicks, or other engagement metrics tied to campaigns sent by a company.
Practical examples include:
- Fetching the most recent email campaign tracking data to update dashboards.
- Integrating email campaign performance data into customer profiles.
- Automating follow-up actions based on the latest campaign interactions.
Properties
| Name | Meaning |
|---|---|
| Company ID | The ID of the company whose latest email campaign trackers you want to retrieve. It is a required numeric identifier. |
Output
The node outputs JSON data containing the latest email campaign trackers for the specified company. The structure typically includes details about each tracked email campaign event, such as timestamps, campaign identifiers, and engagement metrics.
If the node supports binary data output (not evident from the provided code), it would represent attachments or related media, but this is not indicated here.
Dependencies
- Requires an API key credential to authenticate with the MagicDoor API.
- The base URL for the API must be configured in the node credentials.
- The node depends on the MagicDoor API endpoints defined externally (in
MagicDoorEndpoints), which handle the actual request logic.
Troubleshooting
- Missing or invalid Company ID: Ensure the Company ID is provided and is a valid number; otherwise, the API call will fail.
- Authentication errors: Verify that the API key credential is correctly set up and has the necessary permissions.
- API endpoint issues: If the MagicDoor API base URL or endpoints change, update the credentials or node configuration accordingly.
- Network errors or timeouts: Check network connectivity and API availability.
Common error messages might include authentication failures, invalid parameters, or HTTP errors returned by the MagicDoor API. Resolving these usually involves verifying credentials, input values, and API status.
Links and References
- MagicDoor API Documentation (Replace with actual URL)
- n8n documentation on Creating Custom Nodes