Review expenses: Telegram
Starts when someone submits the form across Telegram, PostgreSQL and Slack, pauses on a Wait node until it is time to continue, then branches on the check before anything is written. Built for approvals, around a "Keep Valid Tasks" step, in 23 documented nodes.
Review expenses with Telegram and PostgreSQL on autopilot. An original, ready-to-import n8n workflow built around the 'Approval Workflow' pattern for software development & devops. It starts from a form and orchestrates 23 nodes across Telegram, HTTP / REST API, PostgreSQL. Retry-on-fail is enabled on external calls. Import the JSON, add your credentials, and adapt the parameters. Your team sees the right data at the right time.
Key benefits
- ✓Keeps Telegram and PostgreSQL in step for approvals, without anyone re-typing a row
- ✓Safe to re-run: records already in Telegram or PostgreSQL are skipped, across all 23 nodes of this approvals build
- ✓A failed Telegram or PostgreSQL call is retried rather than dropped, at any of the 23 nodes in this approvals build
- ✓Branches rejoin before Telegram, so a approvals run reports once rather than 23 times
- ✓The pause before Telegram is durable — a approvals run survives a restart
Use cases
- →Teams keeping Telegram and PostgreSQL aligned by hand for approvals
- →Approvals sequences that run over days and must survive a restart before Telegram
- →Intake checked for completeness before it is stored in Telegram, for approvals
- →Approvals work where "Keep Valid Tasks" is still a manual step before Telegram
Integrations
Workflow preview (23 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (23 nodes)
A look at the node types this workflow uses. No purchase required — full parameters and credentials are yours after you buy.
From download to running in 3 steps
- 1Import. In n8n, open Workflows → menu → “Import from File” and pick the downloaded JSON.
- 2Connect. Add your own credentials on the app nodes - n8n highlights exactly which ones need them.
- 3Activate. Run it once to test, then toggle Active. The automation is live.
What you'll learn
Production levelProduction-grade: idempotency, dead-letter handling, and reconciliation included.
- •Pausing a workflow on a Wait node until a human decides
- •Embedding a resume URL so approving is one click
- •Branching cleanly on approve versus decline
Every node carries its own documentation on the canvas, plus notes explaining why the architecture was built this way, a credential setup guide, troubleshooting, and three practice exercises. Sample data comes pinned to the trigger, so you can hit Execute and watch data flow before connecting a single account.
Common questions
What exactly do I get?
The complete, ready-to-import n8n workflow as a JSON file, delivered instantly after payment. Import it into your own n8n (cloud or self-hosted), add your credentials, and it runs.
How do I import it into n8n?
In n8n, open Workflows, click the three-dot menu, choose “Import from File”, and select the downloaded JSON. Then connect your own app credentials on the highlighted nodes.
Do I need anything else for it to work?
You need your own n8n instance and accounts/credentials for the apps this workflow connects to (Telegram, HTTP / REST API, PostgreSQL, Slack, …). No coding is required.
What if it doesn't work for me?
If the file is faulty, won't import, or isn't as described, contact us within 7 days and we'll fix it or refund you - see our refund policy.
Can I modify or resell it?
You can freely adapt and use it in your own or your clients' projects. Reselling or redistributing the template file itself is not permitted.
Related templates
Review requests: PostgreSQL
Task routing on n8n: runs when a form is submitted across PostgreSQL, Google Sheets, Telegram and Slack, starting at "Normalize Task Payload". 23 documented nodes.
Orchestrate a routine task: Google Sheets for helpers
Helpers on n8n: runs on a schedule across Google Sheets, PostgreSQL, Telegram and Slack, starting at "Fetch Changes Since Watermark". 23 documented nodes.
Back up key records: PostgreSQL
Data transforms on n8n: runs on a schedule across PostgreSQL, Slack, Google Sheets and Telegram, starting at "Fetch Changes Since Watermark". 21 documented nodes.
Archive key records for webhooks
Webhooks on n8n: runs on a schedule across Google Sheets, PostgreSQL, Google Drive, Telegram and Slack, starting at "Export All Rows (Google Sheets)". 23 documented nodes.