Instantly icon

Instantly

Interact with Instantly API

Actions24

Overview

This node interacts with the Instantly API to retrieve multiple campaign records. Specifically, the "Campaign - Get Many" operation fetches a list of campaigns from the Instantly platform. It is useful for scenarios where you want to bulk retrieve campaign data for reporting, synchronization, or further processing within an n8n workflow.

Practical examples include:

  • Fetching all marketing campaigns to analyze their performance.
  • Retrieving a limited number of campaigns to display in a dashboard.
  • Integrating campaign data into CRM or analytics tools.

Properties

Name Meaning
Return All Whether to return all available campaign results or only up to a specified limit.
Limit The maximum number of campaign results to return when "Return All" is set to false.
  • Return All: If true, the node will fetch all campaigns without limiting the number.
  • Limit: When "Return All" is false, this sets the upper bound on how many campaigns to retrieve (minimum 1, default 50).

Output

The node outputs an array of JSON objects representing campaigns. Each object corresponds to a single campaign and includes fields as returned by the Instantly API's /api/v2/campaigns endpoint. Typical fields may include campaign ID, name, and other 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, specifically /api/v2/campaigns.
  • No additional environment variables are required beyond the API authentication setup.

Troubleshooting

  • Common issues:

    • API authentication failure due to invalid or missing API key.
    • Network connectivity problems preventing access to the Instantly API.
    • Exceeding rate limits imposed by the Instantly API.

  • Error messages:

    • Errors thrown during API requests will be surfaced with their message. For example, if fetching campaigns fails, the error message from the API or network layer will appear.
    • To handle errors gracefully, enable the "Continue On Fail" option in the node settings to allow the workflow to proceed despite individual request failures.

  • Resolutions:

    • Verify that the API key credential is correctly configured and has necessary permissions.
    • Check network connectivity and proxy settings if applicable.
    • Respect API rate limits by adjusting workflow frequency or implementing delays.

Links and References

Discussion