Overview
The node integrates with the BLAQ List API to retrieve a credit or risk score associated with an individual based on their email and optionally additional personal or card information. This is useful in scenarios such as fraud prevention, creditworthiness assessment, or identity verification where you need to obtain a risk score for a user or customer.
For example, you might use this node to:
- Get a risk score for a user during a signup process by providing their email.
- Enhance scoring accuracy by including partial card details or full name information.
- Automate decision-making workflows that depend on a user's credit or risk score.
Properties
| Name | Meaning |
|---|---|
| The email address of the individual whose score you want to retrieve. Required field. | |
| Additional Fields | Optional extra information to improve the score query accuracy. Includes: |
| - Card BIN | Bank Identification Number (first 6 digits of the card). |
| - Card Last 4 | Last 4 digits of the card number. |
| - First Name | First name of the individual. |
| - Last Name | Last name of the individual. |
Output
The node outputs JSON data containing the retrieved score information from the BLAQ List API. The exact structure depends on the API response but typically includes fields related to the individual's risk or credit score and possibly metadata about the query.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the BLAQ List API.
- The node sends requests to the base URL
https://api.blaqreports.com/integration/v1. - Proper configuration of the API key credential within n8n is necessary.
Troubleshooting
- Missing or invalid API key: Ensure the API key credential is correctly set up and valid.
- Required email field empty: The email property must be provided; otherwise, the request will fail.
- API errors or rate limits: Handle HTTP errors gracefully; check API usage limits and error messages returned by the BLAQ List API.
- Incorrect additional fields format: Make sure optional fields like card BIN or last 4 digits are correctly formatted as strings.
Links and References
- BLAQ List API Documentation (example placeholder, replace with actual if available)
- n8n documentation on creating custom nodes