ReachkitInstall

Overview

The node interacts with the Reachkit API to check if a given email address is present in a specified blocklist. This operation is useful for scenarios where you want to verify whether an email should be excluded from campaigns, communications, or other processes due to being blocked.

Practical examples include:

• Validating user emails before sending marketing campaigns to avoid contacting blocked addresses.
• Integrating with customer support workflows to filter out blocked contacts.
• Automating lead qualification by excluding emails found in blocklists.

Properties

Output

The node outputs JSON data representing the result of the blocklist check. Typically, this will include information indicating whether the email exists in the specified blocklist and possibly additional metadata about the blocklist entry.

If the node supports binary data output (not indicated here), it would typically represent attachments or related files, but this node focuses on JSON responses.

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:

  • Invalid or missing API key credential can cause authentication failures.
  • Providing an incorrect or non-existent Blocklist ID will result in errors or empty results.
  • Malformed email addresses may cause validation errors or unexpected API responses.

• Error messages:

  • Authentication errors usually indicate problems with the API key; ensure the key is valid and has required permissions.
  • "Blocklist not found" or similar errors suggest the Blocklist ID does not exist; verify the ID.
  • Input validation errors for the email field require checking the email format.

Links and References

• Reachkit API Documentation (general reference for API endpoints and usage)
• n8n documentation on creating custom nodes