HumationHuman + Automation
Back to Catalog

Location-based triggered reminder via Telegram Bot (iOS)

RoninimousRoninimous
576 views
2/3/2026
JiraConfluenceContent SyncIntegrationAutomation
Official Page

This workflow integrates iOS Shortcuts with n8n to create a simple, automatic location-based reminder system. When the user arrives at a specified location, an automation in the Shortcuts app sends a webhook trigger to n8n. If the trigger matches predefined date and time conditions, n8n sends a Telegram message reminder to the user.

This is perfect for repetitive weekly tasks like taking out the bins, customized with conditions for day and time.

Key Features

  • Location-Based Trigger: Uses iOS Shortcuts automation to start the workflow upon arrival at a specific location.
  • Time and Day Validation: Logic in n8n checks current weekday and time to ensure reminders are sent only when appropriate.
  • Telegram Integration: Sends reminders directly to your Telegram account using your bot.
  • Minimal Setup: Uses native iOS and simple webhook setup in n8n.

How It Works

  1. iOS Shortcut Trigger: When the user arrives at a designated location, the iOS shortcut sends a GET request to the n8n webhook.
  2. n8n Webhook Node: Receives the request and triggers the workflow.
  3. Conditional Check: An IF node checks if the current time is after 4:00 PM and it's a Wednesday (or any other configured condition).
  4. Telegram Node: If the condition passes, n8n sends a message like "Don't forget to take the bins out." to your Telegram bot.

Setup Instructions

  1. Create a Telegram Bot:

    • Use @BotFather to create a bot and obtain your bot token.
    • Add Telegram API credentials in n8n with your bot token.

  2. Setup iOS Shortcut:

    • Open the Shortcuts app on your iPhone.
    • Go to the Automation tab → Tap + → Create Personal Automation.
    • Choose Arrive → Select a location.
    • Add action: Get Contents of URL. Method: GET, URL: your n8n Webhook URL (e.g. https://n8n.yourdomain.com/webhook/your-path).
    • Save the automation. (You can also test the automation by pressing the Play button)

  3. Import Workflow into n8n:

    • Load the provided workflow JSON.
    • Set your webhook path and Telegram credentials.
    • Adjust the logic in the IF node to your usecase. In my case, I check if today is Wednesday and after 4 PM until Midnight.

  4. Expose n8n Publicly: Ensure your n8n instance is publicly accessible via HTTPS so the shortcut can reach it.

Customization Guidance

  • Change Reminder Message: Modify the text inside the Telegram node to suit different reminders.
  • Add More Conditions: Extend the logic to support more days, hours, or different trigger messages.
  • Add Multi-Channel Output: Send reminders via email, SMS, or Slack in addition to Telegram.
  • Use More Triggers: Expand to other types of shortcut triggers (e.g. NFC tag, leaving location, time of day).

Security and Implementation

  • Webhook Protection: Avoid using easily guessable webhook URLs.
  • Secure Telegram Token: Store your bot token securely in n8n credentials, not in plain workflow text.
  • Limit Shortcut Scope: Only trigger the shortcut at trusted locations or with secure iCloud sync.
  • Automation Permissions: Ensure your iPhone allows shortcut automations to run without confirmation.

Benefits

  • Automates repetitive location-based reminders without user interaction.
  • Provides a lightweight, native solution using iOS and n8n with no extra apps.
  • Keeps you on track for routine tasks like garbage days, medicine reminders, or arrival-based tasks.
  • Easily extendable for multiple locations or trigger conditions.

n8n Location-Based Triggered Reminder via Telegram Bot

This n8n workflow enables you to set up location-based reminders delivered directly to your Telegram bot. It acts as a backend for a system that triggers events based on geographical coordinates, allowing you to receive timely notifications when you enter or leave a specific area.

What it does

This workflow automates the following steps:

  1. Receives a Webhook Trigger: It listens for incoming HTTP requests, which are expected to contain location data or a trigger event from an external service (e.g., an iOS app that detects location changes).
  2. Conditional Logic: It evaluates the incoming data using an "If" node. This node can be configured to check specific conditions (e.g., if a certain location ID is matched, or if a specific event type is present).
  3. Sends Telegram Message: If the condition in the "If" node is met, it sends a predefined message to a specified Telegram chat via your Telegram bot.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance (self-hosted or cloud).
  • Telegram Bot: A Telegram bot token and the chat ID of the recipient. You can create a bot via BotFather on Telegram.
  • External Location Trigger: An external service or application (e.g., an iOS app with geofencing capabilities) that can send HTTP POST requests to the n8n Webhook URL when a location-based event occurs.

Setup/Usage

  1. Import the Workflow:

    • Copy the provided JSON code for this workflow.
    • In your n8n instance, click "New" to create a new workflow.
    • Go to "File" > "Import from JSON" and paste the copied JSON.

  2. Configure the Webhook Node:

    • Click on the "Webhook" node.
    • The "Webhook URL" will be automatically generated once the workflow is activated. Copy this URL. This is the endpoint your external location trigger service will send data to.
    • Ensure the "HTTP Method" is set to POST (or GET if your external service uses it, but POST is generally recommended for sending data).

  3. Configure the If Node:

    • Click on the "If" node.
    • Define your conditions based on the data you expect from your external location trigger. For example:
      • If your external service sends a locationId in the JSON body, you might set a condition like {{ $json.locationId === "home" }}.
      • If it sends a triggerType (e.g., "enter" or "exit"), you could use {{ $json.triggerType === "enter" }}.
    • The "True" branch will execute if the condition is met, and the "False" branch will execute otherwise.

  4. Configure the Telegram Node:

    • Click on the "Telegram" node.
    • Select or create a new Telegram API credential. You will need your Telegram bot token.
    • In the "Chat ID" field, enter the ID of the Telegram chat where you want to receive reminders.
    • In the "Text" field, compose the message you want to send. You can use expressions to include dynamic data from the webhook, e.g., {{ $json.locationName }} reminder: Don't forget your keys!.

  5. Activate the Workflow:

    • Once all nodes are configured, click the "Activate" toggle in the top right corner of the n8n editor to make the workflow live.

Now, whenever your external location trigger sends a request to the Webhook URL that matches the conditions in the "If" node, you will receive a reminder via your Telegram bot.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942