<?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: Cess Mbugua</title>
    <description>The latest articles on DEV Community by Cess Mbugua (@mbugua_cessy).</description>
    <link>https://dev.to/mbugua_cessy</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3626809%2F8965597d-6873-451e-8e28-585d0370197b.jpeg</url>
      <title>DEV Community: Cess Mbugua</title>
      <link>https://dev.to/mbugua_cessy</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mbugua_cessy"/>
    <language>en</language>
    <item>
      <title>Day 1 of 60 — Learning AI Integration in Public</title>
      <dc:creator>Cess Mbugua</dc:creator>
      <pubDate>Tue, 28 Apr 2026 20:19:18 +0000</pubDate>
      <link>https://dev.to/mbugua_cessy/day-1-of-60-learning-ai-integration-in-public-4iie</link>
      <guid>https://dev.to/mbugua_cessy/day-1-of-60-learning-ai-integration-in-public-4iie</guid>
      <description>&lt;p&gt;I'm a student learning AI integration and automation by building one real workflow every day for 60 days. Everything gets documented and pushed to GitHub. Starting today.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fvw93lqesq00ds46zhyt8.PNG" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fvw93lqesq00ds46zhyt8.PNG" alt=" " width="800" height="329"&gt;&lt;/a&gt;&lt;br&gt;
What I learned: you can use an LLM to drive actual routing logic in a workflow — not just generate text. Claude reads each email and returns a full JSON decision object that n8n acts on instantly.&lt;br&gt;
How it works:&lt;/p&gt;

&lt;p&gt;Gmail triggers n8n on every new email&lt;br&gt;
Claude API classifies it — urgency, category, sentiment, summary &amp;amp; suggested reply&lt;br&gt;
Switch node routes it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Urgent → instant Slack alert&lt;/li&gt;
&lt;li&gt; Standard → Airtable + Slack&lt;/li&gt;
&lt;li&gt; FAQ → auto-replied by Claude, zero human touch&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Biggest lesson:&lt;/strong&gt; getting Claude to return consistent, parseable JSON every time is harder than it sounds — and if it breaks, everything breaks. Prompt structure matters more than I expected.&lt;br&gt;
Stack: n8n · Claude API · Gmail · Airtable · Slack&lt;br&gt;
🔗 &lt;a href="https://github.com/mbuguacessy-glitch/ai-support-ticket-router" rel="noopener noreferrer"&gt;https://github.com/mbuguacessy-glitch/ai-support-ticket-router&lt;/a&gt;&lt;br&gt;
59 builds to go!&lt;/p&gt;

&lt;h1&gt;
  
  
  learninpublic #buildinpublic #automation #ai
&lt;/h1&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>buildinpublic</category>
      <category>learning</category>
    </item>
  </channel>
</rss>
