Look for the “chat” section<\/strong> within the JSON data<\/li>\n<\/ol>\n\n\n\nIt looks something like this:<\/p>\n\n\n\n
{\n \"ok\": true,\n \"result\": [\n {\n \"update_id\": 123456789,\n \"message\": {\n \"message_id\": 1,\n \"from\": {\n \"id\": 987654321,\n \"is_bot\": false,\n \"first_name\": \"Your Name\"\n },\n \"chat\": {\n \"id\": 987654321,\n \"first_name\": \"Your Name\",\n \"type\": \"private\"\n },\n \"date\": 1640000000,\n \"text\": \"Hey Ucartz\"\n }\n }\n ]\n}<\/code><\/pre>\n\n\n\n9. Find the “id” field inside the “chat” object
Build the Workflow Node<\/h3>\n\n\n\n\nAdd Telegram Node:<\/strong> In your workflow, add a Telegram node.<\/li>\n\n\n\nSelect Action:<\/strong> Set the Resource to Message<\/code> and the Operation to Send Message<\/code> .<\/li>\n<\/ol>\n\n\n\n\nEnter Chat ID:<\/strong> Paste the number you found in Part 3 into the Chat ID field.<\/li>\n<\/ol>\n\n\n\n\nAdd Text:<\/strong> Type your message (for your project, this is where you will use the expression from the HTTP Request node).<\/li>\n\n\n\nTest:<\/strong> Click Execute Step to see the message pop up on your phone<\/li>\n<\/ol>\n\n\n\nStep 4: Creating Your First n8n Workflow with Telegram Notifications<\/h2>\n\n\n\n
Set the Alarm (Schedule Trigger)<\/h3>\n\n\n\n\nOpen n8n on your laptop and create a New Workflow<\/strong>.<\/li>\n\n\n\nClick the +<\/strong> button and search for the Schedule Trigger<\/strong> node.<\/li>\n<\/ol>\n\n\n\n\nSet the Trigger Interval<\/strong> to “Days.”<\/li>\n\n\n\nPick a time (e.g., 08:00) when you want your motivation to arrive.<\/li>\n<\/ol>\n\n\n\nFetch the Quote (HTTP Request)<\/h3>\n\n\n\n\nAdd a new node after the trigger and search for HTTP Request<\/strong>.<\/li>\n<\/ol>\n\n\n\n\nSet the Method<\/strong> to GET<\/code>.<\/li>\n\n\n\nPaste this URL into the URL<\/strong> zenquotes<\/code> (This is a free API that doesn’t require a password or key).<\/em><\/li>\n<\/ol>\n\n\n\n\nClick Execute Node<\/strong>. You should see a JSON response with a “q” (quote) and “a” (author).<\/li>\n<\/ol>\n\n\n\nSend to Telegram<\/h3>\n\n\n\n\nAdd the Telegram Node<\/strong> at the end.<\/li>\n\n\n\nCredentials:<\/strong> Click “Create New Credential” and paste the Bot Token<\/strong> you got from BotFather.<\/li>\n\n\n\nChat ID:<\/strong> You need to tell the bot where<\/em> to send the message.\n\nOpen your bot in Telegram and send it a quick message (like “Hi”).<\/li>\n\n\n\n In n8n, change the Telegram Operation<\/strong> to “getUpdates” and run it. Look for the id<\/code> under the chat<\/code> section.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\nhttps://api.telegram.org\/bot1234567890:ABCdefGHIjklMNOpqrsTUVwxyz123456789\/getUpdates<\/code><\/pre>\n\n\n\n\nCopy that number and switch the Operation back to SendMessage<\/strong>. Paste that number into the Chat ID<\/strong> field.<\/li>\n\n\n\nText:<\/strong> Click the gears next to the Text field and select Add Expression<\/strong>.\n\nIn the variable selector on the left, navigate to: Nodes > HTTP Request > Output Data > JSON > [0] > q<\/code>.<\/li>\n\n\n\nType a dash -<\/code> and then select the a<\/code> (author) variable. It should look like: {{ $json[0].q }} - {{ $json[0].a }}<\/code>.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\nTesting Your Setup<\/h3>\n\n\n\n 9. Click “Execute Node” or “Test Step”Saving Your Workflow<\/h3>\n\n\n\n 11. Give your workflow a name- Click on “My Workflow” at the top and rename it to something descriptive like “Telegram Notification Test”Practical Use Cases for Telegram and n8n Notifications<\/h2>\n\n\n\n Now that your setup works, here are powerful ways to use it:<\/p>\n\n\n\n
Workflow Completion Alerts<\/h3>\n\n\n\n Add a Telegram node as the final step in any workflow to get notified when it completes:
Troubleshooting Common Issues<\/h2>\n\n\n\n1.”Forbidden: bot was blocked by the user”<\/h3>\n\n\n\n Problem<\/strong>: You blocked your bot at some point in Telegram.<\/p>\n\n\n\nSolution<\/strong>: Search for your bot in Telegram, open the conversation, and click “Unblock” or “Restart.”<\/p>\n\n\n\n2.”Chat not found”<\/h3>\n\n\n\n Problem<\/strong>: Incorrect Chat ID or Chat ID hasn’t been initialized.<\/p>\n\n\n\nSolution<\/strong>:<\/p>\n\n\n\n\nSend a fresh message to your bot<\/li>\n\n\n\n Use the getUpdates URL again to find the correct Chat ID<\/li>\n\n\n\n Make sure you’re copying the ID from the “chat” object, not the “from” object<\/li>\n<\/ol>\n\n\n\n3.”Unauthorized”<\/h3>\n\n\n\n Problem<\/strong>: Invalid or expired API token.<\/p>\n\n\n\nSolution<\/strong>:<\/p>\n\n\n\n\nGo back to BotFather in Telegram<\/li>\n\n\n\n Type \/mybots<\/code><\/li>\n\n\n\nSelect your bot<\/li>\n\n\n\n Select “API Token”<\/li>\n\n\n\n Copy the current token and update your n8n credential<\/li>\n<\/ol>\n\n\n\n4. Messages Not Arriving<\/h3>\n\n\n\n Problem<\/strong>: Messages sent but not received in Telegram.<\/p>\n\n\n\nSolution<\/strong>:<\/p>\n\n\n\n\nCheck Telegram is running and you’re logged in<\/li>\n\n\n\n Check the bot conversation hasn’t been archived or muted<\/li>\n\n\n\n Verify you’re checking the correct Telegram account (if you have multiple)<\/li>\n\n\n\n Send a test message directly to the bot to verify the conversation is active<\/li>\n<\/ol>\n\n\n\n5. JSON Parsing Errors<\/h3>\n\n\n\n Problem<\/strong>: Error when trying to use dynamic data in messages.<\/p>\n\n\n\nSolution<\/strong>:<\/p>\n\n\n\n\nVerify the data exists in previous nodes using the “Execute Previous Nodes” option<\/li>\n\n\n\n Check your expression syntax is correct: {{$json.fieldname}}<\/code><\/li>\n\n\n\nUse the Expression Editor (click the “=” icon) for help with syntax<\/li>\n<\/ul>\n\n\n\n6. Trigger Settings<\/h3>\n\n\n\n I had the issue of timing issue.So the trigger was not happening.If your Schedule Trigger isn’t firing at the right time on your laptop, it\u2019s almost always caused by one of three things: Workflow Settings, Laptop Sleep Mode, or a Missing Publish.<\/p>\n\n\n\n
Here is the checklist to sort this out once and for all:<\/p>\n\n\n\n
1. Set the Workflow Timezone (Crucial)<\/strong> Even if you changed the “Global” n8n settings, you must verify the specific workflow\u2019s timezone.<\/p>\n\n\n\n\nOpen your workflow.<\/li>\n\n\n\n Click the Three Dots (\u22ee)<\/strong> in the top-right corner.<\/li>\n\n\n\nSelect Settings<\/strong>.<\/li>\n\n\n\nCheck the Timezone<\/strong> field. It should be Asia\/Kolkata<\/code> (for Indian Standard Time).<\/li>\n\n\n\nAction:<\/strong> If it was something else, change it, save, and then click Publish<\/strong> again to update the internal clock.<\/li>\n<\/ul>\n\n\n\n2. The “Active” Workflow Requirement<\/strong>: A schedule trigger only works if the workflow is Published\/Active<\/strong>.<\/p>\n\n\n\n\nLook at the top right of your screen. Does it say “Published”<\/strong> in a green box?<\/li>\n\n\n\nIf it says “Draft,” your schedule will never run. You must click the Publish<\/strong> button.<\/li>\n<\/ul>\n\n\n\n3. The “Laptop Sleep” Problem<\/strong> This is the most common reason for beginners.<\/p>\n\n\n\n\nThe Issue:<\/strong> When you close your laptop lid or it goes into “Sleep Mode,” your computer’s brain pauses. n8n cannot “see” the time or run nodes while the computer is sleeping.<\/li>\n\n\n\nThe Test:<\/strong> Try setting a schedule for 2 minutes from now<\/strong> and keep your laptop screen on. If it works, then you know the logic is correct, and the previous failure was likely due to the laptop being asleep at the scheduled hour.<\/li>\n<\/ul>\n\n\n\nSecurity Considerations<\/h2>\n\n\n\nProtecting Your API Token<\/h3>\n\n\n\n Your bot’s API token is sensitive. Anyone with this token can:<\/p>\n\n\n\n
![\"botfather\"](\"https:\/\/www.ucartz.com\/blog\/wp-content\/uploads\/2026\/01\/botfather--1024x597.webp\")
<\/figure>\n\n\n\n![\"telegram](\"https:\/\/www.ucartz.com\/blog\/wp-content\/uploads\/2026\/01\/telegram-api-1024x460.webp\")
<\/figure>\n\n\n\n![\"API](\"https:\/\/www.ucartz.com\/blog\/wp-content\/uploads\/2026\/01\/API-PASTED-1024x478.webp\")
<\/figure>\n\n\n\n![\"Telegram](\"https:\/\/www.ucartz.com\/blog\/wp-content\/uploads\/2026\/01\/Telegram-DASHBOARD--1024x484.webp\")
<\/figure>\n\n\n\n![\"chat](\"https:\/\/www.ucartz.com\/blog\/wp-content\/uploads\/2026\/01\/chat-id-1024x441.webp\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.ucartz.com\/blog\/wp-content\/uploads\/2026\/01\/workflow-1024x422.webp\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/www.ucartz.com\/blog\/wp-content\/uploads\/2026\/01\/telegram-settings-1024x427.webp\")
<\/figure>\n\n\n\n![\"test](\"https:\/\/www.ucartz.com\/blog\/wp-content\/uploads\/2026\/01\/test-execured-1024x432.webp\")
<\/figure>\n\n\n\n![\"telegram](\"https:\/\/www.ucartz.com\/blog\/wp-content\/uploads\/2026\/01\/tellegram-resukt-sent-mesage-1024x583.webp\")
<\/figure>\n\n\n\n![\"schedule](\"https:\/\/www.ucartz.com\/blog\/wp-content\/uploads\/2026\/01\/schedule-trigger-1024x433.webp\")
<\/figure>\n\n\n\n![\"schedule](\"https:\/\/www.ucartz.com\/blog\/wp-content\/uploads\/2026\/01\/schedule-trigger-test-1024x418.webp\")
<\/figure>\n\n\n\n![\"search](\"https:\/\/www.ucartz.com\/blog\/wp-content\/uploads\/2026\/01\/search-http--1024x423.webp\")
<\/figure>\n\n\n\n![\"http](\"https:\/\/www.ucartz.com\/blog\/wp-content\/uploads\/2026\/01\/http-request-setting-1024x425.webp\")
<\/figure>\n\n\n\n![\"http](\"https:\/\/www.ucartz.com\/blog\/wp-content\/uploads\/2026\/01\/http-request-executed-1024x420.webp\")
<\/figure>\n\n\n\n![\"FINAL](\"https:\/\/www.ucartz.com\/blog\/wp-content\/uploads\/2026\/01\/FINAL-output-1024x426.webp\")
<\/figure>\n\n\n\n![\"output\"](\"https:\/\/www.ucartz.com\/blog\/wp-content\/uploads\/2026\/01\/output-1024x600.webp\")
<\/figure>\n\n\n\n