Pulling data from services that n8n doesn’t have a pre-built integration for
Needs changesNeeds changes. This template uses 2 thing(s) that n8n 3.0 removes: Item Lists (legacy), HTML Extract. 2 breaking item(s) found. Static check, last run 2026-10-19.
What to replace before upgrading
| Removed in 3.0 | Replace with |
|---|---|
| Item Lists (legacy) Item Lists - Create Items from Body, Item Lists - Fetch Body | Split Out, Aggregate, Sort, Limit, Remove Duplicates or Summarize (match the operation used) |
| HTML Extract HTML Extract - Extract Article Title | HTML node, 'Extract HTML Content' operation |
Nodes used (6)
- Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - Item Lists
n8n-nodes-base.itemLists - HTML Extract
n8n-nodes-base.htmlExtract - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest
What it does
You still can use the app in a workflow even if we don’t have a node for that or the existing operation for that. With the HTTP Request node, it is possible to call any API point and use the incoming data in your workflow Main use cases: - Connect with apps and services that n8n doesn’t have integration with - Web scraping How it works This workflow can be divided into three branches, each serving a distinct purpose: 1.Splitting into Items (HTTP Request - Get Mock Albums): - The workflow initiates with a manual trigger (On clicking 'execute'). - It performs an HTTP request to retrieve mock albums data from "https://jsonplaceholder.typicode.com/albums." - The obtained data is split into items using the Item Lists node, facilitating easier management. 2.Data Scraping (HTTP Request - Get Wikipedia Page and HTML Extract): - Another branch of the workflow involves fetching a random Wikipedia page using an HTTP request to "https://en.wikipedia.org/wiki/Special:Random." - The HTML Extract node extracts the article title from the fetched Wikipedia page. 3.Handling Pagination (The final branch deals with handling pagination for a GitHub API request): - It sends an HTTP request to "https://api.github.com/users/that-one-tom/starred," with parameters like the page number and items per page dynamically set by the Set node. - The workflow uses conditions (If - Are we finished?) to check if there are more pages to retrieve and increments the page number accordingly (Set - Increment Page). - This process repeats until all pages are fetched, allowing for comprehensive data retrieval.