Block daily salah windows in Google Calendar with Telegram and IslamicAPI

Workflow preview

100%

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

1. Workflow Overview

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. ...

Best for

Personal Productivity automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.telegramtrigger, n8n-nodes-base.if, n8n-nodes-base.httprequest, n8n-nodes-base.set, n8n-nodes-base.code, n8n-nodes-base.googlecalendar, n8n-nodes-base.googlesheets, n8n-nodes-base.telegram

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Abdullahi Osman.

Original n8n.io source

1.1 Workflow description

Title: Block daily salah windows in Google Calendar with Telegram and IslamicAPI
Workflow name: Block daily salah windows in Google Calendar with Telegram and IslamicAPI

what this does

i built this so i can send /salah to my Telegram bot and it instantly fetches today's prayer times from IslamicAPI (using the Egyptian General Authority of Survey method for Cairo), calculates a realistic time window for each prayer, blocks all five prayers directly in Google Calendar, logs everything to a Google Sheet, then sends me a confirmation message on Telegram with the exact time windows. prayer times shift daily — this accounts for that automatically.

what's inside

Telegram Trigger — listens for incoming messages from the bot
Validate the Sender — blocks anyone who isn't me from running this
Check if it's Text — filters out non-text messages like stickers or photos
Check for Triggers — only proceeds if the message is /salah
Send an Action — sends a typing indicator while the workflow runs
Get Prayer Times — fetches today's prayer times via IslamicAPI
Map Prayer Data — extracts and formats the raw API response
Code in JavaScript — calculates start and end windows per prayer
Book for Fajr / Dhuhr / Asr / Maghrib / Isha — creates five Google Calendar events
Map Outputs — bundles all calendar IDs and times into one object
Store Prayer Bookings — appends a row to Google Sheets for tracking
Send the Message — sends a formatted confirmation back to me on Telegram
Error Trigger — catches failures and logs them to a separate sheet

APIs used

IslamicAPI — fetches today's accurate prayer times by coordinates
Google Calendar — creates and holds the five prayer block events
Google Sheets — logs each booking run with full timestamps and event IDs
Telegram Bot API — receives the /salah command and sends the confirmation

estimated cost per run

free — IslamicAPI is free forever, Google and Telegram APIs have no per-call cost at this usage level.

Created by Gurey AI

other workflows i've built

more workflows coming soon — follow along

Need Help?

Email me with your questions my email or ask in the Forum! Happy Hacking!

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Telegram Trigger

Type / Role: n8n-nodes-base.telegramTrigger - telegramTrigger
Config choices: Version 1.2

Block 2 - Validate the sender

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.3

Block 3 - Check if it's Text

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.3

Block 4 - Get prayer times

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.4

Block 5 - Map Prayer data

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 6 - Check for triggers

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.3

Block 7 - Code in JavaScript

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 8 - Book for Fajr

Type / Role: n8n-nodes-base.googleCalendar - googleCalendar
Config choices: Version 1.3

Block 9 - Book for Duhr

Type / Role: n8n-nodes-base.googleCalendar - googleCalendar
Config choices: Version 1.3

Block 10 - Book for Asr

Type / Role: n8n-nodes-base.googleCalendar - googleCalendar
Config choices: Version 1.3

Block 11 - Book for Maghrib

Type / Role: n8n-nodes-base.googleCalendar - googleCalendar
Config choices: Version 1.3

Block 12 - Book for Isha

Type / Role: n8n-nodes-base.googleCalendar - googleCalendar
Config choices: Version 1.3

Block 13 - Map outputs

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 14 - Store Prayer Bookings

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.7

Block 15 - Send the message

Type / Role: n8n-nodes-base.telegram - telegram
Config choices: Version 1.2

Block 16 - Send an action

Type / Role: n8n-nodes-base.telegram - telegram
Config choices: Version 1.2

Block 17 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 18 - Sticky Note1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 19 - Sticky Note2

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 20 - Sticky Note3

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 21 - Sticky Note4

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 22 - Sticky Note5

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 23 - Sticky Note6

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 24 - Sticky Note7

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Showing the first 24 of 34 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow	Block daily salah windows in Google Calendar with Telegram and IslamicAPI
Complexity	advanced
Nodes	34
Categories	Personal Productivity
Author	Abdullahi Osman
Published	18 Apr 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/15124/15124.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Personal Productivity workflows

Frequently asked questions

What does Block daily salah windows in Google Calendar with Telegram and IslamicAPI do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Personal Productivity use case.

Abdullahi Osman

6 workflows

Nodes

n8n-nodes-base.telegramtrigger n8n-nodes-base.if n8n-nodes-base.httprequest n8n-nodes-base.set n8n-nodes-base.code n8n-nodes-base.googlecalendar n8n-nodes-base.googlesheets n8n-nodes-base.telegram

Complexity

advanced

Published 18 Apr 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/15124/15124.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Manage Google Calendar events with Zalo Bot, OpenAI and Gemini

