Automation / AI integrations
n8n Ecosystem
From Telegram links to the right services: rules for known domains, an LLM for new ones, and a queue between intake and processing.
The problem
Links and content from different sources must reach different services. Separate workflows make it harder to identify where processing stopped.
My contribution
I organised intake, routing and error handling on self-hosted n8n. Known domains follow rules; an LLM handles new ones. A queue separates intake from delivery to services such as Karakeep and Mealie.
Available evidence
This presentation uses an overview already published on the site. I can explain the integration choices; the real workflows contain environment details and are not public.
Usage and limits
The error workflow collects context and suggests a diagnosis. I decide how to fix the problem.