This workflow is designed to validate and fetch information about a card using the BIN code. It utilizes apilayer's BIN Check API and provides details like the card brand, type, issuing bank, and country. Prerequisites: An apilayer account API Key for the BIN Check API Steps in n8n: Step 1: Manual Trigger Node Type: Manual Trigger Purpose: Starts the workflow manually Step 2: Set BIN Code and API Key Node Type: Set Fields to set: bin_code: A sample BIN like JH4KA7560RC003647 apikey: Your apilayer API key Step 3: HTTP Request Node Type: HTTP Request Method: GET URL: https://api.apilayer.com/bincheck/{{ $json.bin_code }} Headers: Name: apiKey Value: {{ $json.apikey }} (Optional) Step 4: Handle the Output Add nodes to store, parse, or visualize the API response. Expected Output: The response from apilayer contains detailed information about the provided BIN: Card scheme (e.g., VISA, MasterCard) Type (credit, debit, prepaid) Issuing bank Country of issuance Example Use Case: Use this to build a fraud prevention microservice, pre-validate card data before sending to payment gateways, or enrich card-related logs.
Tags
Related workflows
See all General Automation→Listen on new emails on a IMAP mailbox
Listen on new emails on a given IMAP mailbox. Converts the binary XML attachment to a stringified xmlproperty on the $data object and converts it to JSON. The Setnode could be replaced with Function nodes for example to do a conversion/mapping/transformation. The JSON is ultimately sent to a HTTP Endpoint via POST. This could be a starter for EDI purposes like receiving or transmitting XML data and conversion via JSON object property mapping.
Extract post titles from a blog
This workflow uses n8n to extract the names of all the posts from the Hackernoon homepage.
Create a new DigitalOcean Droplet
Uses a DigitalOcean Personal Access Token to create a new Droplet. Add your personal access token and change the parameters to create droplets of different sizes. You can also specify more options; refer the API docs