<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Lan Exequiel Mislang</title>
    <description>The latest articles on DEV Community by Lan Exequiel Mislang (@lanexbuilds).</description>
    <link>https://dev.to/lanexbuilds</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4208148%2Fb009109f-5339-4aa2-b81b-e1750abc0051.jpg</url>
      <title>DEV Community: Lan Exequiel Mislang</title>
      <link>https://dev.to/lanexbuilds</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/lanexbuilds"/>
    <language>en</language>
    <item>
      <title>Testing Debugging Content Scrape Notify n8n</title>
      <dc:creator>Lan Exequiel Mislang</dc:creator>
      <pubDate>Sat, 31 Oct 2026 15:01:36 +0000</pubDate>
      <link>https://dev.to/lanexbuilds/testing-debugging-content-scrape-notify-n8n-307o</link>
      <guid>https://dev.to/lanexbuilds/testing-debugging-content-scrape-notify-n8n-307o</guid>
      <description>&lt;p&gt;I spend an hour each morning opening three design blogs to see if there are fresh layouts or font updates. The hours add up quickly. The Content Scrape &amp;amp; Notify workflow replaces that manual check with a scheduled scan. It fires at set intervals, pulls the page, pulls out the new items, and pings me only when something actually changes.&lt;/p&gt;

&lt;h2&gt;
  
  
  At a glance
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Built for:&lt;/strong&gt; content creators&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Difficulty:&lt;/strong&gt; beginner&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Starts with:&lt;/strong&gt; Cron Schedule Trigger (scheduleTrigger)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Steps:&lt;/strong&gt; 5 nodes&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tools:&lt;/strong&gt; n8n, HTTP Request, Slack&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The Cron Schedule Trigger
&lt;/h2&gt;

&lt;p&gt;The workflow starts with a Cron Schedule Trigger. This node fires at the interval you set—every hour, every day, or on a custom cron expression. I have mine set to every six hours so the page isn’t hammered, but the check happens often enough to catch new posts before the day is out. The trigger passes no data to the next node; it simply starts the run.&lt;/p&gt;

&lt;h2&gt;
  
  
  The HTTP Request - Scrape Page
&lt;/h2&gt;

&lt;p&gt;After the trigger, an HTTP Request node scrapes the target webpage. I point it at a design blog’s front page and leave the method as GET. The node returns the raw HTML. I use a simple XPath expression in the node’s response format to pull out the article links and titles. If the page structure changes—say the site switches from &lt;code&gt;&amp;lt;h2&amp;gt;&lt;/code&gt; to &lt;code&gt;&amp;lt;h3&amp;gt;&lt;/code&gt; for headings—the scrape will return empty or broken data, and the workflow will stop at that node.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Set - Extract Items
&lt;/h2&gt;

&lt;p&gt;The Set node takes the raw scrape and extracts the relevant items. I map the XPath results into a structured object with fields like &lt;code&gt;title&lt;/code&gt;, &lt;code&gt;url&lt;/code&gt;, and &lt;code&gt;published&lt;/code&gt;. This step normalizes the data so the next IF node can compare apples to apples. Without this mapping, the duplicate check would see raw HTML strings and never match anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  The IF - Check For Duplicates
&lt;/h2&gt;

&lt;p&gt;An IF node runs a simple expression to compare the extracted &lt;code&gt;url&lt;/code&gt; against a list of URLs already seen. I store the seen URLs in n8n’s built‑in &lt;code&gt;Items&lt;/code&gt; cache between runs, or I use a tiny JavaScript function to push new URLs into a persistent key-value store. If the URL is already in the list, the IF evaluates to false and the workflow ends quietly. If the URL is new, the path continues to the Slack node.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Slack - Notify New Content
&lt;/h2&gt;

&lt;p&gt;When fresh content is found, a Slack node sends a message to a channel. The message includes the title as a clickable link and a one‑sentence summary pulled from the extracted data. If the scrape returns nothing—perhaps the site is down or the XPath is wrong—the workflow simply ends without notifying anyone, which is the desired behavior.&lt;/p&gt;

&lt;h3&gt;
  
  
  Worked Example
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Sample data&lt;/strong&gt;: A fictional article titled "New Grid System Released" with URL &lt;code&gt;https://example.design/news/grid-2024&lt;/code&gt;.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Cron Schedule Trigger&lt;/strong&gt; fires at 08:00.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;HTTP Request - Scrape Page&lt;/strong&gt; returns HTML; the XPath extracts &lt;code&gt;[{title: "New Grid System Released", url: "https://example.design/news/grid-2024"}]&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Set - Extract Items&lt;/strong&gt; structures the result into &lt;code&gt;{title: "New Grid System Released", url: "https://example.design/news/grid-2024"}&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;IF - Check For Duplicates&lt;/strong&gt; compares the URL against the cached list. The URL is not present, so the path proceeds.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Slack - Notify New Content&lt;/strong&gt; posts: &lt;em&gt;New Grid System Released&lt;/em&gt; – &lt;a href="https://example.design/news/grid-2024" rel="noopener noreferrer"&gt;https://example.design/news/grid-2024&lt;/a&gt;. The user sees the message and can click through immediately.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If the same URL had appeared in a previous run, the IF would have blocked the Slack step, and no notification would fire.&lt;/p&gt;

&lt;h2&gt;
  
  
  Likely Failure Points
&lt;/h2&gt;

&lt;p&gt;The most common failure is a mismatched XPath. If the target site updates its markup—moving from &lt;code&gt;&amp;lt;article&amp;gt;&lt;/code&gt; tags to &lt;code&gt;&amp;lt;div class="post"&amp;gt;&lt;/code&gt;—the scrape returns an empty array, the Set node produces no items, and the workflow ends silently. Another frequent issue is the duplicate‑check cache. If the cache is cleared or the expression references the wrong field, every run will treat every item as new, flooding the Slack channel with repeats.&lt;/p&gt;

&lt;h3&gt;
  
  
  Debugging Checklist
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Verify the XPath returns at least one element in the HTTP Request node’s output preview.&lt;/li&gt;
&lt;li&gt;Confirm the Set node’s mapping produces the expected &lt;code&gt;url&lt;/code&gt; field.&lt;/li&gt;
&lt;li&gt;Check the IF node’s expression: &lt;code&gt;items.length &amp;gt; 0 &amp;amp;&amp;amp; items[0].url&lt;/code&gt; works only if the field name matches.&lt;/li&gt;
&lt;li&gt;Look at the execution logs: a red error at the HTTP Request node usually means a 404 or a changed site structure; a green pass at the IF node with &lt;code&gt;false&lt;/code&gt; means the item was already seen.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Key takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The Cron Schedule Trigger runs the workflow on a fixed timetable, not on demand.&lt;/li&gt;
&lt;li&gt;The HTTP Request node pulls raw HTML; any change to the page markup breaks the scrape.&lt;/li&gt;
&lt;li&gt;The IF node’s duplicate check depends on a stable URL field and a persistent cache.
}&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Before you import it
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A running n8n instance (cloud or self-hosted).&lt;/li&gt;
&lt;li&gt;n8n account&lt;/li&gt;
&lt;li&gt;website URL to scrape&lt;/li&gt;
&lt;li&gt;Slack workspace and token&lt;/li&gt;
&lt;li&gt;Sample data to test with, before pointing it at real records.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Get the free workflow
&lt;/h2&gt;

&lt;p&gt;The importable JSON for &lt;strong&gt;Content Scrape &amp;amp; Notify&lt;/strong&gt; is free to download: &lt;a href="https://lanexbuilds.com/entry?id=content-scrape-notify" rel="noopener noreferrer"&gt;https://lanexbuilds.com/entry?id=content-scrape-notify&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This workflow was generated with AI assistance. Test it with sample data before using it on real data.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Cover photo by &lt;a href="https://pixabay.com/photos/laptop-mockup-graphics-tablet-2838921/" rel="noopener noreferrer"&gt;lukasbieri&lt;/a&gt; on &lt;a href="https://pixabay.com" rel="noopener noreferrer"&gt;Pixabay&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>n8n</category>
      <category>workflow</category>
      <category>debugging</category>
      <category>scrape</category>
    </item>
    <item>
      <title>Intent Classification and API Actions in a Recruitment Chat Flow</title>
      <dc:creator>Lan Exequiel Mislang</dc:creator>
      <pubDate>Fri, 30 Oct 2026 15:03:03 +0000</pubDate>
      <link>https://dev.to/lanexbuilds/intent-classification-and-api-actions-in-a-recruitment-chat-flow-2hk8</link>
      <guid>https://dev.to/lanexbuilds/intent-classification-and-api-actions-in-a-recruitment-chat-flow-2hk8</guid>
      <description>&lt;h2&gt;
  
  
  Detecting Candidate Intent with the If Node
