DEV Community

Cover image for Quick Guide: Connecting n8n to Any REST API in 10 Minutes
Bernard K
Bernard K

Posted on

Quick Guide: Connecting n8n to Any REST API in 10 Minutes

#n8n #automation #api #tutorial

Connecting n8n to a REST API in under 10 minutes might sound ambitious, but it's quite achievable, even for beginners. I stumbled across n8n a few months ago when I was dealing with automating my IoT data reporting. The need for a flexible automation tool was pressing, given the constraints I face working in Kenya: unreliable internet, budget limits, and a need for simplicity. My goal was to automate data fetching from a weather API, and n8n seemed like the perfect tool because of its visual workflow builder.

Why use n8n?

Before getting started, let me explain why n8n caught my attention. It's open-source, meaning no monthly fees, which is a big win when you're watching your budget. Plus, its visual interface means I don't have to hard-code API calls like I used to, saving heaps of time. For someone juggling over 2,500 IoT devices across regions with sporadic connectivity, automating workflows with minimal overhead is incredibly helpful.

Getting started with n8n

First, you need to have n8n running. You can deploy it locally using Docker or any cloud provider. I usually run it on a DigitalOcean droplet with 2GB RAM, costing about $10 a month. This setup has handled my modest workflows without a hitch.

Once n8n is up and running, you’ll land on a simple canvas ready for your workflow creation. Here's how I connected n8n to a REST API to fetch weather data.

Setting up the HTTP request node

The HTTP Request node is your gateway to external APIs. Here’s how you set it up to connect to any REST API. I'll use the OpenWeather API as an example.

  1. Add the HTTP Request Node: Drag this node from the left panel to your canvas.

  2. Configure the Request: Double-click the node and you’ll see options for configuring your HTTP request.

    • Method: Select GET since we are fetching data.
    • URL: Input the API endpoint, like http://api.openweathermap.org/data/2.5/weather?q=Nairobi&appid=YOUR_API_KEY.

  3. Testing the API: Hit the "Execute Node" button to test your request. Within my setup, this worked smoothly. A successful call displays the response in JSON format, showing temperature, humidity, and more.

Parsing the API response

After you have the raw data, you need to make it usable. Here, the JSON Parse node is quite handy.

  1. Add the JSON Parse Node: Connect this to your HTTP Request node.

  2. Configure the Node: Simply set the "Fields to Convert" to the field containing your JSON data. In our case, it's the entire API response.

Executing this parses the JSON, making it structured data ready for further processing in your workflow.

Handling connectivity issues

Working in Nairobi, internet connectivity isn't always stable. I handle this by introducing retries and error-checking in n8n.

  1. Add a Function Node: Create simple JavaScript code to retry the HTTP request if it fails. Here’s a quick snippet: 
   let retryCount = 0;
   const maxRetries = 3;
   let success = false;

   while (retryCount < maxRetries && !success) {
     try {
       // Call the HTTP Request Node here
       success = true; // set to true if the request succeeds
     } catch (error) {
       retryCount++;
       setTimeout(() => {}, 5000); // wait 5 seconds before retrying
     }
   }

   return success ? [{ json: { success: true } }] : [{ json: { success: false } }];
Enter fullscreen mode Exit fullscreen mode

This logic saved me when connecting to APIs from locations with flaky connections, significantly reducing request failure rates.

Automation with ease

Once you have your data, you can either store it in a Google Sheet, send it via email, or trigger other IoT devices. n8n offers nodes for just about anything. For reporting my IoT data, I often push this info to a Google Sheet. Simply drop the Google Sheets node into your workflow, link it with your Google Account, and specify the sheet and cells to update.

Real-world application

Remarkably, setting up n8n to automate data collection cut manual processing time from 2 hours a day to just 10 minutes of setup and occasional monitoring. In one instance, this saved me roughly $200 a month by eliminating the need for a third-party service to handle HTTP requests and parsing.

Final thoughts

If you're navigating constraints such as budget hardware or tough internet conditions, n8n can offer a simple, effective solution for automating data flows. While it’s not without its issues (node configuration can occasionally be a bit fiddly), it's dependable enough for most small to medium IoT applications I've managed.

The next steps? I'm planning to explore triggering device actions based on API responses automatically. Meanwhile, try n8n for your REST API needs. If my experience is anything to go by, you'll appreciate its straightforward approach in a complex world.

Top comments (0)