n8n Workflow: Fetch & Process Cryptocurrency Data

This n8n workflow demonstrates a basic structure for fetching data, processing it, and potentially storing it. While the provided JSON is a template, it outlines a common pattern for interacting with external APIs and preparing data for further use.

What it does

This workflow is a template that illustrates the following steps:

1. Triggers on a Schedule: The workflow is initiated at predefined intervals by the Schedule Trigger node.
2. Makes an API Request: It uses an HTTP Request node to call an external API. This is where you would configure your API endpoint (e.g., CoinMarketCap API), headers, and parameters to fetch cryptocurrency data.
3. Processes Data (Placeholder): A No Operation, do nothing node acts as a placeholder, indicating where custom logic or data manipulation would typically occur after the API response is received.
4. Edits Fields: The Edit Fields (Set) node allows for adding, modifying, or removing fields from the incoming data, preparing it for subsequent steps.
5. Splits Data for Iteration: The Split Out node is used to break down an array of items into individual items, enabling subsequent nodes to process each item independently.
6. Loops Over Items: The Loop Over Items (Split in Batches) node processes items in batches, which is useful for handling large datasets efficiently and preventing rate limit issues with downstream services.
7. Introduces a Delay: A Wait node adds a pause between processing batches, which is crucial for respecting API rate limits or managing the load on target systems.
8. Executes Custom Code: A Code node provides the flexibility to write custom JavaScript logic for advanced data transformation, filtering, or conditional processing.
9. Stores Data (Placeholder): A NocoDB node is included as a placeholder, suggesting that the processed data would ultimately be stored in a NocoDB database. This node would need to be configured with specific table and operation details.

Prerequisites/Requirements

• n8n Instance: A running instance of n8n.
• API Endpoint: An external API endpoint (e.g., CoinMarketCap API) from which to fetch data. You will need to configure the HTTP Request node with the correct URL, method, and any required authentication (API keys, tokens).
• NocoDB Account/Instance: If you intend to use the NocoDB node for data storage, you will need access to a NocoDB instance and a configured credential within n8n.

Setup/Usage

1. Import the Workflow:
   • Download the provided JSON file.
   • In your n8n instance, click on "Workflows" in the left sidebar.
   • Click "New" and then "Import from JSON".
   • Paste the JSON content or upload the file.
2. Configure the HTTP Request Node (ID: 19):
   • Edit this node to specify the API endpoint you want to call (e.g., CoinMarketCap's latest listings endpoint).
   • Add any necessary headers (like X-CMC_PRO_API_KEY for CoinMarketCap) and query parameters.
   • Select the appropriate HTTP method (GET, POST, etc.).
3. Configure the Edit Fields (Set) Node (ID: 38):
   • Adjust this node to transform the data from the API response into the desired format. You might want to rename fields, extract specific values, or create new ones.
4. Configure the Split Out Node (ID: 1239):
   • If your API response returns an array of items (e.g., a list of cryptocurrencies), configure this node to split that array into individual items for processing.
5. Configure the Loop Over Items (Split in Batches) Node (ID: 39):
   • Set the batch size and interval as needed to manage API rate limits or processing load.
6. Configure the Code Node (ID: 834):
   • Implement any custom JavaScript logic here to further process or filter the data.
7. Configure the NocoDB Node (ID: 510):
   • Provide your NocoDB credentials.
   • Specify the base, table, and operation (e.g., "Create," "Update") you want to perform.
   • Map the incoming data fields to your NocoDB table columns.
8. Activate the Workflow: Once configured, activate the workflow by toggling the "Active" switch in the top right corner of the workflow editor. The Schedule Trigger will then run the workflow at its defined intervals.