&lt;/h2&gt;

&lt;p&gt;The workflow begins when a chat webhook receives a new message from a candidate. The Detect Intent node uses an if condition to evaluate the incoming text. A common approach is to inspect specific keywords or phrases that indicate the applicant's goal. For example, if the message contains the word "resume" or "CV", the condition routes to the resume‑handling branch. If the message mentions "schedule" or "interview", it follows a different path. This branching happens immediately after the webhook trigger, ensuring that every incoming chat is classified before any further processing occurs.&lt;/p&gt;

&lt;h2&gt;
  
  
  At a glance
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Built for:&lt;/strong&gt; recruiters&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Difficulty:&lt;/strong&gt; beginner&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Starts with:&lt;/strong&gt; Chat Webhook Trigger (webhook)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Steps:&lt;/strong&gt; 5 nodes&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tools:&lt;/strong&gt; n8n, HTTP request service, Chat platform API&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;When the if condition evaluates to true for a particular intent, the workflow proceeds to the next node. If none of the defined patterns match, the false branch can direct the message to a fallback response or a human reviewer. The if node does not alter the message content; it only decides which subsequent node will execute. This design keeps the logic explicit and makes it easy to add new intent patterns without restructuring the entire flow.&lt;/p&gt;

&lt;h2&gt;
  
  
  Routing to the Correct API Based on Intent
&lt;/h2&gt;

&lt;p&gt;Once the intent is identified, the Route to API node is called to perform the required action. This HTTP request node sends a POST or GET call to an external service, depending on what the recruiter needs. For a resume‑related intent, the request might target a candidate‑profile API to store or update a CV. For a scheduling intent, the request could hit a calendar‑integration endpoint to propose available time slots.&lt;/p&gt;

&lt;p&gt;The HTTP Request node is configured with the appropriate endpoint URL, headers, and body. Often the body includes dynamic values extracted from the original chat message, such as the candidate’s name or email address. The response from the API is then passed forward to the next node. If the external service returns an error, the workflow can follow a separate path to log the failure or notify the recruiter. This step ensures that the correct system of record is updated for each type of candidate interaction.&lt;/p&gt;

&lt;h2&gt;
  
  
  Formatting the Response for the Chat Platform
&lt;/h2&gt;

&lt;p&gt;After the API call completes, the Format Response node prepares a structured payload that the chat platform can display. The Set node constructs a JSON object with fields such as "type", "content", and any quick‑reply buttons the recruiter wants to offer. For instance, if the API returned a list of open positions, the Set node might format that list into a concise markdown string.&lt;/p&gt;

&lt;p&gt;The formatting step also handles conditional text. If the API returned no results, the node can insert a polite message like "No matching profiles found at this time." The node’s output is a plain object that the final Respond to Webhook step will consume. Keeping the response format consistent across all intents makes the chatbot behavior predictable for both the recruiter and the applicant.&lt;/p&gt;

&lt;h2&gt;
  
  
  Replying to the Chat Channel
&lt;/h2&gt;

&lt;p&gt;The final step in the core workflow is Reply to Chat, which sends the formatted payload back to the original chat platform. The Respond to Webhook node takes the output from the Set node and transmits it as a message in the same conversation thread. This closes the loop: the candidate receives a relevant reply without any manual intervention from the recruiter.&lt;/p&gt;

&lt;p&gt;If the workflow encounters an unexpected situation—such as the API being unreachable— the Respond to Webhook node can output a default message like "We’re having trouble processing your request right now. Please try again later." This ensures that every incoming message gets a response, even when things go wrong.&lt;/p&gt;

