Latenode
Rss.app
MongoDB

Automate RSS feed monitoring and forward articles to webhooks

This automation template helps users monitor an RSS feed for new articles and automatically transmit the extracted data to a designated webhook URL for further processing or storage.

It filters the articles based on keywords, checks them against a MongoDB database to identify unique links, and then sends the unique article links to different webhooks depending on the article content. The workflow can be triggered manually or on a recurring schedule using a Cron node. It leverages various nodes such as RSS Feed Read, IF, SplitInBatches, MongoDB: Find Article, Merge, MongoDB: Insert, and Webhook to streamline the data extraction, filtering, and forwarding process.

Updated Apr 2, 2026Est. run: 15sEst. cost: $0.001
How Latenode estimates time and cost

Latenode bills workflow runs in credits: 1 credit = 30 seconds of processing. Minimum charge per run depends on your plan. Plug-and-Play (PnP) AI nodes are billed separately—each PnP token is $1 USD, charged pay-as-you-go at vendor cost plus a small processing fee, with no API keys required.

Full pricing — how credits work →
Development & API

Workflow preview

What this template does

  • Extracts new articles from an RSS feed
  • Filters articles based on keywords
  • Checks article links against a MongoDB database
  • Sends unique article links to designated webhooks
  • Enables manual or scheduled execution of the workflow

How it works

1
Trigger

Read RSS Feed

The workflow starts by reading the specified RSS feed using the RSS Feed Read node. This retrieves the latest article titles, links, and other relevant metadata from the feed.

2
Logic

Check MongoDB

For each article retrieved from the RSS feed, the workflow checks the MongoDB database to see if the article link already exists. This deduplicates the data and ensures only unique articles are processed.

3
Action

Insert to MongoDB

Any article links that are not found in the MongoDB database are then inserted, along with their titles and other metadata, to store the unique articles for future reference.

4
Action

Send to Webhook

The unique article links are then sent to the designated webhook URL for further processing or storage, such as triggering additional workflows or integrating the data with other systems.

Setup guide

1

Add RSS Feed URL

In the Latenode builder, add an RSS Feed Read node and configure the RSS feed URL you want to monitor.

2

Configure MongoDB Connection

Add a MongoDB: Find Article node and a MongoDB: Insert node. In the node settings, configure the connection details to your MongoDB database, including the host, port, username, and password using the Latenode Secrets panel.

3

Set Up Webhook URLs

Add Webhook nodes to the workflow and configure the respective webhook URLs where you want to send the unique article links.

4

Define Filtering Keywords

In the IF node settings, configure the keyword patterns you want to use to filter the articles, such as "realtors", "real estate", "restaurant(s)".

5

Map Data Fields

For each node in the workflow (RSS Feed Read, MongoDB: Find Article, MongoDB: Insert, Webhook), map the relevant data fields to ensure the data is properly extracted, stored, and forwarded.

Requirements

RSS feed URL to monitor for new articles
Webhook URL to transmit extracted article data
MongoDB database connection details (host, port, username, password) to store and check unique article links
Ability to configure the keywords used to filter relevant articles within the Latenode workspace

FAQ

Common questions about this template

Each run uses credits on your Latenode plan. We charge for processing time (1 credit = 30 seconds). Your actual cost depends on your plan and how long the run takes. See pricing plans for plans and how credits work.
Contact support →

More templates

You might also like

Browse all templates →
Development & API

Automatically route Gravity Forms submissions to webhooks

This automation allows users to trigger a custom webhook URL whenever a new entry is submitted through a Gravity Forms application. By setting up this workflow, users can easily manage information from the form submissions by sending the data to a specified webhook endpoint. The automation involves integrating Gravity Forms, which captures the form submissions, and a webhook service like Zapier to fire off the POST requests to the configured URL. This enables users to automate downstream actions or processes based on the incoming form data without having to manually monitor or forward the submissions.

7s$0.0004
Development & API

Automatically create new Knack records from incoming webhooks

This automation allows users to automatically create new records in their Knack database whenever data is received via a webhook. It eliminates the need for manual data entry by capturing information from external sources or custom tools and storing it in the user's Knack application. The flow is triggered by a 'Catch Hook' event that listens for POST, PUT, or GET requests made to a Zapier webhook URL, allowing the automation to receive data from any system that can send a webhook. The captured data is then used to create a new record in the user's Knack database.

7s$0.0004
Development & API

Automatically create RD Station conversion events from web hooks

This automation scenario allows users to automatically create conversion events in the RD Station marketing platform whenever a webhook is received. It simplifies the process of tracking and reporting on marketing leads and conversions by capturing data from incoming webhooks and using it to generate corresponding events in RD Station. The integration handles the end-to-end workflow, from catching the webhook to registering the conversion event, without requiring manual data entry or coordination between systems.

8s$0.0005