Create invoices: Telegram & Slack
Fires the moment a webhook arrives across Telegram, Slack and Google Drive, rolls the rows up into a few numbers, then runs the custom logic in a Code node. Built for invoices, around a "Gather API Numbers" step, in 13 documented nodes.
Create invoices with HTTP / REST API and Google Drive at scale. An original, ready-to-import n8n workflow built around the 'Document Generation' pattern for legal & compliance. It fires on a webhook and orchestrates 13 nodes across Telegram, Slack, HTTP / REST API. Retry-on-fail is enabled on external calls. Import the JSON, add your credentials, and adapt the parameters. Nothing slips through the cracks.
Key benefits
- ✓Keeps Telegram and Slack in step for invoices, without anyone re-typing a row
- ✓A failed Telegram or Slack call is retried rather than dropped, at any of the 13 nodes in this invoices build
- ✓Every invoices run leaves an audit row behind, alongside Telegram
- ✓Fans the same result out to Google Drive in the same run, for invoices
- ✓Pinned sample data ships with it — run all 13 nodes for invoices before wiring Telegram
Use cases
- →Teams keeping Telegram and Slack aligned by hand for invoices
- →Pushing invoices events into Telegram and Slack the moment they land, not on the next poll
- →Invoices work where "Gather API Numbers" is still a manual step before Telegram
- →Invoices work that only reaches Telegram when a webhook arrives, when someone remembers to start it
Integrations
Workflow preview (13 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (13 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
Core levelA compact production shape: validation and error handling without extra machinery.
- •Moving data between Google Drive, Telegram and Slack in a single run
- •Rolling many rows up into a few reportable numbers
- •Normalising timestamps before anything downstream compares them
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, Slack, HTTP / REST API, Google Drive). 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
Issue contracts with Telegram
Ocr & extraction on n8n: runs when a webhook arrives across Telegram, Slack and Google Drive, starting at "Gather API Numbers". Rolls the rows up into a few numbers. 14 documented nodes.
Generate invoices: Slack, webhook
Summarization on n8n: runs when a webhook arrives across Slack, Google Sheets, Google Drive and Telegram, starting at "Gather API Numbers". Drops anything it has already handled. 23 documented nodes.
Issue quotes with Telegram
Ocr & extraction on n8n: runs when a webhook arrives across Telegram, Slack and Google Drive, starting at "Gather API Numbers". Rolls the rows up into a few numbers. 13 documented nodes.
Digest documents: Slack for ocr & extraction
Ocr & extraction on n8n: runs when a webhook arrives across Slack, Google Sheets, Google Drive and Telegram, starting at "Normalize Document Payload". 22 documented nodes.