Actions15
- Account Actions
- Analytics Actions
- Campaign Actions
- Lead Actions
Overview
This node interacts with the Instantly API to retrieve multiple campaign records. It is designed to fetch a list of campaigns, either limited by a specified number or returning all available campaigns. This operation is useful when you want to bulk retrieve campaign data for reporting, analysis, or further processing within an n8n workflow.
Common scenarios:
- Fetching all campaigns to synchronize with another system.
- Retrieving a subset of campaigns for display or filtering purposes.
- Automating campaign data extraction for analytics or auditing.
Practical example:
You might use this node to get up to 50 campaigns from your Instantly account and then pass that data to a spreadsheet or database for tracking campaign performance over time.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all campaign results or only up to a given limit. Options: true or false. |
| Limit | The maximum number of campaign results to return if "Return All" is set to false. Minimum value is 1. Default is 50. |
Output
The node outputs an array of JSON objects representing campaigns. Each object corresponds to a single campaign retrieved from the Instantly API. The exact structure depends on the API response but typically includes fields such as campaign ID, name, and other campaign metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Instantly API.
- The node uses the Instantly API endpoints under
/api/v2/campaigns. - No additional environment variables are required beyond the API authentication setup in n8n.
Troubleshooting
- Limit Exceeds Maximum: If you set the "Limit" property above 100, the node will throw an error because the Instantly API enforces a maximum limit of 100 per request. To resolve, reduce the limit to 100 or enable "Return All" to paginate through all results.
- API Request Failures: Network issues or invalid API credentials can cause request failures. Ensure your API key is valid and that the Instantly service is reachable.
- Empty Results: If no campaigns are returned, verify that campaigns exist in your Instantly account and that any filters applied (if extended) are correct.
Links and References
- Instantly API Documentation (general reference for API endpoints)
- n8n Documentation on Creating Custom Nodes