Send scheduled financial digests to Telegram from Notion with multi-schedule alerts
Who’s it for
Solo founders and spreadsheet gremlins who track everything in Notion and want crisp Telegram pings without opening a single page.
What it does
This workflow runs on daily, weekly, and monthly schedules, queries multiple Notion databases, summarizes key numbers, formats human‑readable messages, and sends them to Telegram.
Out of the box it sends:
- Daily: Total Expenses Today (sum of
Debitin Financial Transaction since start of day). - Weekly: Total Expenses This Week, Monthly Budget Left/Spent per budget item, Financial Obligations due (from Scheduler).
- Month End (28th by default): Total Expenses This Month, Total Income This Month, Funds status.
- Month Start: Liquidity snapshot — balances for Liquid and Semi Liquid assets (from Assets and Liabilities).
Messages are built via Code nodes (simple JS) and delivered to Telegram.
How it works (nodes & flow)
- Schedule Triggers: Daily, Weekly, Monthly (start & end).
- Notion queries (selected DBs):
- Financial Transaction: filters on
Created time,Type=Debit/Invoice. - Budget:
Currently Applicable = true,Payment Schedule Type = Monthly, formula:Monthly Budget Left. - Income: month-to-date
Created timefilter. - Funds: reads
Amount Left,Amount Spent,Amount Needed. - Scheduler:
Next Dateon or before now,Type = Financial,Repeat Type != off. - Assets and Liabilities:
Liquidity=LiquidorSemi Liquid.
- Financial Transaction: filters on
- Summarize nodes: sum
property_cost/property_balancefields. - Set/Code nodes: reshape Notion properties (e.g.,
property_next_date.start→next-date) and format text blocks like:Total Expenses Today - Rs XMonthly Budget Left - <list>Invoices still to pay - <list>Funds Info - spent/neededLiquidity Balance - <list>
- Telegram: sends the composed message to
chatId.
> Tip: If your Notion property names differ, adjust the filters and Set node mappings accordingly.
Requirements
- n8n (Cloud or self‑hosted)
- Notion workspace with Personal Finance System Notion template cloned into your workspace.
- Telegram account (for bot + chat)
Setup (quick)
-
Telegram
- Create a bot via @BotFather → get Bot Token.
- Get your Chat ID (n8n Telegram Trigger “Run once”, then message your bot, copy
chat.id). - In the Telegram Send node, set
chatId(or use an env var/secret).
-
Notion
- Create an Internal Integration, copy the token, and share each DB with the integration.
- In the Notion nodes, select your Notion credential and map the DB IDs (already present in the JSON).
-
n8n Credentials
- Notion API credential: paste the integration token.
- Telegram API credential: paste Bot Token and set
chatIdin the node or via expression.
-
Time windows
- Daily:
on_or_after: $now.startOf('day') - Weekly:
on_or_after: $now.startOf('week') - Monthly:
on_or_after: $now.startOf('month') - Monthly end trigger runs on day
28by default — change in the Schedule node.
- Daily:
Customization
- Change the date ranges, add currency symbol, or swap summaries for tables.
- Add more filters (labels, categories) to the Notion nodes.
- Replace Telegram with Slack/Email by swapping the final node.
- To avoid “expects dateTime but got object”, convert
$nowto string:{{$now.toISO()}}or parse Notion dates withDateTime.fromISO(...)as needed.
Example messages
Total Expenses Today - Rs 1,840
Monthly Budget Left - 3
1) Groceries: Rs 4,500
2) Dining Out: Rs 1,200
3) Utilities: Rs 800
Invoices still to pay - 2
1) Figma Pro: Rs 3,000
2) AWS: Rs 2,450
Why this is useful
- Keeps your spend & cash visibility tight without opening Notion.
- Turns your financial system into low‑effort telemetry — you just look at Telegram.
Credentials you’ll likely name in n8n
- Notion:
Notion account - Telegram:
Accountant AI
> Works great with the “Personal Finance System” style schemas. Adjust property keys (property_*) if your Notion columns differ.
Send Scheduled Financial Digests to Telegram from Notion with Multi-Schedule Alerts
This n8n workflow automates the process of sending scheduled financial digests to Telegram, pulling data from Notion. It's designed to provide timely updates and alerts based on your financial tracking in Notion, with the flexibility of multiple scheduling options.
What it does
This workflow performs the following key steps:
- Triggers on Schedule: The workflow is activated based on a predefined schedule (e.g., daily, weekly, monthly).
- Retrieves Data from Notion: It connects to your Notion database to fetch relevant financial information.
- Processes and Summarizes Data: The retrieved data is processed and summarized using a Code node, likely to format it into a digestible financial digest.
- Transforms Data for Output: An "Edit Fields (Set)" node is used to prepare the data for the Telegram message, ensuring it's in the correct format.
- Sends Digest to Telegram: The summarized financial digest is then sent as a message to a specified Telegram chat.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Notion Account: A Notion account with a database containing your financial data. You will need to create a Notion integration and grant it access to your database.
- Telegram Account: A Telegram account and a Telegram Bot. You will need the Bot Token and the Chat ID where you want to send the messages.
- Notion Credentials: Configured Notion API credentials in n8n.
- Telegram Credentials: Configured Telegram API credentials (Bot Token) in n8n.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Credentials:
- Notion: Set up your Notion API credentials. Ensure your Notion integration has access to the database you intend to query.
- Telegram: Set up your Telegram API credentials with your Bot Token.
- Configure Notion Node:
- In the "Notion" node, select the database you want to pull financial data from.
- Adjust any filters or properties as needed to retrieve the specific financial information relevant to your digest.
- Configure Code Node:
- Review and modify the "Code" node to customize how your financial data is processed and formatted into a digest. This is where you'll define the logic for summarizing your financial overview.
- Configure Edit Fields Node:
- Adjust the "Edit Fields (Set)" node if you need to further refine the data structure or add/remove fields before sending to Telegram.
- Configure Telegram Node:
- In the "Telegram" node, specify the
Chat IDwhere the financial digest should be sent. - Customize the message text to display the summarized financial information from the previous nodes.
- In the "Telegram" node, specify the
- Configure Schedule Trigger:
- Set the "Schedule Trigger" node to your desired frequency (e.g., daily, weekly, monthly) for sending the financial digests.
- Activate the Workflow: Once configured, activate the workflow to start sending scheduled financial digests.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.