## Quick Overview This workflow lets users manage Google Calendar by sending text or voice messages to a Zalo Official Account bot, transcribing voice notes with Google Gemini and using an OpenAI-powered agent to create, update, list, or delete events, then replying in Zalo with the result. ## How it works 1. Receives an incoming text or voice message through a Zalo Bot trigger. 2. Sends a typing indicator back to the Zalo chat and normalizes key message fields (chat ID, type, text, and voice URL). 3. If the message is a voice note, sends the audio URL to Google Gemini to transcribe it into text. 4. Sends the combined text/transcription to an OpenAI chat model agent that interprets the request in Vietnamese and decides whether to list, create, update, or delete a Google Calendar event. 5. Uses Google Calendar tools to get events and then create, update, or delete the targeted event based on the agent’s extracted parameters. 6. Sends the agent’s Markdown-formatted response back to the user in Zalo, and posts an error message to Zalo if the agent run fails. ## Setup 1. Install the community node package `n8n-nodes-zalo-bot-official` and restart n8n if required. 2. Connect your Zalo Bot API credentials and configure the Zalo webhook URL in your Zalo Official Account so incoming messages reach this workflow. 3. Add a Google Calendar OAuth2 credential and set the target calendar account (currently configured as `[email protected]`) for all calendar operations. 4. Add a Google Gemini (PaLM) API credential for audio transcription and ensure voice messages include a reachable `voice_url`. 5. Add an OpenAI API credential, select the chat model you want to use (currently `gpt-5-mini`), and adjust the system prompt/tone if needed.

View

Screen LinkedIn jobs and generate tailored resume and cover PDFs with Anthropic and DocRaptor

## Quick Overview This workflow collects your job preferences and resume via an n8n form, scrapes fresh LinkedIn job listings with Apify, screens and ranks matches using Anthropic Claude, generates tailored resume and cover letter PDFs via DocRaptor, then emails them to you and logs each match in Google Sheets. ## How it works 1. Receives a form submission with your email, target role, seniority, locations, skills, deal-breakers, and resume text. 2. Calls the Apify LinkedIn Job Scraper API to fetch up to 150 jobs posted in the last 7 days for the provided keywords and location. 3. Removes duplicates and filters out obvious mismatches based on seniority, required years of experience patterns, and location rules. 4. Uses Anthropic Claude (Haiku) to score each remaining job for relevance and eligibility and returns a JSON verdict and fit score. 5. Ranks the results, drops rejected roles, and keeps the top five best-scoring matches. 6. Uses Anthropic Claude (Sonnet) to generate a structured resume JSON and cover letter JSON tailored to each shortlisted job using only facts from your provided profile. 7. Renders the resume and cover letter to HTML, converts them to PDF files with DocRaptor, emails the PDFs to you via Gmail, and appends a tracker row to Google Sheets. ## Setup 1. Add credentials for Anthropic (Claude), Gmail, Google Sheets, and DocRaptor (HTTP Basic Auth with your API key as the username and a blank password). 2. Replace YOUR_APIFY_TOKEN in the Apify HTTP request URL and ensure you have access to the Apify LinkedIn Jobs Scraper actor endpoint used in the workflow. 3. Create a Google Sheet with a “Tracker” tab and set the document ID (YOUR_TRACKER_SHEET_ID) to match your sheet. 4. If you want non-watermarked PDFs, set DocRaptor "test" to false in both PDF generation requests.

View

Triage and route tasks with Google Sheets, GPT-4o-mini, Gmail, Slack, and Google Tasks

## Quick Overview This workflow collects tasks via a webhook, stores validated tasks in Google Sheets, and runs a daily prioritization routine that creates urgent items in Google Tasks with Slack alerts while summarizing medium/low tasks with OpenAI and emailing the digest via Gmail. ## How it works 1. Receives a POST webhook request containing task details and normalizes fields like priority and due date. 2. Validates required fields (including allowed priority values) and rejects invalid submissions with an error. 3. Appends valid tasks to Google Sheets with a pending status and returns a success response to the webhook caller. 4. Runs daily on a schedule, reads tasks from Google Sheets, keeps only pending items, removes duplicates, and sorts them by priority. 5. For high-priority tasks, creates a Google Tasks item and sends a Slack alert. 6. For medium and low-priority tasks, compiles a digest, generates an email-ready summary with OpenAI, and sends it via Gmail. 7. Updates each handled task in Google Sheets with a Processed status and a processed timestamp. ## Setup 1. Create a Google Sheet with columns for taskName, priority, category, dueDate, status, createdAt, and processedAt, and update the spreadsheet and sheet IDs in the Google Sheets steps. 2. Add Google Sheets OAuth2 credentials for both reading and updating/appending rows. 3. Add credentials for Google Tasks, Slack (OAuth2), Gmail, and OpenAI, and set the target Google Task list, Slack destination, and email recipients/subject as needed. 4. Copy the webhook URL from the webhook trigger and configure your task intake source to send POST requests with fields like "Task Name", "Priority", "Category", and "Due Date". 5. Adjust the schedule time and any validation rules (required fields and accepted priority values) to match your process.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Block daily salah windows in Google Calendar with Telegram and IslamicAPI

Workflow preview

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

what this does

what's inside

APIs used

estimated cost per run

Created by Gurey AI

other workflows i've built

Need Help?

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Telegram Trigger

Block 2 - Validate the sender

Block 3 - Check if it's Text

Block 4 - Get prayer times

Block 5 - Map Prayer data

Block 6 - Check for triggers

Block 7 - Code in JavaScript

Block 8 - Book for Fajr

Block 9 - Book for Duhr

Block 10 - Book for Asr

Block 11 - Book for Maghrib

Block 12 - Book for Isha

Block 13 - Map outputs

Block 14 - Store Prayer Bookings

Block 15 - Send the message

Block 16 - Send an action

Block 17 - Sticky Note

Block 18 - Sticky Note1

Block 19 - Sticky Note2

Block 20 - Sticky Note3

Block 21 - Sticky Note4

Block 22 - Sticky Note5

Block 23 - Sticky Note6

Block 24 - Sticky Note7

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions