<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Senemdemir on Medium]]></title>
        <description><![CDATA[Stories by Senemdemir on Medium]]></description>
        <link>https://medium.com/@senemdemir262?source=rss-fb7f768cf824------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*_uk8UlqyVKGz_VWJ</url>
            <title>Stories by Senemdemir on Medium</title>
            <link>https://medium.com/@senemdemir262?source=rss-fb7f768cf824------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 07:45:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@senemdemir262/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Running n8n Workflows 24/7 on AWS (Even When Your Computer Is Off)]]></title>
            <link>https://medium.com/@senemdemir262/running-n8n-workflows-24-7-on-aws-even-when-your-computer-is-off-fabf5a164048?source=rss-fb7f768cf824------2</link>
            <guid isPermaLink="false">https://medium.com/p/fabf5a164048</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Senemdemir]]></dc:creator>
            <pubDate>Sat, 21 Mar 2026 08:09:21 GMT</pubDate>
            <atom:updated>2026-03-21T08:09:21.588Z</atom:updated>
            <content:encoded><![CDATA[<p>While building automation workflows with <strong>n8n</strong>, I initially ran everything on my local machine.If you’d like to start from there, you can check it out <a href="https://medium.com/@senemdemir262/building-an-automated-daily-tech-update-telegram-bot-with-n8n-step-by-step-guide-724cf51a3225">here</a>. This worked well during development, but it had one major limitation:</p><p>If my computer was turned off, scheduled workflows would stop running. To solve this problem, I moved my n8n setup to a cloud server so that workflows could run continuously, independent of my computer.</p><p>In this guide, I will explain:</p><ul><li>What a server actually is</li><li>What sudo means in Linux</li><li>How to deploy n8n on a cloud server</li><li>How to run scheduled workflows 24/7</li></ul><p>The setup uses:</p><ul><li>Amazon Web Services</li><li>Docker</li><li>n8n</li></ul><p><strong>Understanding the Basics</strong></p><p>Before diving into the setup, it helps to understand a few fundamental concepts.</p><p><strong>What is a Server?</strong></p><p>A <strong>server</strong> is simply a computer that provides services to other computers over a network.</p><p>Unlike a personal computer, a server is typically:</p><ul><li>Always running</li><li>Accessible through the internet</li><li>Designed to handle requests from users or applications</li></ul><p>For example:</p><ul><li>A <strong>web server</strong> delivers websites.</li><li>A <strong>database server</strong> stores and manages data.</li><li>An <strong>automation server</strong> can run scheduled tasks.</li></ul><p>In our case, the server will run <strong>n8n workflows automatically</strong>, even when our personal computer is turned off. Cloud providers such as Amazon Web Services allow us to create virtual servers within minutes. These virtual machines are called <strong>instances</strong>.</p><p><strong>What Does </strong>sudo<strong> Mean?</strong></p><p>When working with Linux servers, you will often see commands starting with:</p><pre>sudo</pre><p>sudo stands for:</p><pre>superuser do</pre><p>It allows a normal user to execute commands with <strong>administrator privileges</strong>.</p><p>For example:</p><pre>sudo apt install docker.io</pre><p>This command installs Docker on the system. Because installing software affects the whole system, administrative permissions are required. Without sudo, many system-level commands would fail due to insufficient permissions.</p><p><strong>Why Run n8n on a Server?</strong></p><p>Running n8n locally works for development, but it has a major limitation:</p><pre>Workflows stop when your computer turns off.</pre><p>By deploying n8n on a cloud server:</p><ul><li>workflows run continuously</li><li>schedules trigger automatically</li><li>the system becomes independent from your local machine</li></ul><p>This is especially useful for automation workflows such as:</p><ul><li>RSS monitoring</li><li>scheduled notifications</li><li>background jobs</li><li>data synchronization</li></ul><p><strong>Step 1 — Creating a Cloud Server</strong></p><p>First, we create a virtual server using Amazon Web Services. The service used for virtual machines is <strong>EC2 (Elastic Compute Cloud)</strong>. We launched a new instance with the following configuration.</p><p>Operating system:</p><pre>Ubuntu Server 24.04</pre><p>Instance type:</p><pre>t3.micro</pre><p>This configuration includes:</p><ul><li>1 CPU</li><li>1GB RAM</li></ul><p>It is sufficient for running n8n workflows.</p><p><strong>Step 2 — Configuring Network Access</strong></p><p>Servers are protected by firewall rules. On AWS, these rules are defined in <strong>Security Groups</strong>.</p><p>We allowed inbound traffic for the following ports:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VSYhEFzCc6dKKAJZxxm2fw.png" /></figure><p>The most important rule was opening port <strong>5678</strong>, which is the default port used by n8n.</p><pre>Type: Custom TCP<br>Port: 5678<br>Source: 0.0.0.0/0</pre><p>This allows the n8n interface to be accessed from the internet.</p><p><strong>Step 3 — Connecting to the Server</strong></p><p>After launching the server, we connect to it using <strong>SSH</strong>. SSH allows secure remote access to the server through a terminal.</p><p>Example command:</p><pre>ssh -i aws-server-key.pem ubuntu@SERVER_IP</pre><p>Once connected, we can execute commands directly on the server.</p><p><strong>Step 4 — Installing Docker</strong></p><p>Instead of installing n8n directly on the system, we run it inside a <strong>Docker container</strong>. Docker is a platform that allows applications to run in isolated environments.</p><p>Advantages of Docker:</p><ul><li>easy deployment</li><li>consistent environment</li><li>simple updates</li><li>better isolation</li></ul><p>Installation:</p><pre>sudo apt update<br>sudo apt install docker.io -y</pre><p>Start the Docker service:</p><pre>sudo systemctl start docker<br>sudo systemctl enable docker</pre><p><strong>Step 5 — Running n8n with Docker</strong></p><p>Next, we launch n8n as a container.</p><pre>sudo docker run -d \<br>--name n8n \<br>--restart unless-stopped \<br>-p 5678:5678 \<br>-e N8N_SECURE_COOKIE=false \<br>-e NODE_OPTIONS=&quot;--max-old-space-size=512&quot; \<br>-v ~/.n8n:/home/node/.n8n \<br>n8nio/n8n</pre><p>This command performs several tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hZkaYPO0SA6pCBAFxe5XaQ.png" /></figure><p><strong>Step 6 — Accessing the n8n Interface</strong></p><p>Once the container is running, the editor becomes accessible via:</p><pre>http://SERVER_IP:5678</pre><p>On first launch, n8n asks you to create an <strong>owner account</strong>. This account will be used to manage workflows and credentials.</p><p><strong>Step 7 — Migrating Workflows from Local to Server</strong></p><p>Workflows created locally can easily be transferred. The simplest approach is exporting them as JSON.</p><p>Steps:</p><ul><li>Export workflow from local n8n</li><li>Download JSON file</li><li>Import the file into the server instance</li><li>Reconnect credentials</li><li>Activate the workflow</li></ul><p><strong>Step 8 — Running Scheduled Workflows</strong></p><p>n8n provides a <strong>Schedule Trigger</strong> node.</p><p>Example schedule:</p><pre>Every day at 11:00</pre><p>Or using cron syntax:</p><pre>0 11 * * *</pre><p>Once the workflow is <strong>activated</strong>, n8n automatically triggers it at the defined time.</p><p>After completing the setup, the system works like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/412/1*fFlqCgzoQYwuVZISbMyt6w.png" /></figure><p>Because the automation runs on the server, workflows continue executing even when the local computer is turned off.</p><h4>Conclusion</h4><p>By deploying n8n on a cloud server, we achieved:</p><ul><li>continuous automation</li><li>reliable scheduled workflows</li><li>independence from local machines</li><li>persistent workflow storage</li></ul><p>Running n8n on a server turns simple automation experiments into a <strong>reliable production system</strong>.</p><p>Your n8n setup is now fully automated and running in the cloud. From this point on, your workflows will continue to execute on schedule — even when your computer is turned off.</p><p>This marks the transition from a development setup to a production-ready automation system.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fabf5a164048" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building an Automated Daily Tech Update Telegram Bot with n8n (Step-by-Step Guide)]]></title>
            <link>https://medium.com/@senemdemir262/building-an-automated-daily-tech-update-telegram-bot-with-n8n-step-by-step-guide-724cf51a3225?source=rss-fb7f768cf824------2</link>
            <guid isPermaLink="false">https://medium.com/p/724cf51a3225</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[n8n]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[rss]]></category>
            <category><![CDATA[telegram-bot]]></category>
            <dc:creator><![CDATA[Senemdemir]]></dc:creator>
            <pubDate>Tue, 03 Mar 2026 10:52:03 GMT</pubDate>
            <atom:updated>2026-03-05T22:39:10.697Z</atom:updated>
            <content:encoded><![CDATA[<h3>Building a Daily Tech Update Telegram Bot with n8n</h3><p>In this article, I’ll walk through how I built a Telegram bot using <strong>n8n</strong> that scans selected RSS sources daily and sends updates automatically.</p><p>The goal is simple:</p><p>Every day, at a specific time, fetch updates from sources like React, Next.js, OpenAI, Angular, etc., and send them to a Telegram channel automatically.</p><h4>What is n8n?</h4><p>n8n is an open-source workflow automation tool that allows you to connect different services and automate repetitive tasks.</p><p>It works similarly to tools like Zapier or Make, but with much more flexibility and the ability to run it on your own infrastructure.</p><p>Using a visual workflow interface, you can connect APIs, process data and trigger actions across multiple services without writing a full backend application.</p><p>In this project, n8n acts as the automation engine that:</p><ul><li>collects updates from multiple RSS feeds</li><li>processes the data</li><li>formats the message</li><li>sends the result to a Telegram channel</li></ul><p>Before jumping into the implementation details, let’s first take a look at the overall architecture of the system. The following diagram shows how the automation pipeline works.</p><h4>Automation Workflow</h4><p>The system is designed as a simple automation pipeline. It periodically checks multiple technology news sources, processes the incoming data and publishes a formatted summary to a Telegram channel.</p><p>The workflow looks like this:</p><figure><img alt="Overview of the automation pipeline used in this project" src="https://cdn-images-1.medium.com/max/367/1*Lb9tZ8Uhbyt9DQ0FDy3TNA.jpeg" /></figure><p>Now that we understand the overall architecture, let’s go step by step and build the workflow inside n8n.</p><h4>Step-by-Step Implementation</h4><p><strong>1)Running n8n Locally<br></strong>If you have Node.js installed, you can start n8n with:</p><pre>npx n8n</pre><p>After running the command, press “o” to open it in your browser at:<br>http://localhost:5678<br>You’ll see the initial setup screen.</p><p><strong>2)First-Time Setup</strong></p><p>You’ll need to create a user account.This account is only for your local n8n instance — it does not register you to any external service.You’ll also see a short onboarding questionnaire. The following options are fine:</p><ul><li><strong>Company:</strong> Personal Use</li><li><strong>Role</strong>: Engineering</li><li><strong>What are you automating:</strong> IT operations or Other</li><li><strong>Main usage:</strong> Myself</li><li><strong>Company size:</strong> Just me</li><li><strong>How did you hear about n8n:</strong> Doesn’t matter</li></ul><p>After that, you’ll reach the dashboard.</p><p><strong>3)Creating Your First Workflow</strong></p><p>On the dashboard:</p><ul><li>Click <strong>Create First Workflow</strong></li><li>Give it a name</li><li>Save it</li></ul><p>Now we’re ready to build the automation flow.</p><p><strong>4)Adding Telegram Node</strong></p><p>Click the “+” button and search for <strong>Telegram</strong>.Choose <strong>Send a Message</strong>.</p><p><strong>5)Getting a Telegram Bot Token (BotFather)</strong></p><p>To create credentials, you’ll need an <strong>Access Token</strong>. Steps:</p><ul><li>Open Telegram</li><li>Search for <a href="https://medium.com/u/fff1d3dcc826">Botfather</a></li><li>Type /newbot</li><li>Enter a bot name and username(The username must end with _bot)</li></ul><p>BotFather will generate a token. Keep it secure and do not share it.</p><p><strong>6)Getting the Chat ID</strong></p><ul><li>Find your bot in Telegram.</li><li>Start a conversation.</li><li>Send a message like “Hello”</li></ul><p>Then open this in your browser:</p><pre>https://api.telegram.org/botYOURTOKEN/getUpdates</pre><p>Replace YOURTOKEN with your actual token (make sure it includes the word bot).From the returned JSON, find:</p><p>chat → id<br>If you see result: []:</p><ul><li>Send /start to your bot</li><li>Send another message</li><li>Refresh the page</li></ul><p><strong>7)Testing the Connection</strong></p><p>In the Telegram node:</p><ul><li>Enter your Chat ID</li><li>In Text field, write: <strong>“n8n test is successful”</strong></li><li>Click <strong>Execute Step<br></strong>If you receive the message in Telegram, everything works correctly.</li></ul><p><strong>8)Adding a Schedule Trigger</strong></p><p>We want this to run daily. Add a <strong>Schedule Trigger</strong>:</p><ul><li>Mode: Every Day</li><li>Time: The hour you want to receive updates<br>This node will trigger the workflow automatically every day.</li></ul><p><strong>9)Using RSS Read</strong></p><p>After the Schedule Trigger:</p><ul><li>Click “+”</li><li>Add <strong>RSS Read</strong></li><li>Enter your RSS URL</li><li>Execute Step to test<br>You can add multiple RSS nodes for different sources.</li></ul><p><strong>10)Handling “Request Entity Too Large” Error</strong></p><p>Some RSS feeds contain too many items. To prevent this error:</p><pre>Request entity too large</pre><p>Open each RSS node and set a <strong>Limit</strong> value.</p><p><strong>11)Merging Multiple Feeds</strong></p><p>To combine multiple RSS outputs:</p><ul><li>Add a <strong>Merge</strong> node</li><li>Mode: Append</li></ul><p>Important:</p><ul><li>Each Merge node only accepts 2 inputs.</li><li>If you have many feeds, you need chained merge nodes.</li></ul><h4>Formatting the Telegram Message (Code Node)</h4><p>After the final <strong>Merge</strong> node, add a <strong>Code</strong> node to format the Telegram message. If you are using <strong>RSS Read nodes</strong>, this step is required to structure the data before sending it to Telegram.</p><pre>const items = $input.all();<br><br>function clean(s) {<br> return String(s || &quot;&quot;).replace(/\s+/g, &quot; &quot;).trim();<br>}</pre><p>You can find the full code in <a href="https://gist.github.com/senemdemirr/d2cae4a066a5e3dfbd608b78c7c98f01"><strong>this Gist.</strong></a></p><h4>A More Stable Approach: HTTP Request + XML + Set</h4><p>As the number of feeds increases, RSS Read may cause:</p><ul><li>Request timed out after 60000ms</li><li>Request entity too large</li></ul><p>Instead of RSS Read, using <strong>HTTP Request + XML + Set</strong> provides more control and better stability.</p><p><strong>12)HTTP Request Configuration</strong></p><p>For each HTTP Request node, add the following headers:</p><pre>User-Agent: Mozilla/5.0 (compatible; n8n; +https://n8n.io/)<br>Accept: application/rss+xml, application/atom+xml, application/xml, text/xml;q=0.9, */*;q=0.8<br>Accept-Encoding: identity</pre><p>Why?</p><ul><li><strong>User-Agent</strong> → Prevent bot traffic from being blocked</li><li><strong>Accept</strong> → Explicitly request RSS/XML format</li><li><strong>Accept-Encoding</strong> → Receive raw XML instead of compressed data</li></ul><p><strong>13)Timeout &amp; Retry Settings</strong></p><ul><li>Timeout: <strong>180000 ms (3 minutes)</strong></li><li>Retry on Fail: Enabled</li><li>Wait Between Tries: <strong>2000 ms</strong></li></ul><p>The default 60 seconds is sometimes not enough for large feeds. These settings make the workflow more resilient against:</p><ul><li>Temporary network issues</li><li>Rate limiting</li><li>Slow servers</li></ul><p><strong>14)Parsing XML</strong></p><p>HTTP Request returns raw XML. Add an <strong>XML node</strong> to convert it into JSON.Benefits:</p><ul><li>Easier access to title and link</li><li>Cleaner structure</li><li>No need to manually parse XML inside Code node</li></ul><p><strong>15)Normalizing with Set Node</strong></p><p>Different RSS feeds use different field names.Using a <strong>Set node</strong>:</p><ul><li>Remove unnecessary fields</li><li>Keep only title and link</li><li>Reduce payload size</li><li>Simplify the merged data</li></ul><p>This structure is much more production-ready compared to plain RSS Read usage.</p><h4>Formatting the Telegram Message (Code Node)</h4><p>After the final <strong>Merge</strong> node, add a <strong>Code</strong> node to format the Telegram message. If you are using HTTP Request nodes, this step is required to structure the data before sending it to Telegram.</p><pre>const items = $input.all();<br><br>const nowMs = Date.now();<br>const windowStartMs = nowMs - 36 * 60 * 60 * 1000;<br>const MAX_PER_SUB = 5;</pre><p>You can find the full code in <a href="https://gist.github.com/senemdemirr/c00387bf3558aa8f7dcbfa56eccbd99e"><strong>this Gist.</strong></a></p><p><strong>16)Sending Dynamic Message to Telegram</strong></p><p>After the Code node:</p><ul><li>Add <strong>Telegram → Send Message</strong></li><li>Chat ID → your Chat ID</li><li>Switch Text field to <strong>Expression mode</strong></li></ul><pre>{{$json.text}}</pre><p><strong>17)Publishing the Workflow</strong></p><ul><li>Click <strong>Execute Workflow</strong> to test</li><li>If the message arrives, everything works</li><li>Click <strong>Publish</strong> to activate automatic execution</li></ul><h4>Final Thoughts</h4><p>For small setups, RSS Read works fine.</p><p>But as the number of feeds grows, the <strong>HTTP Request + XML + Set</strong> structure becomes:</p><ul><li>More stable</li><li>More controlled</li><li>More production-friendly</li></ul><p>With this setup:</p><ul><li>Timeout issues decrease</li><li>Rate-limit situations are handled better</li><li>Data is normalized</li><li>Message formatting is fully controlled</li></ul><p>And now you have your own automated Daily Tech Update bot 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=724cf51a3225" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>