Reachkit icon

Reachkit

Interact with the Reachkit API

Actions20

Blocklist → Get Many

AI-generated

Overview

The node interacts with the Reachkit API to retrieve multiple entries from the Blocklist resource. It is designed to fetch either all blocklist entries or a limited subset based on user-defined parameters. This functionality is useful for scenarios where users need to review, audit, or process lists of blocked entities such as emails, IPs, or other identifiers managed by Reachkit.

Practical examples include:

  • Exporting all blocklisted contacts for compliance checks.
  • Searching and retrieving specific blocklist entries using keywords.
  • Paginating through blocklist data when dealing with large datasets.

Properties

Name Meaning
Return All Whether to return all blocklist entries or limit the number of results returned.
Limit Maximum number of blocklist entries to return if not returning all (1 to 100).
Additional Fields Optional extra parameters:
• Page: The page number of results to retrieve.
• Search: A search term to filter blocklist entries.

Output

The node outputs JSON data representing the retrieved blocklist entries. Each item in the output corresponds to a blocklist record fetched from the Reachkit API. The structure typically includes details about each blocked entity, such as identifiers and metadata.

No binary data output is indicated for this operation.

Dependencies

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

Troubleshooting

  • Common Issues:
    • Authentication failures due to missing or invalid API keys.
    • Exceeding rate limits imposed by the Reachkit API.
    • Invalid parameter values, such as setting "Limit" outside the allowed range (1-100).
  • Error Messages:
    • Unauthorized or 401 errors indicate issues with API credentials; verify and update the API key.
    • 400 Bad Request errors may result from invalid query parameters; ensure "Limit" and "Page" are within valid ranges.
    • Network or timeout errors suggest connectivity problems; check internet connection and Reachkit service status.

Links and References

Discussion