Skip to main content
n8n is a fair-code licensed workflow automation platform that lets you connect apps, APIs, and services to build automated workflows with minimal effort. The Decodo node is an n8n integration for Decodo’s scraping APIs, which automatically bypass blocks and bot protection to extract data from a target URL. It’s designed for developers and startups automating data collection from platforms like Google, eCommerce sites, and job boards. The node is published as @decodo/n8n-nodes-decodo and works with any Web Data API plan. Older Web Scraping API plans also work. Free trials are available on the dashboard.
More information can be found on GitHub here.

​
Features

  • Target selector. Universal, Google Search, Amazon, and YouTube Transcript, each with its own parameters.
  • Easy integration. Plug the Decodo node into existing workflows to start scraping with minimal setup.
  • Bypassing CAPTCHAs, rate-limits, and IP bans. Automatic handling of common anti-bot defenses.
  • Geo-targeting. Request region-specific results from websites that restrict content based on location.
  • Rotating proxy support to avoid IP bans. Built-in proxy rotation to keep requests distributed and persistent.
  • Structured data output. Get results in JSON or Markdown formats for easy readability and further analysis.
  • Usable as an AI agent tool. Attach the node directly to an AI Agent node without extra configuration.

​
Installation

Decodo is an official node integrated into n8n. To use it, simply:
  1. Open the nodes panel.
  1. Search for “Decodo” to find the node.
  1. Click + Add to workflow.

​
Obtaining a Decodo account

Once you have a plan activated, copy your API key from the Web Data API playground. Older plans only have a generated authentication token, which also works.

​
Setting up credentials on n8n

  1. Open the credentials window on n8n.
  1. Create a new credential.
  1. Find the Decodo Credentials API.
  1. Paste your key into the Authentication Token field.
There is a single credential field for both plan types, and the node works out which one you pasted:
The node decides by base64-decoding the value: if it decodes to printable text containing a colon, it is treated as a legacy token, otherwise as an API key. You do not need to tell it which one you have.

​
Targets

The node has a required Target dropdown that determines which Decodo scraping target is called and which other fields appear: n8n also injects its own Custom API Call option into this dropdown at runtime.
Don’t use the YouTube Transcript target for now. It relies on a retired API target and fails on every request. Until the node is updated, use YouTube Subtitles instead, called through n8n’s HTTP Request node.

​
Using the node

The node can be used in 2 ways - as an individual HTTP request node, or a tool for an AI agent.

​
Individual node

To use the Decodo node by itself, connect it to an existing workflow. Once you add it, pick a Target and fill in the fields it shows.
The node requests the target through a proxy in the chosen location, scrapes the page, and returns the response for use by downstream nodes, such as the HTML node to extract content. Below is an example setup:

​
AI Agent tool

You can connect the Decodo node to the AI Agent node as a tool. You don’t need to modify anything inside the node. Here’s what a simple setup would look like:
With this setup, you can prompt the agent to scrape a website in order to extract information. The prompt must be detailed and specific to return the best results.

​
Bad prompt example

If your AI model does not have access to the most recent web information, the following question may fail:
who won NBA in 2025?

​
Good prompt example

The question is more likely to be answered by updating the prompt with an instruction to scrape a reliable source:
scrape wikipedia and tell me who won NBA in 2025

​
Parameters

Which fields appear depends on the target you selected. A dash means the field is not offered for that target. Where a value is shown instead of “Optional”, that is the default the node starts with. Field notes:
  • JS Rendering is on by default and sends headless: "html". Turning it off sends no rendering parameter at all.
  • Markdown only appears once JS Rendering is turned off, so Markdown and JavaScript rendering cannot be combined in this node. It is off by default.
  • Geolocation takes a country name with a capital first letter, for example United States. Read more.
  • Locale changes the language of the search page interface, not the language of the results. For example, en-US or en-GB.
  • Results Amount accepts 1 to 100 and defaults to 10.
  • Video ID must be the bare ID, such as dQw4w9WgXcQ. A full youtube.com/watch?v=... URL is rejected with a validation error.
  • Language Code is required for YouTube Transcript. Omitting it fails validation, and a video with no transcript in that language returns HTTP 404.
When the node is used as an AI agent tool, the agent fills these same fields from your message: If used as an individual node, these parameters can be manually configured by double-clicking on the node. For the full list of API parameters, see Parameters.

​
Compatibility

The node requires Node.js 20.15 or newer. It has been developed and tested with:
  • Node.js v22.17.0
  • n8n nodes API version 1
  • MCP Server – Connect AI agents and MCP-compatible tools to Decodo.
  • CLI – Run Decodo scraping workflows from the command line.
  • Zapier – Use Decodo as an action in your Zaps.
  • TypeScript SDK – Build the same requests in Node.
  • GitHub repository – View the source code and latest releases.

Support

Need help or just want to say hello? Our support is available 24/7.
You can also reach us anytime via email at support@decodo.com.

Feedback

Can’t find what you’re looking for? Request an article!
Have feedback? Share your thoughts on how we can improve.