<?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: Ahmed Negm</title>
    <description>The latest articles on DEV Community by Ahmed Negm (@ahmednegm91).</description>
    <link>https://dev.to/ahmednegm91</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%2F4256389%2Fb0c04ac7-51b4-41f8-b2a3-110ca4a69ea2.png</url>
      <title>DEV Community: Ahmed Negm</title>
      <link>https://dev.to/ahmednegm91</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ahmednegm91"/>
    <language>en</language>
    <item>
      <title>Designing Arabic-first support triage with a safe send boundary</title>
      <dc:creator>Ahmed Negm</dc:creator>
      <pubDate>Fri, 20 Nov 2026 21:57:04 +0000</pubDate>
      <link>https://dev.to/ahmednegm91/designing-arabic-first-support-triage-with-a-safe-send-boundary-55ei</link>
      <guid>https://dev.to/ahmednegm91/designing-arabic-first-support-triage-with-a-safe-send-boundary-55ei</guid>
      <description>&lt;p&gt;Support automation should help classify and draft a response without quietly turning a generated answer into a sent message. This n8n portfolio demo explores that boundary for Arabic-first and English support requests.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the workflow does
&lt;/h2&gt;

&lt;p&gt;The project is split into nine workflows with four n8n Data Tables. Channel adapters cover a web form, Gmail, Telegram, WhatsApp, and a simulated multichannel API. A classifier routes the message into FAQ matching and a knowledge-grounded draft path. Gemini is the primary model with Groq as a configured fallback.&lt;/p&gt;

&lt;p&gt;The workflow records ticket and event data, can prepare a response draft, and has an escalation path when the message needs human attention. The design goal is to give an operator context and a proposed next step while leaving uncertain or sensitive cases for review.&lt;/p&gt;

&lt;p&gt;That separation matters for a support inbox: a plausible answer is not necessarily an authorized answer, and a successful model response is not the same as successful delivery to a customer. Channel boundaries and escalation rules should be explicit before connecting real accounts.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is and is not verified
&lt;/h2&gt;

&lt;p&gt;The repository reports 72 of 72 offline checks passing. An author report describes local tests using fictional messages, but I have not independently repeated those on the user's n8n runtime. Live Gmail, Telegram, and WhatsApp sending is off and not verified; the public demo sets ALLOW_LIVE_SEND=false. Some channel behavior is simulated. The walkthrough videos are screenshot-led edits, not direct screen recordings.&lt;/p&gt;

&lt;p&gt;This is not a production support service, SLA, guaranteed-accuracy system, implemented RAG stack, or booking automation. To adapt it for a business, the message sources, knowledge ownership, escalation criteria, privacy requirements, retention, and approved sending channels would need to be defined and tested with that organization.&lt;/p&gt;

&lt;p&gt;Source and setup notes: &lt;a href="https://github.com/ahmednegm91/ai-customer-support-triage" rel="noopener noreferrer"&gt;https://github.com/ahmednegm91/ai-customer-support-triage&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This project demonstrates an architecture for assisted triage and review; it does not claim verified delivery or autonomous customer support.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>architecture</category>
    </item>
    <item>
      <title>Human gates in an n8n lead-to-cash workflow</title>
      <dc:creator>Ahmed Negm</dc:creator>
      <pubDate>Fri, 20 Nov 2026 21:56:46 +0000</pubDate>
      <link>https://dev.to/ahmednegm91/human-gates-in-an-n8n-lead-to-cash-workflow-2ljf</link>
      <guid>https://dev.to/ahmednegm91/human-gates-in-an-n8n-lead-to-cash-workflow-2ljf</guid>
      <description>&lt;p&gt;A lead-to-cash workflow is not one automation. Intake, qualification, proposal drafting, contract creation, invoicing, and payment tracking each have different data and approval boundaries. I built this portfolio demo as six modular n8n workflows so those transitions are explicit.&lt;/p&gt;

&lt;h2&gt;
  
  
  A modular path from lead to payment record
&lt;/h2&gt;

&lt;p&gt;The demo receives leads, checks for duplicates, and stores the record in n8n Data Tables. Gemini or Groq can help qualify the lead and draft a proposal, but the output remains a draft. Sales and finance decisions sit behind human gates rather than being inferred from model text.&lt;/p&gt;

&lt;p&gt;After a person reviews the proposal, the workflow can create draft contract and invoice records for further review. Payment events are logged manually; the demo does not connect to a payment gateway or bank. Revenue summaries use the records already present in the tables.&lt;/p&gt;