&lt;h2&gt;
  
  
  Extending the Workflow
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Add a CRM branch&lt;/strong&gt; – Insert an additional if condition after the intent check to detect when a candidate expresses interest in a specific role. Route that branch to an HTTP Request node that updates a CRM record with the candidate’s ID and preferred job title. The Set node then appends a tag to the chat response, such as "Noted interest in Senior Engineer role."&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Move API logic into a sub‑workflow&lt;/strong&gt; – If the routing logic becomes complex, extract the Route to API and Format Response steps into a separate sub‑workflow. The main flow calls the sub‑workflow via the Execute Workflow node, passing the intent type as a parameter. This keeps the primary diagram clean and allows the API‑specific steps to be version‑controlled independently.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Swap the messaging service&lt;/strong&gt; – Replace the Respond to Webhook node with a different chat integration, such as a Slack or Microsoft Teams node. Configure the new node with the same structured payload, ensuring the channel ID and formatting match the target platform. The rest of the workflow remains unchanged, only the delivery endpoint shifts.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Key takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The if node classifies every incoming message before any action is taken.&lt;/li&gt;
&lt;li&gt;The HTTP request node updates the correct system of record based on the detected intent.&lt;/li&gt;
&lt;li&gt;The Set and Respond to Webhook nodes ensure a consistent reply is sent back to the candidate.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Before you import it
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A running n8n instance (cloud or self-hosted).&lt;/li&gt;
&lt;li&gt;n8n account&lt;/li&gt;
&lt;li&gt;Chat platform credentials&lt;/li&gt;
&lt;li&gt;API endpoint access&lt;/li&gt;
&lt;li&gt;Sample data to test with, before pointing it at real records.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Get the free workflow
&lt;/h2&gt;

&lt;p&gt;The importable JSON for &lt;strong&gt;Recruitment Intent Router&lt;/strong&gt; is free to download: &lt;a href="https://lanexbuilds.com/entry?id=recruitment-intent-router" rel="noopener noreferrer"&gt;https://lanexbuilds.com/entry?id=recruitment-intent-router&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This workflow was generated with AI assistance. Test it with sample data before using it on real data.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Cover photo by &lt;a href="https://pixabay.com/photos/bunny-business-businessmen-career-3830669/" rel="noopener noreferrer"&gt;kirill_makes_pics&lt;/a&gt; on &lt;a href="https://pixabay.com" rel="noopener noreferrer"&gt;Pixabay&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>automation</category>
      <category>beginners</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Error Handling and Edge Cases in the Restaurant Booking n8n Workflow</title>
      <dc:creator>Lan Exequiel Mislang</dc:creator>
      <pubDate>Thu, 29 Oct 2026 15:03:50 +0000</pubDate>
      <link>https://dev.to/lanexbuilds/error-handling-and-edge-cases-in-the-restaurant-booking-n8n-workflow-3bf9</link>
      <guid>https://dev.to/lanexbuilds/error-handling-and-edge-cases-in-the-restaurant-booking-n8n-workflow-3bf9</guid>
      <description>&lt;p&gt;The lunch rush ends and the kitchen wind-down begins. The host checks the day's reservations. One slot shows a name with no phone number, another has a time that has already passed. These moments happen when data moves between forms and spreadsheets. This workflow automates the path from a web form to a Google Sheet and a confirmation email, but each node introduces failure modes that must be understood to keep bookings reliable.&lt;/p&gt;

&lt;h2&gt;
  
  
  At a glance
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Built for:&lt;/strong&gt; restaurants and cafes&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Difficulty:&lt;/strong&gt; beginner&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Starts with:&lt;/strong&gt; Form Trigger (formTrigger)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Steps:&lt;/strong&gt; 5 nodes&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tools:&lt;/strong&gt; n8n, Google Sheets, Gmail&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Form Trigger – formTrigger
&lt;/h2&gt;

&lt;p&gt;The workflow starts when a visitor submits the online booking form. If the form is submitted without a name or email, the trigger passes empty values downstream. A missing required field can cause the Google Sheets node to write a row of nulls, or the Gmail node to address a blank recipient. The Set node cannot fix absent data; it can only re‑map what it receives. Retries on the form submit side are the only way to guarantee complete records.&lt;/p&gt;

&lt;h2&gt;
  
  
  Set – Preprocess Form
&lt;/h2&gt;

&lt;p&gt;set&lt;br&gt;
After the trigger, the Set node maps form fields to Google Sheet columns. If the form uses different labels than the sheet expects, the node will map fields to empty columns. For example, a form field called "party size" left unmapped will not populate the "guests" column. The node also runs on every execution; if a user resubmits quickly, a second row appears in the sheet unless duplicate checks are added outside n8n. Timeouts here are rare but can occur if the form payload is large, causing the node to pause while it waits for the data structure to resolve.&lt;/p&gt;

&lt;h2&gt;
  
  
  Google Sheets – Insert Booking
&lt;/h2&gt;

&lt;p&gt;googleSheets&lt;br&gt;
This node writes the booking row into a spreadsheet. Network glitches or exceeding the sheet's row limit can cause the operation to fail. When the write fails, the booking is lost unless an error trigger catches the exit path. Duplicate entries are a risk if the form is submitted twice; the sheet does not inherently de‑duplicate, so manual review or a unique identifier in the form is needed. The node does not retry automatically—any retry must be handled by the workflow's error branch.&lt;/p&gt;

