Service scheduling & route planner for deliveries with Notion, Telegram and Maps
Needs changesWhat this workflow does
This workflow has 10 nodes and runs when an HTTP GET request hits its webhook URL. Along the way it connects Telegram.
How it runs
Trigger: When an HTTP GET request hits its webhook URL.
- Parse Booking (Function): runs custom JavaScript (legacy Function node)
- Geocode (OSM Nominatim) (HTTP Request): calls an HTTP API
- Merge: merges the data from its input branches
- Format Geocode (Function): runs custom JavaScript (legacy Function node)
- Build Summary & Links (Function): runs custom JavaScript (legacy Function node)
- Telegram: uses Telegram
- Wait: pauses before continuing
- Respond to Webhook: sends the response back to the webhook caller
- Email → Client (Pre-arrival) (Send Email): sends an email over SMTP
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Function (legacy) in Parse Booking, Format Geocode, Build Summary & Links: replace with Code node, mode 'Run Once for All Items'.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Function (legacy) Parse Booking, Format Geocode, Build Summary & Links | Code node, mode 'Run Once for All Items' |
Nodes used (8)
- Webhook
n8n-nodes-base.webhook - Function
n8n-nodes-base.function - HTTP Request
n8n-nodes-base.httpRequest - Merge
n8n-nodes-base.merge - Telegram
n8n-nodes-base.telegram - Wait
n8n-nodes-base.wait - Send Email
n8n-nodes-base.emailSend - Respond to Webhook
n8n-nodes-base.respondToWebhook
From the author
This workflow contains community nodes that are only compatible with the self-hosted version of n8n. 🌸 Graceful Deliveries — Service Scheduling & Route Planner (Notion + Telegram) What this template does Turn new bookings into a graceful, automated delivery…