n8n Workflow: Daily Telegram Market Briefing w/ OpenAI

Get a weekday market briefing to your Telegram—generated with OpenAI from real-time data

This n8n workflow automatically collects market prices, crypto quotes, US 10Y yields, macro calendar events, and top market news—then uses OpenAI to generate a structured market briefing and posts it to Telegram every weekday morning.

What this workflow does

• Runs on a schedule: executes every weekday at 07:45 (Europe/Berlin).
• Pulls data from multiple providers: market ETF/FX time series from Twelve Data, crypto prices from CoinGecko, the US 10-year yield series from FRED, near-term macro events from QuantGist, and recent market news from Marketaux.
• Normalizes inputs + captures issues: standardizes each provider’s response into a consistent structure and records errors or missing/invalid payloads without guessing.
• Generates a briefing with OpenAI: sends the normalized dataset and source health to OpenAI to produce a strictly JSON-formatted market briefing in Bosnian/Serbian with a single market_regime label.
• Validates and formats output: enforces allowed market_regime values and reshapes array fields, then builds an HTML Telegram message.
• Posts and archives: sends the briefing to the configured Telegram chat and inserts the full result (headline, summary, assets, events, news, drivers, opportunities, plus raw sources) into Postgres.

Use cases

• Automated daily market updates for traders or investment teams via Telegram
• SaaS operators building a “market brief” feature without manual research
• Automation engineers who want a reliable, traceable workflow using Postgres storage and source health reporting

Technical details

• n8n nodes/tools: schedule trigger, http request, code, merge, telegram, postgres
• External APIs: Twelve Data, CoinGecko, FRED, QuantGist, Marketaux
• OpenAI integration: generates strictly JSON output, then the workflow validates and converts it to an HTML Telegram message
• Setup requirement: configure credentials for each provider and ensure API authentication is passed via the configured HTTP header/query method