Aggregate news articles from NewsAPI, Mediastack & CurrentsAPI into database
Ready for 3.0What this workflow does
This workflow has 29 nodes and runs on a schedule (every day at 06:00) (plus 3 other triggers). Along the way it connects NocoDB. It also calls newsapi.org, api.currentsapi.services and api.mediastack.com over HTTP.
How it runs
Trigger: On a schedule (every day at 06:00) (plus 3 other triggers).
- currentsapi config (Edit Fields (Set)): sets 2 fields: article_limit, category
- mediastack categories (Edit Fields (Set)): sets 2 fields: article_limit, categories
- call newsapi.org - Top Headlines (HTTP Request): calls newsapi.org
- newsapi.org categories (Edit Fields (Set)): sets 2 fields: article_limit, categories
- call currentsapi (HTTP Request): calls api.currentsapi.services
- Itemize Mediastack Categories (Code): runs custom JavaScript code
- Split Out: splits a list into separate items
- Itemize Newsapi Categories (Code): runs custom JavaScript code
- Split Out: splits a list into separate items
- Loop Over Mediastack (Loop Over Items (Split in Batches)): loops over the items in batches
…plus 15 more steps. See the full node list below.
Services it uses
HTTP calls to: newsapi.org, api.currentsapi.services, api.mediastack.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Split Out
n8n-nodes-base.splitOut - Edit Fields (Set)
n8n-nodes-base.set - NocoDB
n8n-nodes-base.nocoDb - HTTP Request
n8n-nodes-base.httpRequest - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Code
n8n-nodes-base.code - Wait
n8n-nodes-base.wait - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches
From the author
This workflow pulls news articles from NewsAPI, Mediastack, and CurrentsAPI on a scheduled basis. Each provider’s results are normalized into a consistent schema, then written into your database (NocoDB by default). Use case: automated aggregation of…