&lt;p&gt;The important design choice is keeping states and handoffs visible: a model can suggest a next step, while a person approves customer-facing terms and finance actions. The modular split also makes it easier to test failure paths without pretending the connected business systems are in place.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the verification means
&lt;/h2&gt;

&lt;p&gt;The supplied Node.js simulator passed 39 of 39 scenarios and exercised 157 of 157 executable workflow nodes. That is simulator coverage, not a live test of n8n, Gemini, Groq, a CRM, email delivery, e-signatures, a payment gateway, or bank settlement. The original screenshots predate export QA changes; the updated graph images were rendered from corrected workflow JSON rather than captured from live runs.&lt;/p&gt;

&lt;p&gt;This project does not claim collected revenue, verified payments, customer ROI, or production readiness. A real implementation would need agreed CRM and finance schemas, authentication, permission design, exception ownership, and tests against the customer's actual systems.&lt;/p&gt;

&lt;p&gt;Source and demo notes: &lt;a href="https://github.com/ahmednegm91/ai-lead-to-cash-automation" rel="noopener noreferrer"&gt;https://github.com/ahmednegm91/ai-lead-to-cash-automation&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This is a demonstration of guarded workflow design that can be tailored after a business's approval rules and integrations are understood.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>architecture</category>
    </item>
    <item>
      <title>A safer n8n invoice workflow: extract, validate, then review</title>
      <dc:creator>Ahmed Negm</dc:creator>
      <pubDate>Fri, 20 Nov 2026 21:52:12 +0000</pubDate>
      <link>https://dev.to/ahmednegm91/a-safer-n8n-invoice-workflow-extract-validate-then-review-13pp</link>
      <guid>https://dev.to/ahmednegm91/a-safer-n8n-invoice-workflow-extract-validate-then-review-13pp</guid>
      <description>&lt;p&gt;An invoice workflow can fail in two different ways: it can extract the wrong value, or it can confidently move a correct-looking value into the wrong business action. I designed this n8n demo to make those steps visible and keep approval outside the automation.&lt;/p&gt;

&lt;p&gt;The example processes Arabic or English invoices supplied as PDF, JPG, or PNG. It uses Gemini to extract fields, then applies deterministic checks to catch arithmetic inconsistencies before writing a record to an n8n Data Table. Each record remains pending review.&lt;/p&gt;

&lt;h2&gt;
  
  
  The flow
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Receive the file.&lt;/strong&gt; The workflow accepts an invoice document and routes supported formats into extraction.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Extract candidate fields.&lt;/strong&gt; Gemini returns structured values such as supplier, invoice number, line amounts, tax, and total. These are suggestions from a model, not trusted accounting data.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check arithmetic in code.&lt;/strong&gt; The workflow recalculates totals and compares them with the extracted total. A mismatch is recorded as a validation issue rather than silently accepted.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Look for duplicates.&lt;/strong&gt; It checks the supplier and invoice number against prior records. This catches a common repeat-submission case, though it is not a universal duplicate detector.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Save for review.&lt;/strong&gt; The result is written to an n8n Data Table with a pending-review state so a person can inspect the document and extracted values.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Why keep approval separate?
&lt;/h2&gt;

&lt;p&gt;Extraction quality and business authorization are different questions. A model can help turn an unstructured document into fields, and code can check arithmetic, but neither decides whether a payment should be approved. Keeping the demo at “pending review” makes that boundary explicit.&lt;/p&gt;

&lt;p&gt;The same separation is useful when tailoring an invoice process for a business: define what the system may extract, which checks can be deterministic, who reviews exceptions, and what authenticated downstream action is permitted. A production integration would also need the customer’s document storage, access rules, accounting system, retention policy, and error-handling requirements. Those are not included here.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I verified
&lt;/h2&gt;

&lt;p&gt;The repository includes two workflow exports, six screenshots, synthetic invoice examples, and 26 passing offline checks. Those checks do not establish a fresh live n8n run or production readiness. The public exports need credentials, the supporting subworkflow and Data Tables to be configured, and fresh runtime testing; the backup Gemini model also needs review. The demo does not approve invoices, post to an ERP, or claim zero errors or measured savings.&lt;/p&gt;

&lt;p&gt;Source and setup notes: &lt;a href="https://github.com/ahmednegm91/intelligent-invoice-processing" rel="noopener noreferrer"&gt;https://github.com/ahmednegm91/intelligent-invoice-processing&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This is a portfolio demonstration of an approach I can adapt after requirements and approval boundaries are clear.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>tooling</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
