BIN Code Data Enrichment via apilayer API - n8n Workflow

E-commerce developers needing real-time financial data verification.
Security analysts focused on fraud detection and payment intelligence.
Users looking for advanced examples of integrating third-party APIs using the n8n HTTP Request node.
Beginners seeking foundational n8n templates for external data enrichment.

This essential n8n workflow provides a robust method for integrating external data sources directly into your automation pipelines. Utilizing the standard HTTP Request n8n node, the automation queries the apilayer service to retrieve detailed information based on a provided BIN (Bank Identification Number) code. This capability is crucial for implementing payment validation, verifying card types, and gathering geographical data related to payment instruments before processing transactions.

This specific n8n template is straightforward, demonstrating the best practice for how to securely pass API keys and dynamic variables to external RESTful APIs within an n8n environment. This ensures your data enrichment processes are reliable and easy to maintain. Mastering this basic n8n node integration is key to building complex automations.

The execution of this n8n workflow is simple and systematic. The process begins with the When clicking ‘Execute workflow’ n8n trigger node, which allows for manual testing and initiation.

1. Initialization: The flow moves to the Set API Key & BIN Number to Lookup n8n node. Here, input variables are defined: bincode (the number to lookup) and apikey (your apilayer authentication key). This node ensures data consistency before the external call.


2. External Request: The core action is handled by the Lookup BIN n8n node, which is configured as an HTTP Request. This n8n node constructs a GET request targeting the apilayer BIN check endpoint. Crucially, the bincode is embedded directly into the URL path, while the sensitive apikey is securely passed as an HTTP header parameter named apiKey.


3. Output: The n8n workflow successfully executes the request and returns the structured JSON data provided by the apilayer service, containing all relevant BIN details.

To use this n8n workflow, follow these steps:

1. Import: Copy the provided JSON code and import it directly into your n8n instance using the 'New' menu and selecting 'Import from JSON'.


2. Credentials: Obtain an API key from the apilayer service for their BIN check endpoint.


3. Configuration: Locate the Set API Key & BIN Number to Lookup n8n node. You must update the apikey field with your actual apilayer key. For initial testing, you may also replace the sample bin_code.


4. Activation: Ensure the n8n workflow is activated (if you plan to use a different trigger) or click 'Execute workflow' on the manual n8n trigger node to test the integration.

This n8n workflow relies on three core nodes:

When clicking ‘Execute workflow’ (Manual Trigger)
Function: Acts as the initial n8n trigger, allowing the user to start the n8n workflow manually for testing or single executions.
Key Configuration: No specific parameters, designed solely to initiate the sequence.

Set API Key & BIN Number to Lookup (Set n8n Node)
Function: Defines the input variables (bincode and apikey) needed for the subsequent API call. This is a crucial step for parameterizing the n8n workflow.
Key Configuration: Sets two string assignments: bincode (sample value: JH4KA7560RC003647) and apikey (must be replaced with your actual key).

Lookup BIN (HTTP Request n8n Node)
Function: Executes the external API query to apilayer using the defined variables. This demonstrates powerful external connectivity within the n8n workflow.
Key Configuration:
Method: GET.
URL: https://api.apilayer.com/bincheck/{{ $json.bin_code }} (Dynamically inserts the BIN code).
Header Parameter: Uses apiKey header to pass the security token {{ $json.apikey }} securely.