Skip to content
FlowHubFluxonLab
HTTP Request
General Automationfree

Tiny Tiny RSS new stared article saved to wallabag

by devadapted from n8n official workflow galleryUpdated Aug 2026
RequiresHTTP RequestHTTP Request
Share Post Share
MaOn clicking 'execute'On clicking 'ex…HRHTTP RequestCrCronFuFunctionIfIFNONoOpHRAuth WallabagMeMergeHRGet stared articlesGet stared arti…HRAuth TTRss123456789
1/5
STEPS · 9
Run manually by an operator

Every 10 minutes check if a new article was stared, if so, save it in wallabag to read it later.

Tags

n8nreference-only
Connects
WHTTP Request
CategoryGeneral Automation
Triggermanual
Complexitymedium
Nodes10
AddedFeb 2, 2022
W
free

Tiny tiny Rss (aka tt-rss) Feed to Mastodon

Every 10 minutes look at your published news in your Tiny tiny RSS public feed and make a toot on your mastodon. You'll need: Your mastondon URL instance Your mastondon access token Your Tiny Tiny RSS public published feed URL

by dev
CW
free

Search and preview GIFs with forms and GIPHY

Quick overview This workflow publishes an n8n Form where users enter a search term, queries the GIPHY Search API for the top 9 G-rated GIFs, and renders the results as a clickable HTML gallery on the form completion page with copy-to-clipboard links. How it works Receives a submission from an n8n Form at the gif-finder path with a required query field. Calls the GIPHY Search API with the submitted query, limiting results to 9 GIFs and filtering to G-rated content. Transforms the GIPHY response into responsive HTML that shows a grid of GIF thumbnails and a fallback message when no results are returned. Displays the generated HTML on the form completion page so users can click any GIF to copy its direct URL to the clipboard. Setup Create a GIPHY developer app and generate an API key. Add an HTTP Query Auth credential and set the api_key value to your GIPHY API key, then select it in the HTTP Request that calls GIPHY. Activate the workflow and share the n8n Form URL for the gif-finder form with your users.

by Roshan Ramani
CW
free

Monitor competitor web page changes with HTTP and Slack or Discord

Quick overview This workflow checks a list of competitor web pages every six hours, detects content changes by hashing cleaned page text, and posts a diff-style alert to a Discord or Slack channel via an incoming webhook. How it works Runs every 6 hours on a schedule. Loads a configured list of target competitor page URLs and the destination Discord/Slack webhook URL. Fetches each target page over HTTP with browser-like headers and continues even if a request fails. Converts the fetched HTML into cleaned plain text, stores a baseline on first run, and compares the latest hash against the previously saved version. When a change (or fetch error) is detected, generates a message including the URL and a small list of added/removed lines. Sends the alert message to your Discord or Slack webhook endpoint. Setup Create an incoming webhook in Discord or Slack and paste its URL into the workflow configuration. Update the target list with the competitor page names and URLs you want to monitor. Ensure n8n can persist workflow static data between runs (so change history is retained) and that your instance can reach the target sites over HTTP. Requirements n8n version 1.60+. A Discord or Slack

by Ruben Fabioux