Reachkit icon

Reachkit

Interact with the Reachkit API

Actions20

Campaign → Get Many

AI-generated

Overview

The node integrates with the Reachkit API to retrieve multiple campaign records. It is designed to fetch a list of campaigns, optionally filtered or paginated, which is useful for workflows that need to process or analyze marketing campaigns managed in Reachkit.

Common scenarios include:

  • Automating reporting by retrieving all or a subset of campaigns.
  • Syncing campaign data into other systems or databases.
  • Filtering campaigns based on search terms or pagination to handle large datasets efficiently.

For example, you might use this node to get the first 50 campaigns matching a specific keyword or to retrieve all campaigns across multiple pages for comprehensive analysis.

Properties

Name Meaning
Return All Whether to return all campaign results or limit the number of results returned.
Limit Maximum number of campaign results to return when "Return All" is false (1 to 100).
Additional Fields Optional extra parameters:
• Page: The page number of results to retrieve.
• Search: A search term to filter campaigns by name or content.

Output

The node outputs an array of campaign objects in the json field of each item. Each object represents a campaign retrieved from Reachkit, containing details such as campaign ID, name, status, and other metadata as provided by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Reachkit API.
  • The node sends requests to the Reachkit API endpoint at https://reachkit.ai/api/v1.
  • Proper configuration of the API key credential within n8n is necessary for successful execution.

Troubleshooting

  • Authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Empty results: Verify the search term and pagination parameters; if no campaigns match the criteria, the result will be empty.
  • Limit exceeded: The Limit property must be between 1 and 100; setting values outside this range may cause errors.
  • API rate limits: If many requests are made rapidly, the API might throttle requests; consider adding delays or handling retries.

Links and References

Discussion