Block daily salah windows in Google Calendar with Telegram and IslamicAPI
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 19 nodes and runs on Telegram events (message) (plus 1 other trigger). Along the way it connects Telegram, Google Calendar and Google Sheets. It also calls islamicapi.com over HTTP.
How it runs
Trigger: On Telegram events (message) (plus 1 other trigger).
- Validate the sender (If): checks a condition and branches into true / false
- Append row in sheet (Google Sheets): append
- Check if it's Text (If): checks a condition and branches into true / false
- Send The error (Telegram): uses Telegram
- Check for triggers (If): checks a condition and branches into true / false
- Send an action (Telegram): send chat action
- Get prayer times (HTTP Request): calls islamicapi.com
- Map Prayer data (Edit Fields (Set)): sets 4 fields: Prayers, Readable Gregorian Date, Hijri Date…
- Code: runs custom JavaScript code
- Book for Fajr (Google Calendar): uses Google Calendar
…plus 7 more steps. See the full node list below.
Services it uses
HTTP calls to: islamicapi.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (9)
- Telegram Trigger
n8n-nodes-base.telegramTrigger - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - Google Calendar
n8n-nodes-base.googleCalendar - Google Sheets
n8n-nodes-base.googleSheets - Telegram
n8n-nodes-base.telegram - Error Trigger
n8n-nodes-base.errorTrigger
From the author
clients kept booking meetings during my prayer times. i'd either miss a prayer or scramble to reschedule. the problem wasn't the clients — it was that my calendar had no blocked windows for salah. i needed a way to block those times every day, automatically,…