Actions32
- Campaign Actions
- List Actions
- Media Actions
- Setting Actions
- Subscriber Actions
- Template Actions
- Transaction Actions
Campaign → Get
AI-generatedOverview
This node integrates with a Listmonk instance, a platform for email marketing and newsletter management. Specifically, the "Campaign" resource with the "Get" operation allows users to retrieve campaign data from their Listmonk account. This is useful for scenarios where you want to list or analyze existing campaigns, such as fetching campaign details for reporting, monitoring campaign performance, or syncing campaign data with other systems.
Practical examples include:
- Fetching a paginated list of email campaigns to display in a dashboard.
- Retrieving campaign metadata for further processing or automation workflows.
- Integrating campaign data into CRM or analytics tools.
Properties
| Name | Meaning |
|---|---|
| Page | The page number of campaign results to query (pagination). Default is 1. |
| Per Page | The number of campaign items to return per page. Default is 25. |
Output
The node outputs JSON data representing the requested campaigns. The structure typically includes an array of campaign objects containing details such as campaign ID, name, status, creation date, and other relevant metadata provided by Listmonk's API.
If the node supports binary data output (not indicated here), it would generally relate to attachments or media associated with campaigns, but this operation focuses on retrieving campaign metadata only.
Dependencies
- Requires connection to a Listmonk instance via its API.
- Needs an API authentication credential consisting of a domain URL, username, and password.
- The base URL for API requests is constructed from the provided domain credential.
- Proper permissions on the Listmonk instance to read campaign data.
Troubleshooting
- Authentication errors: Ensure that the API credentials (domain, username, password) are correct and have sufficient permissions.
- Pagination issues: If no campaigns are returned, verify that the
PageandPer Pagevalues are within valid ranges and that campaigns exist on those pages. - Network errors: Confirm that the Listmonk instance is reachable from n8n and that there are no firewall or connectivity issues.
- API changes: If the Listmonk API changes, the node might fail; ensure compatibility with the current Listmonk version.
Links and References
- Listmonk Official Documentation
- Listmonk GitHub Repository
- n8n documentation on creating custom nodes