<?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: Vivekanand Malakar</title>
    <description>The latest articles on DEV Community by Vivekanand Malakar (@vivek120891).</description>
    <link>https://dev.to/vivek120891</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%2F3938794%2F7766f050-c608-462f-b487-d06f18bee006.png</url>
      <title>DEV Community: Vivekanand Malakar</title>
      <link>https://dev.to/vivek120891</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/vivek120891"/>
    <language>en</language>
    <item>
      <title>I built a 3-agent Python + Claude pipeline: RSS ingestion AI scoring Gmail MCP email drafts. Repo inside.</title>
      <dc:creator>Vivekanand Malakar</dc:creator>
      <pubDate>Tue, 19 May 2026 19:51:37 +0000</pubDate>
      <link>https://dev.to/vivek120891/i-built-a-3-agent-python-claude-pipeline-rss-ingestion-ai-scoring-gmail-mcp-email-drafts-3cfh</link>
      <guid>https://dev.to/vivek120891/i-built-a-3-agent-python-claude-pipeline-rss-ingestion-ai-scoring-gmail-mcp-email-drafts-3cfh</guid>
      <description>&lt;h1&gt;
  
  
  Multi-Agent Job Outreach Pipeline — Supervisor/Worker Pattern in Python + Claude
&lt;/h1&gt;

&lt;p&gt;Wanted to share a multi-agent pattern I've been running — it's a supervisor/worker architecture that maps cleanly to n8n if anyone wants to port it.&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%2Forbxtbfyyhstbsn62fwi.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%2Forbxtbfyyhstbsn62fwi.png" alt="Multi-agent pipeline architecture" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  The Pipeline
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Agent 1 — Ingestion + Scoring
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Pulls from Remotive API, WeWorkRemotely RSS, and Upwork RSS (all free, no keys needed)&lt;/li&gt;
&lt;li&gt;Each item goes to Claude with a structured scoring prompt (1–10 against defined criteria)&lt;/li&gt;
&lt;li&gt;Only items scoring ≥ 6 pass through to the next agent&lt;/li&gt;
&lt;li&gt;Output: &lt;code&gt;items_YYYY-MM-DD.json&lt;/code&gt; with score, reason, pain point, and pitch angle per item&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Agent 2 — Context-aware Email Drafter
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Reads the scored items JSON&lt;/li&gt;
&lt;li&gt;For each item: Claude reads the full source text and writes a personalised email that references specific details — stack, stated problems, their own wording&lt;/li&gt;
&lt;li&gt;No templates. Every draft is generated fresh against the actual source content&lt;/li&gt;
&lt;li&gt;Output: &lt;code&gt;drafts_YYYY-MM-DD.json&lt;/code&gt; — human reviews before anything is sent&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Agent 3 — Gmail MCP Send
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Approved drafts sent via Gmail MCP directly from inbox&lt;/li&gt;
&lt;li&gt;Full send log maintained in JSON&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Why This Pattern Is Interesting Technically
&lt;/h2&gt;

&lt;p&gt;The scoring step is the key. Without it, you're passing 60+ low-signal items to an LLM and burning tokens on noise. With a Claude scoring gate, only ~10–15% of raw items make it through — and those are the ones worth spending a full generation on.&lt;/p&gt;

&lt;p&gt;The other thing worth noting: keeping state in flat JSON files rather than a DB is underrated for single-user pipelines at this scale. Simple to inspect, easy to debug, no infra overhead.&lt;/p&gt;




&lt;h2&gt;
  
  
  n8n Equivalent of Each Agent
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Agent&lt;/th&gt;
&lt;th&gt;n8n Implementation&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Agent 1&lt;/td&gt;
&lt;td&gt;Schedule trigger + HTTP Request nodes + AI Agent node (scoring prompt) + Filter node&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Agent 2&lt;/td&gt;
&lt;td&gt;Manual trigger + Loop over items + AI Agent node (drafting prompt) + Write file&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Agent 3&lt;/td&gt;
&lt;td&gt;Manual trigger + Gmail node with approval gate&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;h2&gt;
  
  
  Stack
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Claude claude-sonnet-4-6&lt;/li&gt;
&lt;li&gt;Python 3.12 + httpx&lt;/li&gt;
&lt;li&gt;Gmail MCP&lt;/li&gt;
&lt;li&gt;JSON for state&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Repo
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/vivekanandtech/ai-outreach-agent" rel="noopener noreferrer"&gt;https://github.com/vivekanandtech/ai-outreach-agent&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Happy to share the scoring prompt or the drafter prompt in the comments — took ~20 iterations to get both right.&lt;/p&gt;

&lt;p&gt;Anyone built something similar with native n8n nodes?&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I build systems like this for agencies and ops-heavy businesses. Portfolio at &lt;a href="https://flowvanta.dev/" rel="noopener noreferrer"&gt;flowvanta.dev&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>n8nbrightdatachallenge</category>
      <category>python</category>
    </item>
  </channel>
</rss>