&lt;h2&gt;
  
  
  Email – Send Confirmation
&lt;/h2&gt;

&lt;p&gt;gmail&lt;br&gt;
Once the sheet row is created, the Gmail node sends a confirmation to the customer. If the email address from the form is malformed, the send fails and the workflow stops at that node. Rate limits from the Gmail API can also throttle consecutive sends, especially during a busy service period. The node does not hold the email for later retry; it logs the failure and moves on. A common edge case is sending to an address that accepts mail but triggers a spam filter, resulting in the customer never seeing the notice.&lt;/p&gt;

&lt;h3&gt;
  
  
  Worked Example
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Booking record (fictional)&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Name: Luna Patel&lt;/li&gt;
&lt;li&gt;Email: &lt;a href="mailto:luna.patel@mail.example"&gt;luna.patel@mail.example&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Date: 2026‑02‑14&lt;/li&gt;
&lt;li&gt;Time: 19:00&lt;/li&gt;
&lt;li&gt;Party size: 4&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Step‑by‑step trace&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;formTrigger&lt;/strong&gt;: The form submits the JSON payload `{&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Key takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Form submissions missing required fields pass empty values downstream, potentially causing null entries in Google Sheets or blank email recipients, requiring form-side retries to guarantee complete data.&lt;/li&gt;
&lt;li&gt;The Set node maps form fields to sheet columns; mismatched labels or quick resubmissions can result in empty columns or duplicate rows unless external duplicate checks are implemented.&lt;/li&gt;
&lt;li&gt;Google Sheets writes booking data but fails silently on network errors or row limits without automatic retries, and Gmail confirmation sends fail on malformed addresses or API rate limits, logging errors and moving on without retrying.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Before you import it
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A running n8n instance (cloud or self-hosted).&lt;/li&gt;
&lt;li&gt;n8n account&lt;/li&gt;
&lt;li&gt;Google Sheets service account with write access&lt;/li&gt;
&lt;li&gt;Gmail credentials for sending emails&lt;/li&gt;
&lt;li&gt;Sample data to test with, before pointing it at real records.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Get the free workflow
&lt;/h2&gt;

&lt;p&gt;The importable JSON for &lt;strong&gt;Restaurant Booking Form&lt;/strong&gt; is free to download: &lt;a href="https://lanexbuilds.com/entry?id=restaurant-booking-form" rel="noopener noreferrer"&gt;https://lanexbuilds.com/entry?id=restaurant-booking-form&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This workflow was generated with AI assistance. Test it with sample data before using it on real data.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Cover photo by &lt;a href="https://pixabay.com/photos/woman-laptop-desk-workspace-1851464/" rel="noopener noreferrer"&gt;Pexels&lt;/a&gt; on &lt;a href="https://pixabay.com" rel="noopener noreferrer"&gt;Pixabay&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>automation</category>
      <category>beginners</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Morning Course Digest for Coaches Node Logic Deep Dive</title>
      <dc:creator>Lan Exequiel Mislang</dc:creator>
      <pubDate>Wed, 28 Oct 2026 15:02:08 +0000</pubDate>
      <link>https://dev.to/lanexbuilds/morning-course-digest-for-coaches-node-logic-deep-dive-2f0d</link>
      <guid>https://dev.to/lanexbuilds/morning-course-digest-for-coaches-node-logic-deep-dive-2f0d</guid>
      <description>&lt;p&gt;At 6:15 am a coach opens their laptop to review yesterday’s student messages. Before coffee is finished, a Slack notification pings: "New course digest ready." The workflow has already gathered the latest articles from three RSS feeds, extracted the key takeaways, and posted a formatted summary to the #coaching‑updates channel. This is what the Morning Course Digest for Coaches workflow does each morning.&lt;/p&gt;

&lt;h2&gt;
  
  
  At a glance
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Built for:&lt;/strong&gt; coaches and course creators&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Difficulty:&lt;/strong&gt; beginner&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Starts with:&lt;/strong&gt; Schedule Trigger (scheduleTrigger)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Steps:&lt;/strong&gt; 5 nodes&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tools:&lt;/strong&gt; n8n, Slack, RSS Feed&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Schedule Trigger – scheduleTrigger
&lt;/h2&gt;

&lt;p&gt;The workflow begins with the &lt;strong&gt;scheduleTrigger&lt;/strong&gt; node. It is configured to run at 06:00 local time every weekday. When the trigger fires, it passes an empty execution context to the next node. No input data is required; the trigger simply starts the cycle at the set interval.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fetch RSS Feed – httpRequest
&lt;/h2&gt;

&lt;p&gt;The &lt;strong&gt;httpRequest&lt;/strong&gt; node receives the empty context from the schedule trigger and issues GET requests to the three selected RSS feed URLs. Each response contains an XML payload with items, each item having a title, link, and description. The node outputs an array of RSS items; each item includes the raw XML fields plus any metadata the node adds, such as the fetch timestamp. A typical output item looks like { "title": "Advanced Python Techniques", "link": "&lt;a href="https://example.com/python-tips" rel="noopener noreferrer"&gt;https://example.com/python-tips&lt;/a&gt;", "description": "Learn decorators and context managers." }.&lt;/p&gt;

&lt;h2&gt;
  
  
  Split RSS Items – splitInBatches
&lt;/h2&gt;

&lt;p&gt;The &lt;strong&gt;splitInBatches&lt;/strong&gt; node receives the array of RSS items from the httpRequest node. It separates the items into individual batches so that each item can be processed independently in the code node. The node does not alter the item structure; it simply outputs one execution per RSS item, passing the full item object down the branch. This allows the code node to run once per article rather than once for the entire feed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Summarize Content – code
&lt;/h2&gt;

&lt;p&gt;The &lt;strong&gt;code&lt;/strong&gt; node receives one RSS item at a time from the splitInBatches node. Inside the node’s JavaScript function, the raw description text is extracted and trimmed. A simple prompt is constructed using an expression: &lt;code&gt;{{$json["description"]}}&lt;/code&gt;. The function then generates three concise, actionable points: the main topic, a practical takeaway, and a suggested next step for a coach. The output is a new JSON object attached to the execution, for example { "summary": "Topic: Using decorators to reduce boilerplate. Takeaway: Wrap repetitive logging. Next step: Apply to your onboarding emails." }.&lt;/p&gt;

&lt;h2&gt;
  
  
  Post to Slack – slack
&lt;/h2&gt;

&lt;p&gt;The &lt;strong&gt;slack&lt;/strong&gt; node gathers the summarized outputs from all code executions. It formats the results into a single message block, prepending the article title and linking back to the source. The node then posts the formatted text to the chosen Slack channel. The final message might read:&lt;br&gt;
"📚 &lt;em&gt;Advanced Python Techniques&lt;/em&gt;&lt;br&gt;
Learn decorators and context managers.&lt;br&gt;
• Topic: Using decorators to reduce boilerplate.&lt;br&gt;
• Takeaway: Wrap repetitive logging.&lt;br&gt;
• Next step: Apply to your onboarding emails.&lt;br&gt;
Read more: &lt;a href="https://example.com/python-tips" rel="noopener noreferrer"&gt;https://example.com/python-tips&lt;/a&gt;"&lt;/p&gt;

&lt;h3&gt;
  
  
  Worked Example
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Input (RSS item):&lt;/strong&gt;&lt;br&gt;
{ "title": "Time‑boxing Coaching Sessions", "link": "&lt;a href="https://coachingblog.com/timeboxing" rel="noopener noreferrer"&gt;https://coachingblog.com/timeboxing&lt;/a&gt;", "description": "A quick method to structure 30‑minute client calls with clear start, middle, and end phases." }&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;After splitInBatches:&lt;/strong&gt;&lt;br&gt;
The item is passed to the code node as a single execution context.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;After code:&lt;/strong&gt;&lt;br&gt;
The node produces { "summary": "Topic: Time‑boxing structure for 30‑min calls. Takeaway: Define start, middle, end phases. Next step: Map your own client intake flow." }.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;After slack:&lt;/strong&gt;&lt;br&gt;
The Slack message posted reads:&lt;br&gt;
"📚 &lt;em&gt;Time‑boxing Coaching Sessions&lt;/em&gt;&lt;br&gt;
A quick method to structure 30‑minute client calls with clear start, middle, and end phases.&lt;br&gt;
• Topic: Time‑boxing structure for 30‑min calls.&lt;br&gt;
• Takeaway: Define start, middle, end phases.&lt;br&gt;
• Next step: Map your own client intake flow.&lt;br&gt;
Read more: &lt;a href="https://coachingblog.com/timeboxing" rel="noopener noreferrer"&gt;https://coachingblog.com/timeboxing&lt;/a&gt;"&lt;/p&gt;

&lt;h2&gt;
  
  
  Watch Out For
&lt;/h2&gt;

&lt;p&gt;The httpRequest node relies on the RSS feeds being well‑formed. If a feed returns HTML error pages or missing description fields, the code node may throw an error or produce incomplete summaries. Adding a Set node before the code step to check for the existence of &lt;code&gt;description&lt;/code&gt; can prevent failures.&lt;/p&gt;

&lt;h2&gt;
  
  
  Key takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The scheduleTrigger starts the workflow each morning without manual input.&lt;/li&gt;
&lt;li&gt;The httpRequest node fetches raw RSS data from selected feeds, outputting individual items.&lt;/li&gt;
&lt;li&gt;The splitInBatches node isolates each item so the code node can summarize them one at a time.&lt;/li&gt;
&lt;li&gt;The code node generates concise actionable points from the article description.&lt;/li&gt;
&lt;li&gt;The slack node posts the formatted summary to a chosen channel, linking back to the source article.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Before you import it
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A running n8n instance (cloud or self-hosted).&lt;/li&gt;
&lt;li&gt;n8n account&lt;/li&gt;
&lt;li&gt;Slack workspace access&lt;/li&gt;
&lt;li&gt;RSS feed URLs for course content&lt;/li&gt;
&lt;li&gt;Sample data to test with, before pointing it at real records.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Get the free workflow
&lt;/h2&gt;

&lt;p&gt;The importable JSON for &lt;strong&gt;Morning Course Digest for Coaches&lt;/strong&gt; is free to download: &lt;a href="https://lanexbuilds.com/library" rel="noopener noreferrer"&gt;https://lanexbuilds.com/library&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This workflow was generated with AI assistance. Test it with sample data before using it on real data.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Cover photo by &lt;a href="https://pixabay.com/photos/startup-meeting-brainstorming-594090/" rel="noopener noreferrer"&gt;StartupStockPhotos&lt;/a&gt; on &lt;a href="https://pixabay.com" rel="noopener noreferrer"&gt;Pixabay&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>n8n</category>
      <category>workflow</category>
      <category>rss</category>
      <category>slack</category>
    </item>
    <item>
      <title>Morning Course Digest for Coaches Node Logic Deep Dive</title>
      <dc:creator>Lan Exequiel Mislang</dc:creator>
      <pubDate>Wed, 28 Oct 2026 08:09:51 +0000</pubDate>
      <link>https://dev.to/lanexbuilds/morning-course-digest-for-coaches-node-logic-deep-dive-1im9</link>
      <guid>https://dev.to/lanexbuilds/morning-course-digest-for-coaches-node-logic-deep-dive-1im9</guid>
      <description>&lt;p&gt;The alarm at 06:30 rings across a quiet home office. A coach opens her laptop and glances at the Slack channel dedicated to course updates. The daily summary has already arrived, compiled from three RSS feeds she follows. She scans the bullet points, picks one link to read fully, and drafts a response to a student all before her first client call at 09:00. This workflow automates that morning compilation. &lt;/p&gt;

&lt;h2&gt;
  
  
  At a glance
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Built for:&lt;/strong&gt; coaches and course creators&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Difficulty:&lt;/strong&gt; beginner&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Starts with:&lt;/strong&gt; Schedule Trigger (scheduleTrigger)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Steps:&lt;/strong&gt; 5 nodes&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tools:&lt;/strong&gt; n8n, Slack, RSS Feed&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Schedule Trigger Node
&lt;/h2&gt;

&lt;p&gt;The &lt;strong&gt;scheduleTrigger&lt;/strong&gt; node is the entry point for the workflow. It is configured to fire at 07:00 UTC every morning. On each run, it outputs a single execution context that downstream nodes inherit. The node does not fetch any data itself; it simply signals the start of the run and passes the current timestamp to the next node in the chain.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fetch RSS Feed Node
&lt;/h2&gt;

&lt;p&gt;The &lt;strong&gt;httpRequest&lt;/strong&gt; node receives the trigger payload from the schedule and initiates three separate HTTP GET requests to the configured RSS feed URLs. Each request returns an XML document structured with channel items, including title, link, description, and pubDate. The node outputs an array of these items, which can number from a handful to dozens depending on how recently each feed was updated. The node handles basic HTTP errors, but if a feed is permanently down, the workflow stops at this point unless error handling is added.&lt;/p&gt;

&lt;h2&gt;
  
  
  Split In Batches Node
&lt;/h2&gt;

&lt;p&gt;The &lt;strong&gt;splitInBatches&lt;/strong&gt; node takes the array of RSS items from the previous node and breaks them into manageable chunks. A batch size of 5 is typical, meaning if 12 items are returned, the workflow creates three batches: two full batches of five and one final batch of two. Each batch is processed independently by the next node, allowing the summarization logic to run in parallel across groups of articles rather than one by one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Code Node
&lt;/h2&gt;

&lt;p&gt;The &lt;strong&gt;code&lt;/strong&gt; node receives one batch of RSS items at a time. Inside the function, the node iterates over the items and extracts the title and description fields. It then constructs a prompt that asks the large language model to summarize the content into three concise, actionable points suitable for a coach’s audience. The node outputs a single string per batch, formatted as markdown with a bold title link and a bullet list of points. If the description is missing, the node skips that item and logs a warning, ensuring the output does not contain broken references.&lt;/p&gt;

&lt;h2&gt;
  
  
  Slack Node
&lt;/h2&gt;

&lt;p&gt;The &lt;strong&gt;slack&lt;/strong&gt; node gathers the formatted summary strings from all batches and posts them to a specified Slack channel via an incoming webhook. The message includes the date at the top and a divider line before the bullet points. The node outputs a confirmation ID from Slack, which the workflow uses to verify delivery, but the coach sees only the published message in the channel.&lt;/p&gt;

&lt;h3&gt;
  
  
  Worked Example
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Input (fictional RSS item):&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"title"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"10 Productivity Hacks for Online Coaches"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"description"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Learn how to batch your client sessions, use timers for focus blocks, and automate your email follow-ups. Updated this week."&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"link"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"https://examplecoachblog.com/productivity-hacks"&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;After scheduleTrigger:&lt;/strong&gt; The workflow begins; timestamp 2024-05-20T07:00:00Z is attached to the execution.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;After httpRequest:&lt;/strong&gt; The item is included in the XML response array alongside other feed entries.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;After splitInBatches (batch size 3):&lt;/strong&gt; This item resides in the first batch of three.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;After code node:&lt;/strong&gt; The output string is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;&lt;span class="gs"&gt;**10 Productivity Hacks for Online Coaches**&lt;/span&gt;
&lt;span class="p"&gt;-&lt;/span&gt; Batch client sessions to reduce context switching.
&lt;span class="p"&gt;-&lt;/span&gt; Set timers for deep focus blocks during peak hours.
&lt;span class="p"&gt;-&lt;/span&gt; Automate email follow-ups after each session.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;After slack node:&lt;/strong&gt; The message appears in the "course-digest" channel with the date prefix and the markdown above.&lt;/p&gt;

&lt;h2&gt;
  
  
  Key takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The scheduleTrigger node fires on a cron-like schedule and passes a timestamp to downstream nodes.&lt;/li&gt;
&lt;li&gt;The httpRequest node fetches raw XML from RSS feeds and outputs an item array that may vary in length.&lt;/li&gt;
&lt;li&gt;The splitInBatches node divides the item array into chunks so the code node can process them in parallel batches.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Before you import it
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A running n8n instance (cloud or self-hosted).&lt;/li&gt;
&lt;li&gt;n8n account&lt;/li&gt;
&lt;li&gt;Slack workspace access&lt;/li&gt;
&lt;li&gt;RSS feed URLs for course content&lt;/li&gt;
&lt;li&gt;Sample data to test with, before pointing it at real records.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Get the free workflow
&lt;/h2&gt;

&lt;p&gt;The importable JSON for &lt;strong&gt;Morning Course Digest for Coaches&lt;/strong&gt; is free to download: &lt;a href="https://lanexbuilds.com/library" rel="noopener noreferrer"&gt;https://lanexbuilds.com/library&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This workflow was generated with AI assistance. Test it with sample data before using it on real data.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Cover photo by &lt;a href="https://pixabay.com/photos/online-class-course-teacher-laptop-6204349/" rel="noopener noreferrer"&gt;Tumisu&lt;/a&gt; on &lt;a href="https://pixabay.com" rel="noopener noreferrer"&gt;Pixabay&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>automation</category>
      <category>beginners</category>
      <category>productivity</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
