<?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: Felix</title>
    <description>The latest articles on DEV Community by Felix (@felix__s).</description>
    <link>https://dev.to/felix__s</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%2F3840372%2Fce66d723-676c-43c0-ac33-a5c80a0808b8.png</url>
      <title>DEV Community: Felix</title>
      <link>https://dev.to/felix__s</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/felix__s"/>
    <language>en</language>
    <item>
      <title>Purchase Order Extraction with n8n: Free PDF to Google Sheets Automation [Workflow Included]</title>
      <dc:creator>Felix</dc:creator>
      <pubDate>Wed, 07 Oct 2026 07:37:16 +0000</pubDate>
      <link>https://dev.to/felix__s/purchase-order-extraction-with-n8n-free-pdf-to-google-sheets-automation-workflow-included-2n8o</link>
      <guid>https://dev.to/felix__s/purchase-order-extraction-with-n8n-free-pdf-to-google-sheets-automation-workflow-included-2n8o</guid>
      <description>&lt;p&gt;👋 Hey dev.to Community,&lt;/p&gt;

&lt;p&gt;A while back I shared a purchase order extractor I built for a friend with a big online store who was working through PO PDFs by hand. It's now published on the n8n template library, so you can grab it for free.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What it does:&lt;/strong&gt; you upload one or many PO PDFs through a form, and it extracts each into a Google Sheet, one row per line item, with the source document name on every row. It handles POs in different layouts, runs them as a batch, and before writing it checks each PO number against the sheet so nothing gets entered twice. The completion screen then tells you what was added, what it skipped as already processed (with the PO number), and whether any extraction looked off.&lt;/p&gt;

&lt;p&gt;One thing worth pulling out if you build batch extraction of your own: a batch is only worth running if you can trust it without eyeballing every row. The feature that actually made this usable wasn't extraction accuracy, it was the summary that surfaces skipped duplicates and failed fields, so you know exactly what to check instead of assuming it all worked.&lt;/p&gt;

&lt;p&gt;Template (free to grab): &lt;a href="https://n8n.io/workflows/18674-extract-purchase-orders-from-pdfs-with-easybits-google-sheets-and-google-drive/" rel="noopener noreferrer"&gt;https://n8n.io/workflows/18674-extract-purchase-orders-from-pdfs-with-easybits-google-sheets-and-google-drive/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The optional EDI 850 add-on (for pushing orders into SAP and other ERPs) isn't in the library version, but it sits in my repo alongside 25+ other workflows: &lt;a href="https://github.com/felix-sattler-easybits/n8n-workflows" rel="noopener noreferrer"&gt;https://github.com/felix-sattler-easybits/n8n-workflows&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you're automating PO or invoice intake too, how are you handling the fact that every supplier sends a different layout? That was the hardest part to make reliable here, and I'd be curious how others approach it.&lt;/p&gt;

&lt;p&gt;Best,&lt;br&gt;
Felix&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>automation</category>
      <category>n8n</category>
    </item>
    <item>
      <title>3 Document Workflows Small Businesses Should Set Up Before Year End [Workflows Included]</title>
      <dc:creator>Felix</dc:creator>
      <pubDate>Wed, 30 Sep 2026 09:11:04 +0000</pubDate>
      <link>https://dev.to/felix__s/3-document-workflows-small-businesses-should-set-up-before-year-end-workflows-included-2hi1</link>
      <guid>https://dev.to/felix__s/3-document-workflows-small-businesses-should-set-up-before-year-end-workflows-included-2hi1</guid>
      <description>&lt;p&gt;👋 Hey dev.to Community,&lt;/p&gt;

&lt;p&gt;Year end is when all the document chaos catches up with small businesses at once, the shoebox of receipts, the contracts nobody tracked, the folder that is just "scan_final_2.pdf" forty times over. These are the three document workflows that saved my clients the most time this past year, all built around simple extraction and a place to put the data, and they are worth setting up now to make January far less painful.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;1. Auto log every invoice and receipt as it arrives.&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;Extract the key fields (date, vendor, amount, tax) from each invoice and append them straight to a single sheet, so instead of sorting a pile in January your accountant gets one clean list and you can actually see your spending as the year closes. To make it fully hands off, use a Gmail trigger as the entry point, and it will process invoices attached to incoming emails automatically, no manual upload needed.&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F63tqgzlzg7gxldceuege.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F63tqgzlzg7gxldceuege.png" alt="batch invoice extractor" width="" height=""&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;2. A contract renewal and cancellation watchdog.&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;Most auto renewals sneak through at year end because nobody is watching the dates. Extract the renewal term and notice period from each contract, store them, and get a Slack or email nudge before a cancellation deadline passes. This one tends to pay for itself the first time it catches a subscription you meant to drop.&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcjk0cn1378h5y6757kof.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcjk0cn1378h5y6757kof.png" alt="contract renewal watchdog" width="800" height="320"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;3. Sort incoming documents by type automatically.&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;Classify each document as invoice, contract, statement, or whatever buckets you care about, then file it in the right place without touching it. By the time you need something for the accountant or the tax filing, it is already where it should be.&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1s0y693053tzy0dvy03l.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1s0y693053tzy0dvy03l.png" alt="document classification" width="800" height="320"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;None of these are big builds, and that is the point: one entry point, one extraction step, one place the data lands. If you want a head start, my ready to use templates are here, most of them document focused: &lt;a href="https://n8n.io/creators/easybits/" rel="noopener noreferrer"&gt;https://n8n.io/creators/easybits/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;There are also a few more on my GitHub that I never uploaded to n8n: &lt;a href="https://github.com/felix-sattler-easybits/n8n-workflows" rel="noopener noreferrer"&gt;https://github.com/felix-sattler-easybits/n8n-workflows&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Pick the workflow that matches your biggest year end headache and set up just that one this week. Something that quietly logs your documents all year beats a heroic cleanup every January, and if you get stuck setting any of these up, feel free to drop a comment or reach out, happy to help.&lt;/p&gt;

&lt;p&gt;I actually run the invoice logging one on my own documents too, so everything is already sorted and ready when tax time comes around instead of me digging for it. Curious what everyone else is scrambling to get in order before the books close.&lt;/p&gt;

&lt;p&gt;Best,&lt;br&gt;
Felix&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>opensource</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Invoice Automation in n8n – extract data from many invoices at once into Google Sheets [Workflow Included]</title>
      <dc:creator>Felix</dc:creator>
      <pubDate>Thu, 13 Aug 2026 12:39:54 +0000</pubDate>
      <link>https://dev.to/felix__s/invoice-automation-in-n8n-extract-data-from-many-invoices-at-once-into-google-sheets-workflow-kn8</link>
      <guid>https://dev.to/felix__s/invoice-automation-in-n8n-extract-data-from-many-invoices-at-once-into-google-sheets-workflow-kn8</guid>
      <description>&lt;p&gt;👋 Hey dev.to Community,&lt;/p&gt;

&lt;p&gt;I've built a lot of finance workflows over the last few months for friends who run small businesses, and going back through my library I realised I'd never shared the most basic one people keep asking for: a simple batch invoice extractor. So I cleaned one up and pushed it to the n8n template library: &lt;a href="https://n8n.io/workflows/16774-extract-batch-invoice-data-from-form-uploads-with-easybits-and-google-sheets/" rel="noopener noreferrer"&gt;Extract batch invoice data from form uploads with easybits and Google Sheets&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The idea is simple. You upload one or many invoices (JPG, PNG, or PDF) through a single form, and it extracts the data from all of them in one go, instead of dragging every invoice in one by one. Each invoice lands as a row in a Google Sheet, and when the batch finishes, the form shows a summary marking every file with a ✅ or ❌ so you instantly see which ones need a second look.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How it's set up:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;An n8n Form takes one or more invoice files.&lt;/li&gt;
&lt;li&gt;The files get split into one item per file, keeping the original filename.&lt;/li&gt;
&lt;li&gt;It loops over the invoices one at a time, sending each to the easybits Extractor, which returns the fields (invoice number, date, vendor, total, and so on) as a structured data object.&lt;/li&gt;
&lt;li&gt;The filename gets reattached, and a check runs over the critical fields.&lt;/li&gt;
&lt;li&gt;One row per invoice is appended to Google Sheets, with a pass/fail status.&lt;/li&gt;
&lt;li&gt;A batch summary is shown as the form's completion message.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A few things from the build that might save you time on your own flows:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The extractor bundles everything you hand it into one request.&lt;/strong&gt; Pass it all the files at once and you get one merged result back, not one per invoice. Looping one file at a time is what gives you a clean result per invoice. This one cost me a debugging session.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Treat "missing" as a signal, not an error.&lt;/strong&gt; The extractor returns null when a field isn't on the document. Instead of fighting that, I lean into it: a small check flags any invoice missing a critical field, which is what powers the ✅/❌ summary. Worth catching the sneaky empties too (the string "null", empty strings, whitespace), so nothing slips through looking present when it isn't.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The fields are yours to change.&lt;/strong&gt; The mapped fields are just a starting point, so you can add whatever you need to pull from your own invoices, like a VAT ID, PO number, or IBAN. The extractor also has auto-mapping, so you can upload one example invoice, let it detect the fields, and tweak from there.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I also recorded a short video showing how it runs end to end, which I'll post alongside this.&lt;/p&gt;

&lt;p&gt;For more free workflows, feel free to check my GitHub as well: &lt;a href="https://github.com/felix-sattler-easybits/n8n-workflows" rel="noopener noreferrer"&gt;https://github.com/felix-sattler-easybits/n8n-workflows&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A star helps other builders find it, so I'd be really thankful for that support.&lt;/p&gt;

&lt;p&gt;How do you all handle the invoices that fail extraction? Curious whether people flag them for manual review like this or route them elsewhere.&lt;/p&gt;

&lt;p&gt;Best,&lt;br&gt;
Felix&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>ai</category>
      <category>automation</category>
    </item>
    <item>
      <title>Purchase Order Automation in n8n – batch-extract POs and generate EDI 850 files for your ERP [Workflow Included]</title>
      <dc:creator>Felix</dc:creator>
      <pubDate>Wed, 12 Aug 2026 14:51:58 +0000</pubDate>
      <link>https://dev.to/felix__s/purchase-order-automation-in-n8n-batch-extract-pos-and-generate-edi-850-files-for-your-erp-45hf</link>
      <guid>https://dev.to/felix__s/purchase-order-automation-in-n8n-batch-extract-pos-and-generate-edi-850-files-for-your-erp-45hf</guid>
      <description>&lt;p&gt;👋 Hey dev.to Community,&lt;/p&gt;

&lt;p&gt;A while back I built a purchase order extractor for a friend who was drowning in PO PDFs. It let him batch-upload the documents through a form and pull all the data into a Google Sheet through the &lt;a href="https://go.easybits.tech/edi-files" rel="noopener noreferrer"&gt;easybits extractor&lt;/a&gt;. That alone saved him a lot of manual re-typing.&lt;/p&gt;

&lt;p&gt;Last week he told me his company is moving onto SAP, and he asked whether the workflow could also spit out EDI files so he can push the orders straight into the ERP instead of keying them in by hand. So I built that in, and while I was at it I made the whole thing a good bit more robust.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How it's set up:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Batch PDF upload:&lt;/strong&gt; the form takes one or many PO PDFs at once, and a toggle lets you decide per submission whether you also want EDI files out.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Extraction:&lt;/strong&gt; each PO runs through the easybits extractor one at a time and lands in a Google Sheet, one row per line item, with the source document name on every row so you can always trace a row back to its PDF.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;EDI 850 generation (optional):&lt;/strong&gt; when the toggle is on, each PO is also turned into a valid X12 850 EDI file and saved to a Drive folder, ready to upload into SAP. A separate sub-workflow handles the generation, so the main flow stays clean.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Duplicate check:&lt;/strong&gt; after extraction it checks the PO number against what's already in the sheet. If that PO was processed before, it skips it, so you never get double entries.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Flag summary:&lt;/strong&gt; the completion screen tells you if any field was missing or looked off in an extraction, and lists any duplicates it skipped along with the PO number.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Short video attached showing a batch run of three POs with EDI generation switched on, then a re-upload of one of them so you can see the duplicate check catch it and report which document and PO number it was.&lt;/p&gt;

&lt;p&gt;Both workflows (the main one plus the EDI sub-workflow) and a setup guide are here: &lt;a href="https://github.com/felix-sattler-easybits/n8n-workflows/tree/f4dec1bef3561aa9e803bb21b96ebff1ab0dde04/easybits-purchase-order-extractor-v2" rel="noopener noreferrer"&gt;https://github.com/felix-sattler-easybits/n8n-workflows/tree/f4dec1bef3561aa9e803bb21b96ebff1ab0dde04/easybits-purchase-order-extractor-v2&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You'll also find it alongside 20+ other n8n workflows in my repo. If it's useful to you, a ⭐ really helps other builders discover it too: &lt;a href="https://github.com/felix-sattler-easybits/n8n-workflows" rel="noopener noreferrer"&gt;https://github.com/felix-sattler-easybits/n8n-workflows&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Curious how the rest of you are handling the PO-to-ERP step. Are you going through EDI, hitting a direct API, or still uploading into the ERP by hand?&lt;/p&gt;

&lt;p&gt;Best,&lt;br&gt;
Felix&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>automation</category>
      <category>dataextraction</category>
    </item>
    <item>
      <title>Data table extraction in n8n – fixing multi-page PDF table extraction in n8n [Workflow Included]</title>
      <dc:creator>Felix</dc:creator>
      <pubDate>Fri, 31 Jul 2026 11:25:57 +0000</pubDate>
      <link>https://dev.to/felix__s/data-table-extraction-in-n8n-fixing-multi-page-pdf-table-extraction-in-n8n-workflow-included-edg</link>
      <guid>https://dev.to/felix__s/data-table-extraction-in-n8n-fixing-multi-page-pdf-table-extraction-in-n8n-workflow-included-edg</guid>
      <description>&lt;p&gt;👋 Hey dev.to community,&lt;/p&gt;

&lt;p&gt;One of our users reached out with a problem I think a lot of people hit: he was extracting a data table from a multi-page PDF, and the cells kept bleeding into each other. About 95% of the data came out right, but 5% got mixed up with the wrong rows, so he could never fully trust the result.&lt;/p&gt;

&lt;p&gt;This week we shipped something to fix exactly that: an extraction engine dropdown you can set per pipeline. In the video I run the same messy multi-page table through both engines, with a small n8n workflow that checks every extracted cell against a reference so you can actually see what slipped.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What the two engines are:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The General engine runs on Gemini and covers about 90% of everyday extraction (image description, classification, normal documents). The Specialized engine runs on Mistral and is OCR-optimized for document-heavy work like dense or multi-page tables.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What the test showed:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The General engine slipped on a couple of rows and came back with pass = false. Switching the pipeline to Specialized took the same document to 100%, every cell correct. The bonus I did not expect: Specialized also ran faster on the multi-page PDF.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A couple of takeaways even if you skip the video:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;For dense or multi-page tables, reach for the Specialized extraction engine. For most other jobs, General is the right default.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Do not eyeball table extraction. A tiny workflow that cross-checks each cell against a known-good reference tells you exactly which rows are wrong, instead of you scanning 20 rows by hand.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;If rows still bleed after switching engines, it is almost always the response structure. Model the table as one records field set as an array of objects with each column nested inside, not one separate list per column.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Want to try the new engine on your own tables? The &lt;a href="https://go.easybits.tech/data-table-extraction" rel="noopener noreferrer"&gt;easybits Extractor&lt;/a&gt; is a verified community node with 50 free monthly API requests included. On n8n Cloud, just search 'easybits Extractor' in the node panel, no install needed. Self-hosted, install '@easybits/n8n-nodes-extractor' from Settings, Community Nodes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;I put a full step-by-step guide (PDF) for setting up your extractor for data tables here:&lt;/strong&gt; &lt;a href="https://github.com/felix-sattler-easybits/n8n-workflows/tree/ee1ed5fe0a3e898843422a619922cedb7cf618c4/easybits-data-table-extraction" rel="noopener noreferrer"&gt;https://github.com/felix-sattler-easybits/n8n-workflows/tree/ee1ed5fe0a3e898843422a619922cedb7cf618c4/easybits-data-table-extraction&lt;/a&gt; (the validation workflow from the video is in that same folder too, so you can import it and try it on your own tables)&lt;/p&gt;

&lt;p&gt;What is the most stubborn multi-page document you have tried to pull a table out of?&lt;/p&gt;

&lt;p&gt;Best,&lt;br&gt;
Felix&lt;/p&gt;

</description>
      <category>ai</category>
      <category>tutorial</category>
      <category>automation</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Purchase Order Automation in n8n – extract PO data straight into a Google Sheet [Workflow Included]</title>
      <dc:creator>Felix</dc:creator>
      <pubDate>Thu, 02 Jul 2026 12:06:44 +0000</pubDate>
      <link>https://dev.to/felix__s/purchase-order-automation-in-n8n-extract-po-data-straight-into-a-google-sheet-workflow-included-45ji</link>
      <guid>https://dev.to/felix__s/purchase-order-automation-in-n8n-extract-po-data-straight-into-a-google-sheet-workflow-included-45ji</guid>
      <description>&lt;p&gt;👋 Hey dev.to community,&lt;/p&gt;

&lt;p&gt;Last week I shipped a workflow I built for a friend who runs an online shop. He called me again a few days later with a new headache: he's drowning in Purchase Orders. Every single one gets opened by hand, the data typed into a Google Sheet, and that sheet uploaded into his ERP to update his numbers. Hours a week, pure copy-paste.&lt;/p&gt;

&lt;p&gt;So I built him something to kill that step. He uploads the PO PDFs through a simple n8n form, and a structured Google Sheet comes out the other end. He just downloads it and pushes it to his ERP.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;How it's set up:&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The form &lt;strong&gt;accepts multiple PDFs at once&lt;/strong&gt;, so he can batch a whole stack instead of doing them one by one. Each PO loops through on its own so nothing gets jumbled.&lt;/p&gt;

&lt;p&gt;The extraction runs on the &lt;a href="https://go.easybits.tech/poe" rel="noopener noreferrer"&gt;easybits Extractor&lt;/a&gt; node (&lt;code&gt;@easybits/n8n-nodes-extractor&lt;/code&gt;). I set the field structure up in two parts: the &lt;strong&gt;header fields&lt;/strong&gt; that appear once per PO (PO number, PO date, delivery date, mark for, PR number, reference no), plus an &lt;strong&gt;articles array&lt;/strong&gt; for the line items, each holding article name, unit and quantity. That array is the key bit, it gives you one entry per row of the PO table, and I flatten it into one sheet row per article with the header details repeated on each.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Two things I added because real documents are messy:&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Error flagging&lt;/strong&gt;. If any field comes back empty, the completion screen lists which document and which field didn't extract cleanly, so he knows exactly which PO to double-check instead of trusting it blindly.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Document name column&lt;/strong&gt;. The original filename lands in the sheet next to every row, so if a number looks off he can jump straight back to the source PDF.&lt;/p&gt;

&lt;p&gt;Workflow JSON is on GitHub: &lt;a href="https://github.com/felix-sattler-easybits/n8n-workflows/blob/c38749a68fd6ea4ae6ebff41789d35cceaacdef1/easybits-purchase-order-extractor-workflow/easybits_purchase_order_extractor_workflow.json" rel="noopener noreferrer"&gt;https://github.com/felix-sattler-easybits/n8n-workflows/blob/c38749a68fd6ea4ae6ebff41789d35cceaacdef1/easybits-purchase-order-extractor-workflow/easybits_purchase_order_extractor_workflow.json&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Anyone else automating document-to-sheet data entry? Curious how you're handling the messy multi-line rows – that was the trickiest part to get right.&lt;/p&gt;

&lt;p&gt;Best,&lt;br&gt;
Felix&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>opensource</category>
      <category>automation</category>
    </item>
    <item>
      <title>CV Slack Assistant in n8n – Drop a CV, Get a Structured Summary in Seconds [Workflow Template]</title>
      <dc:creator>Felix</dc:creator>
      <pubDate>Fri, 19 Jun 2026 07:30:54 +0000</pubDate>
      <link>https://dev.to/felix__s/cv-slack-assistant-in-n8n-drop-a-cv-get-a-structured-summary-in-seconds-workflow-template-4bc4</link>
      <guid>https://dev.to/felix__s/cv-slack-assistant-in-n8n-drop-a-cv-get-a-structured-summary-in-seconds-workflow-template-4bc4</guid>
      <description>&lt;p&gt;👋 Hey dev.to Community,&lt;/p&gt;

&lt;p&gt;You might remember Mike – friend of mine who runs a small company. Most of the automations I've built over the last months have been for him and his finance colleague Sarah (duplicate invoice detector, Slack approvals, invoice classification, the whole thing).&lt;/p&gt;

&lt;p&gt;This time it wasn't a finance problem. Mike called me last week because the company's going through a bigger hiring phase right now, and he has exactly one recruiter – let's call her Lisa – who's drowning.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The problem:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Lisa goes through dozens of CVs every day. The annoying part isn't reading them – it's that every single CV looks different. Different layouts, different sections, different orders. Some are PDFs, some are screenshots, some are exports from LinkedIn. Lisa already knows exactly what she cares about for the first-pass screen:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Last 3 roles&lt;/li&gt;
&lt;li&gt;Last 3 educations&lt;/li&gt;
&lt;li&gt;Top 3 skills&lt;/li&gt;
&lt;li&gt;Location&lt;/li&gt;
&lt;li&gt;Years of experience&lt;/li&gt;
&lt;li&gt;LinkedIn link (if she wants to dig deeper)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;But to extract those 6 things from a CV that's structured however the candidate felt like structuring it, she has to read the whole thing every time. Multiply by 30 a day. That's hours.&lt;/p&gt;

&lt;p&gt;Mike asked: "Can you build her something that just shows her those 6 things, in the same format, every time?"&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The build:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I wanted Lisa to be able to use this from where she already works – which is mostly Slack. So the flow ended up being:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Lisa drops a CV (PDF, PNG, or JPG) into a dedicated Slack channel&lt;/li&gt;
&lt;li&gt;Bot picks it up, runs it through the easybits Extractor with 8 structured fields&lt;/li&gt;
&lt;li&gt;Bot posts a clean summary back in the thread within ~5 seconds: name, location, years of experience, top 3 skills, last 3 roles with dates, education, salary expectations (if mentioned), LinkedIn &lt;/li&gt;
&lt;li&gt;Below the summary, an action card with two buttons: 💾 Save to Sheet or Dismiss &lt;/li&gt;
&lt;li&gt;Save → appends a row to a Google Sheet with all the fields split into discrete columns (sortable, filterable). Dismiss → just removes the card&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The Sheet is a placeholder for now – Mike's actually still in talks with different ATS providers, so once they pick one I'll just swap the Sheets node for whatever API the ATS exposes. Same workflow shape, different endpoint.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What ended up being harder than I expected:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I had to split this into two workflows. Workflow A handles the trigger and posts the summary + card. Workflow B catches button clicks from the card and does the Sheet append. Same pattern as the Slack invoice approval I shared a while back — Slack interactivity needs its own webhook endpoint, and you can't have both a trigger and a webhook listener in the same workflow without conflicts.&lt;/p&gt;

&lt;p&gt;The other annoying gotcha: the n8n Slack node has a bug right now where Block Kit payloads sometimes just don't render – you get the fallback text only ("Action menu") with no buttons. Worked around it by posting the action card via a direct HTTP call to chat.postMessage instead of using the Slack node. Documented this in the sticky notes so anyone running into it knows the fix.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why CV screening fits extraction so well:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The interesting thing here is that this is exactly the kind of task that has historically been done with custom CV parsers or expensive ATS resume-parsing add-ons. But once you treat a CV as just another structured document, the easybits Extractor handles it the same way it handles invoices or contracts. 8 fields, description per field, return null when not present – same pattern I've been using all year.&lt;/p&gt;

&lt;p&gt;The whole thing runs on the free plan since it's under 10 fields.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The templates:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Workflow A (lookup): &lt;a href="https://github.com/felix-sattler-easybits/n8n-workflows/blob/a8138f54ec6b225b7e90e2a66b4491c746767214/easybits-cv-slack-assistant/easybits_cv_slack_assistant_instant_summary.json" rel="noopener noreferrer"&gt;https://github.com/felix-sattler-easybits/n8n-workflows/blob/a8138f54ec6b225b7e90e2a66b4491c746767214/easybits-cv-slack-assistant/easybits_cv_slack_assistant_instant_summary.json&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Workflow B (save action): &lt;a href="https://github.com/felix-sattler-easybits/n8n-workflows/blob/a8138f54ec6b225b7e90e2a66b4491c746767214/easybits-cv-slack-assistant/easybits_cv_slack_assistant_save_to_sheet_and_card_actions.json" rel="noopener noreferrer"&gt;https://github.com/felix-sattler-easybits/n8n-workflows/blob/a8138f54ec6b225b7e90e2a66b4491c746767214/easybits-cv-slack-assistant/easybits_cv_slack_assistant_save_to_sheet_and_card_actions.json&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Sticky notes cover the full setup – Slack app config, scopes, credentials, Sheet schema. Both workflows together take about 20 min to wire up if you've done a Slack integration before.&lt;/p&gt;

&lt;p&gt;Curious if anyone else has built recruiter tooling in n8n – would love to hear what fields you found most useful, or if you've gone deeper into ATS integration than I have so far.&lt;/p&gt;

&lt;p&gt;Best,&lt;br&gt;
Felix&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>automation</category>
      <category>startup</category>
    </item>
    <item>
      <title>Built a batch business card scanner for my CEO – finally one that handles 20 cards in a single photo [Workflow Included]</title>
      <dc:creator>Felix</dc:creator>
      <pubDate>Fri, 05 Jun 2026 13:00:30 +0000</pubDate>
      <link>https://dev.to/felix__s/built-a-batch-business-card-scanner-for-my-ceo-finally-one-that-handles-20-cards-in-a-single-386c</link>
      <guid>https://dev.to/felix__s/built-a-batch-business-card-scanner-for-my-ceo-finally-one-that-handles-20-cards-in-a-single-386c</guid>
      <description>&lt;p&gt;👋 Hey dev.to Community,&lt;/p&gt;

&lt;p&gt;My CEO mentioned he’s got a few conferences coming up in the next weeks and he’s actually looking forward to them. There’s just one problem: every time he comes back from an event, he has a stack of business cards in his pocket and zero time to manually add them all to his phone. By the time he gets around to it, half the context is already gone – who was that founder we wanted to follow up with? Which one was the panel guy?&lt;/p&gt;

&lt;p&gt;So I went looking for a tool I could just hand him. Plenty of business card scanners exist. But every single one of them has the same baffling design choice: you have to photograph each card individually. One at a time. For 20 cards.&lt;/p&gt;

&lt;p&gt;That’s not really a scanner. That’s a slightly faster version of typing them in by hand.&lt;/p&gt;

&lt;p&gt;So I built him something better in n8n.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;📸 The setup&lt;/strong&gt;&lt;br&gt;
The flow is now this: he lays all the business cards out on a hotel desk, takes ONE photo, and sends it to a Telegram bot. That’s the whole input.&lt;/p&gt;

&lt;p&gt;What he gets back: every contact appended as a row in a Google Sheet, plus a separate vCard file for each new contact, sent right there in the Telegram chat. He taps a vCard on his iPhone → “Add Contact” → done. The whole thing takes about 15 seconds for 20 cards.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;🔍 The hard part: making batch extraction actually work&lt;/strong&gt;&lt;br&gt;
The reason every other scanner does one card at a time is that multi-card extraction is genuinely hard. Most OCR tools turn a photo of 20 cards into one giant blob of text and then you’re writing regex to figure out which phone number belongs to which person.&lt;/p&gt;

&lt;p&gt;I used the easybits Extractor for this because it returns structured JSON with each card as a separate object – so the workflow can just iterate. The prompt explicitly tells the model to treat each rectangular card as a distinct contact and to return null for any field it can’t read confidently (instead of hallucinating a plausible-looking phone number, which is the classic OCR failure mode).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;🚫 Then I added duplicate handling&lt;/strong&gt;&lt;br&gt;
The Google Sheet is the real unlock here. Before contacts go to his phone, the workflow checks the sheet for duplicates – matched by email, or name+company if no email is on the card. If he scanned someone last month at a different event, they don’t get re-added.&lt;/p&gt;

&lt;p&gt;So his phone stays clean and the sheet becomes a proper running database of every person he’s met. No more 5 versions of the same contact because he forgot he already had them.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;📦 What you need to set this up&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;An n8n instance (Cloud or self-hosted)&lt;/li&gt;
&lt;li&gt;A Telegram bot (free, takes 2 minutes via BotFather)&lt;/li&gt;
&lt;li&gt;A Google Sheet with the right column headers&lt;/li&gt;
&lt;li&gt;An easybits account at easybits.tech for the extractor – the free Sandbox tier covers what you need&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The &lt;a href="https://go.easybits.tech/bc-scanner" rel="noopener noreferrer"&gt;easybits Extractor&lt;/a&gt; is a verified n8n community node, so on n8n Cloud you just search 'easybits Extractor' in the node panel and it’s there. On self-hosted, install via Settings → Community Nodes with '@easybits/n8n-nodes-extractor'.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;📁 Workflow &amp;amp; setup guide&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;To the workflow:&lt;br&gt;
&lt;a href="https://n8n.io/workflows/15530-scan-business-cards-to-google-sheets-and-iphone-contacts-with-telegram-and-easybits/" rel="noopener noreferrer"&gt;https://n8n.io/workflows/15530-scan-business-cards-to-google-sheets-and-iphone-contacts-with-telegram-and-easybits/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The sticky notes inside the workflow walk through every node – what it does, how it’s configured, and why.&lt;/p&gt;

&lt;p&gt;Anyone else built something similar for handling event leads? Curious whether people are pushing contacts straight to a CRM (HubSpot, Pipedrive) or keeping it in a sheet. The Sheet to vCard pattern is nice because it works for everyone, but I imagine the CRM version would be even better for sales-heavy teams.&lt;/p&gt;

&lt;p&gt;Best,&lt;br&gt;
Felix&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>github</category>
      <category>startup</category>
    </item>
    <item>
      <title>Agentic vs. deterministic: I built the same n8n workflow both ways. The agent lost.</title>
      <dc:creator>Felix</dc:creator>
      <pubDate>Tue, 28 Apr 2026 13:20:48 +0000</pubDate>
      <link>https://dev.to/felix__s/agentic-vs-deterministic-i-built-the-same-n8n-workflow-both-ways-the-agent-lost-2apn</link>
      <guid>https://dev.to/felix__s/agentic-vs-deterministic-i-built-the-same-n8n-workflow-both-ways-the-agent-lost-2apn</guid>
      <description>&lt;p&gt;👋 Hey dev.to Community,&lt;/p&gt;

&lt;p&gt;A couple weeks back I shared a workflow that uses the easybits Extractor to classify uploaded invoices (PDF, PNG, JPG), route them to the right Google Drive folder, and flag low-confidence documents to Slack for review.&lt;/p&gt;

&lt;p&gt;A lot of comments came in asking the same thing: why not build this agentic?&lt;/p&gt;

&lt;p&gt;Fair question. So I built the same workflow again – this time with an AI Agent node, Gemini as the chat model, and seven tools hanging off it (six "move to folder" tools + one Slack alert). The agent sees the file ID, decides the category, and calls the matching tool.&lt;/p&gt;

&lt;p&gt;It works. But after building it, here are the four reasons I'm sticking with the deterministic version.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;🎲 Non-determinism where I don't want it&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Classification is a solved deterministic task. Adding an LLM in the middle means the same invoice can route differently on two runs. For a process that's supposed to be boring and reliable, that's a downgrade.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;🔍 Debuggability collapses when it fails&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;When the deterministic workflow breaks, an IF node either fires or it doesn't – I can tell you exactly why in 10 seconds. When the agent misroutes, I'm reading execution logs trying to reverse-engineer what the model was reasoning about. The tool calls are visible, sure, but the why behind a wrong call is a judgment about a black box.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;📊 You lose real confidence scoring&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The Extractor returns null when it genuinely can't extract a field – that's a clean signal I can branch on with a single IF node. An agent's self-reported confidence is vibes. It'll happily tell you it's 90% sure on something it got wrong.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;⚠️ More failure modes, zero capability gained&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Building this I hit tool loops, missing $fromAI parameters, schema mismatches, binary-passing issues between agent and tool nodes. Every one of those is a new thing that can break in production – and at the end, the output is the same file in the same folder.&lt;/p&gt;

&lt;p&gt;My take: agentic makes sense when you actually need reasoning – ambiguous decisions, multi-step planning, or work that genuinely can't be expressed as a graph. Invoice classification is none of those.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;📁 Both workflows if you want to compare:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Agentic version: &lt;a href="https://github.com/felix-sattler-easybits/n8n-workflows/blob/2e9153b83d94fb1200a130f2c3b10a21298ed49b/agentic-document-classification-workflow/agentic_document_classification_workflow.json" rel="noopener noreferrer"&gt;https://github.com/felix-sattler-easybits/n8n-workflows/blob/2e9153b83d94fb1200a130f2c3b10a21298ed49b/agentic-document-classification-workflow/agentic_document_classification_workflow.json&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Deterministic (easybits Extractor) version: &lt;a href="https://n8n.io/workflows/14960-classify-invoices-and-route-them-to-google-drive-with-easybits-and-slack/" rel="noopener noreferrer"&gt;https://n8n.io/workflows/14960-classify-invoices-and-route-them-to-google-drive-with-easybits-and-slack/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;⚙️ easybits Extractor setup (for the deterministic one):&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Cloud users: easybits Extractor is available – search in the node panel&lt;/p&gt;

&lt;p&gt;Self-hosted: Settings → Community Nodes → install '@easybits/n8n-nodes-extractor'&lt;/p&gt;

&lt;p&gt;Create a pipeline at extractor.easybits.tech with two fields: document_class and confidence_score&lt;/p&gt;

&lt;p&gt;Free tier covers 50 requests/month.&lt;/p&gt;

&lt;p&gt;For those of you running agents in n8n – where have they earned their keep for you, and where have you found yourself ripping them back out? Genuinely curious what the line looks like for other people.&lt;/p&gt;

&lt;p&gt;Best,&lt;br&gt;
Felix&lt;/p&gt;

</description>
      <category>ai</category>
      <category>agents</category>
      <category>beginners</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>We connected Claude to a self-hosted n8n instance via MCP and used it to co-build a 71-node production workflow. Here's the honest version.</title>
      <dc:creator>Felix</dc:creator>
      <pubDate>Wed, 15 Apr 2026 09:06:47 +0000</pubDate>
      <link>https://dev.to/felix__s/we-connected-claude-to-a-self-hosted-n8n-instance-via-mcp-and-used-it-to-co-build-a-71-node-g6p</link>
      <guid>https://dev.to/felix__s/we-connected-claude-to-a-self-hosted-n8n-instance-via-mcp-and-used-it-to-co-build-a-71-node-g6p</guid>
      <description>&lt;p&gt;👋 Hey dev.to Community&lt;/p&gt;

&lt;p&gt;A friend of mine was building an automation project for a multi-brand retail operation – taking messy supplier files and turning them into Oracle EBS-compatible records. 735 brands, 321,000+ barcodes, seven AI extraction pipelines. He'd connected Claude Opus to his self-hosted n8n instance through MCP and was building workflows by just talking to it. I wanted to see if this actually works, so we ran the remaining project phases together.&lt;/p&gt;

&lt;h2&gt;
  
  
  🛠️ What the setup looks like
&lt;/h2&gt;

&lt;p&gt;Through MCP, Claude can search workflows, read every node config, and execute workflows on the live n8n instance. But n8n is just one connector – it also talks to Google Drive, Chrome, and Slack. So in one conversation, Claude can read your workflow, pull a reference file from Drive, verify a live Sheet through Chrome, and message your team on Slack.&lt;/p&gt;

&lt;p&gt;Model choice matters. Opus consistently knows n8n-specific stuff – Code node vs Function node, Switch vs IF, expression syntax. Earlier models got the shape right but missed the details.&lt;/p&gt;

&lt;h2&gt;
  
  
  🏗️ What we built
&lt;/h2&gt;

&lt;p&gt;Over four phases: a 71-node production workflow with webhook trigger, file routing, PDF chunker, seven AI extraction pipelines (running through &lt;a href="https://go.easybits.tech/mcp-devto" rel="noopener noreferrer"&gt;easybits&lt;/a&gt;), merge/validation layers, Google Sheets integration across 10+ tabs, error handling, and dashboard refresh.&lt;/p&gt;

&lt;p&gt;The standout moments: Claude analyzed ~940,000 rows across two reference files and built a color-coded duplicate report with five matching categories. Later, it reverse-engineered how the data team manually converts 13-column supplier files into a 47-column EBS format – identified the mapping logic, handled that different brands use different column names (UPC vs INTERNATIONAL BARCODE vs EAN), and designed a four-step season resolution chain that became production logic. It found three fields we'd missed.&lt;/p&gt;

&lt;h2&gt;
  
  
  🐛 Where it saved the most time: debugging
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Stale schema.&lt;/strong&gt; Workflow wrote empty rows but showed "success." Claude read the node config through MCP and found the Sheets node had cached 31 columns with old names while the live sheet had 45 columns with new names. Mapped every discrepancy, gave step-by-step fix. Would've taken hours manually.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Phantom match.&lt;/strong&gt; Claude's own fuzzy matching used &lt;code&gt;string.includes("")&lt;/code&gt; – always true for empty strings. Every empty barcode matched against 321k records. Clean code, invisible bug. Found it once we described the symptom.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The one it couldn't solve.&lt;/strong&gt; Apps Script onChange trigger created a race condition during sheet wipes. Claude kept suggesting vanilla JS that doesn't apply to Apps Script. My friend solved it with a WIPE_IN_PROGRESS flag, taught Claude the pattern, and it applied it correctly going forward. Some domain stuff is still on you – but the learning compounds.&lt;/p&gt;

&lt;h2&gt;
  
  
  📊 The honest numbers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Simple workflows (webhook → transform → write): 40–50% work first try&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Complex multi-step with conditional logic: 15–20% work first try&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Time: 2–4 hours manually → 30–90 minutes with Claude&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The first-try rate is misleading. Even when it doesn't run immediately, the architecture is right. You're debugging details, not building from scratch.&lt;/p&gt;

&lt;h2&gt;
  
  
  💬 How prompting actually works
&lt;/h2&gt;

&lt;p&gt;Nobody types "build me a pipeline." Real prompt:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;"Look at the upload workflow. I need a sub-workflow that takes raw supplier files with 13 columns and maps them into our 47-column BSMS_ITEM_UPLOAD format. The January file is the reference."&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;~80% correct on first pass. The 20% was edge cases. Mental model: treat it like a senior dev on their first week. Technically strong, needs context about your specific setup.&lt;/p&gt;

&lt;h2&gt;
  
  
  ✅ Bottom line
&lt;/h2&gt;

&lt;p&gt;This isn't "AI builds n8n workflows." It's Claude operating across the full project – reading live configs, analyzing data, debugging multi-layer issues, writing stakeholder emails, building decks. All through MCP.&lt;/p&gt;

&lt;p&gt;Best description: a senior engineer who can read your systems and debug your configs, but needs you as the architect who signs off before anything touches production.&lt;/p&gt;

&lt;p&gt;Happy to answer questions about the setup or specific situations we ran into.&lt;/p&gt;

&lt;p&gt;Best,&lt;br&gt;
Felix&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>beginners</category>
      <category>automation</category>
    </item>
    <item>
      <title>How far can you push document extraction before it breaks? Here's the stress test workflow I built to find out.</title>
      <dc:creator>Felix</dc:creator>
      <pubDate>Fri, 10 Apr 2026 08:00:50 +0000</pubDate>
      <link>https://dev.to/felix__s/how-far-can-you-push-document-extraction-before-it-breaks-heres-the-stress-test-workflow-i-built-2f52</link>
      <guid>https://dev.to/felix__s/how-far-can-you-push-document-extraction-before-it-breaks-heres-the-stress-test-workflow-i-built-2f52</guid>
      <description>&lt;p&gt;👋 Hey everyone,&lt;/p&gt;

&lt;p&gt;As I shared in my last post, the easybits Extractor just got released as a &lt;a href="https://dev.to/felix__s/verified-n8n-community-node-easybits-extractor-the-easiest-way-to-set-up-data-extraction-in-n8n-f99"&gt;verified community node on n8n&lt;/a&gt;. With the setup now being faster than ever (auto-mapping + community node = about 2 minutes from zero to working extraction), I figured this is the perfect time to actually stress test the whole thing properly.&lt;/p&gt;

&lt;p&gt;A few of you also asked me after my last posts about extraction accuracy – how well does it really hold up when the document quality drops? Clean PDFs are easy. Every solution handles those. But what about scanned copies, coffee-stained paper, or documents covered in pen scribbles? I wanted to answer that with actual numbers instead of guessing.&lt;/p&gt;

&lt;p&gt;So I built a stress test workflow and I'm sharing it here so anyone can use it to benchmark their own extraction solution.&lt;/p&gt;

&lt;h2&gt;
  
  
  ⚙️ What the workflow does:
&lt;/h2&gt;

&lt;p&gt;You upload a document through a web form. The workflow extracts the data, compares every single field against the known correct values (ground truth), and shows you a results page with a per-field pass/fail breakdown and an overall accuracy percentage. Upload, wait a few seconds, see the score. That's the whole loop.&lt;/p&gt;

&lt;p&gt;No Code node needed – the entire validation is built with native n8n nodes and expressions.&lt;/p&gt;

&lt;h2&gt;
  
  
  📄 The test documents:
&lt;/h2&gt;

&lt;p&gt;I spent some time thinking about what actually makes a good stress test. Just degrading quality isn't enough – you also need to test whether the extraction actually reads the document or just memorises where fields tend to appear. So I put together 11 test versions of the same invoice:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Original – clean digital PDF. The baseline. Should be 100%.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Versions 1–7 – progressive degradation. It starts mild with v1 (slightly aged scan, barely noticeable) and gets worse step by step. By v4 you're looking at aged paper, coffee stains, and handwritten "Rec'd &amp;amp; OK" annotations. By v6, heavy coffee ring stains are sitting right on top of key fields. And v7 – "The Survivor" – has burn marks, pen scribbles ("WRONG ADDRESS? check billing!"), the amount due field circled and scribbled over, and half the document barely readable. If anything can extract data from that one, I'll be impressed.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;2 Layout Variants – same data, completely different visual structure. One uses a card-based layout with grouped sections, the other rearranges everything into a three-column format. These test whether the extraction actually understands the content or is just relying on positional patterns.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;1 Handwritten Version – this one came from community feedback. Someone asked how extraction handles handwriting, so I added a fully handwritten version of the same invoice to the test set.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;All test documents are available in my GitHub repo (link below), so you can use the exact same set to benchmark your own solution and compare results.&lt;/p&gt;

&lt;h2&gt;
  
  
  🚀 How I set it up:
&lt;/h2&gt;

&lt;p&gt;The extraction side took about 2 minutes – created a pipeline on &lt;a href="https://go.easybits.tech/st" rel="noopener noreferrer"&gt;easybits&lt;/a&gt;, used the auto-mapping feature to detect the fields, dropped the verified community node into the workflow, connected credentials, done. The rest is native n8n: a Set node holding the ground truth values, a Merge node to combine extracted and expected data, a Validation node with expressions comparing each field, and a Form completion screen that displays the results directly in the browser.&lt;/p&gt;

&lt;p&gt;I've already done a first test run with the original invoice – 100% accuracy across all 10 fields, as expected. I'll add a screenshot so you can see what the results page looks like.&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%2Fhylz6vanju2xx0yvli3j.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%2Fhylz6vanju2xx0yvli3j.png" alt="Stresstest Results" width="800" height="647"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;r/n8n - How far can you push document extraction before it breaks? Here's the stress test workflow I built to find out.&lt;/p&gt;

&lt;h2&gt;
  
  
  🔄 Want to test a different extraction solution?
&lt;/h2&gt;

&lt;p&gt;The workflow is designed to be solution-agnostic. You can swap out the easybits Extractor node for an HTTP Request node pointing at any other extraction API. As long as your response returns the same field names under json.data, the entire validation chain – ground truth comparison, per-field flagging, accuracy percentage, results page – works identically. So if you're evaluating multiple tools, you can benchmark them all using the exact same workflow and test documents.&lt;/p&gt;

&lt;h2&gt;
  
  
  ✨ What's coming next week:
&lt;/h2&gt;

&lt;p&gt;I'm going to run all 11 documents through the workflow and share a full results breakdown here – accuracy percentages for every single version, from the clean original all the way down to the destroyed one and the handwritten version. I'll also put together a short video walkthrough showing the workflow in action and how the results look across the different quality levels.&lt;/p&gt;

&lt;h2&gt;
  
  
  Links:
&lt;/h2&gt;

&lt;p&gt;Workflow JSON: &lt;a href="https://github.com/felix-sattler-easybits/n8n-workflows/blob/1cb44eceee6939343b076225aa9bfea900855a18/data-extraction-stresstest/stresstest_workflow_easybits_extractor.json" rel="noopener noreferrer"&gt;GitHub link&lt;/a&gt;&lt;br&gt;
Test documents: &lt;a href="https://github.com/felix-sattler-easybits/n8n-workflows/tree/1cb44eceee6939343b076225aa9bfea900855a18/data-extraction-stresstest" rel="noopener noreferrer"&gt;GitHub repo&lt;/a&gt;&lt;br&gt;
easybits Extractor community node: &lt;a href="https://extractor.easybits.tech/documentation/integration" rel="noopener noreferrer"&gt;Integration guide&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Would love to hear if anyone runs the test with a different extraction solution – curious how the results compare. And if you have ideas for even nastier test documents, I'm all ears.&lt;/p&gt;

&lt;p&gt;Best,&lt;br&gt;
Felix&lt;/p&gt;

</description>
      <category>ai</category>
      <category>testing</category>
      <category>productivity</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>[Verified n8n Community Node] easybits Extractor – The easiest way to set up data extraction in n8n (no code, set up in minutes)</title>
      <dc:creator>Felix</dc:creator>
      <pubDate>Wed, 08 Apr 2026 16:24:57 +0000</pubDate>
      <link>https://dev.to/felix__s/verified-n8n-community-node-easybits-extractor-the-easiest-way-to-set-up-data-extraction-in-n8n-f99</link>
      <guid>https://dev.to/felix__s/verified-n8n-community-node-easybits-extractor-the-easiest-way-to-set-up-data-extraction-in-n8n-f99</guid>
      <description>&lt;p&gt;👋 Hey Everyone!&lt;/p&gt;

&lt;p&gt;If you've ever built a document processing pipeline in n8n, you probably know the exact headache we've been dealing with for the last year:&lt;/p&gt;

&lt;p&gt;You use a standard OCR node, it dumps a massive wall of raw text, and you spend hours writing custom Code nodes filled with fragile Regex just to find the "Total Amount" on an invoice. Or, you try to use heavy cloud tools like AWS Textract, and you get bogged down in complex setups and unpredictable token pricing.&lt;/p&gt;

&lt;p&gt;We got tired of our workflows breaking every time a vendor changed their invoice layout, so we built a dedicated data extraction platform specifically for n8n workflows and just released our &lt;em&gt;official verified community node&lt;/em&gt;.&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%2Fq4ye2kqi5apzdbfvyr2u.jpg" 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%2Fq4ye2kqi5apzdbfvyr2u.jpg" alt="easybits' Extractor Verified Community Node" width="800" height="214"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  🛠️ What it does
&lt;/h2&gt;

&lt;p&gt;It essentially acts as a pre-processor for your document pipelines. You feed it a binary file (PDFs, invoices, receipts, etc.), and it returns reliable, structured JSON output matching the exact schema you define. No AI hallucinations breaking your downstream nodes, and zero post-processing required.&lt;/p&gt;

&lt;h2&gt;
  
  
  ✨ Key Features for Builders
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Simple Setup:&lt;/strong&gt; If you're on n8n Cloud, just search for "easybits Extractor" in the node panel – it's available out of the box, no installation needed. Self-hosted users: go to Settings → Community Nodes → Install and enter &lt;code&gt;@easybits/n8n-nodes-extractor&lt;/code&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Binary In, Clean JSON Out:&lt;/strong&gt; Replaces massive, fragile Code nodes. The node reads binary file attachments directly from any upstream node – a Telegram Trigger, Gmail Trigger, n8n Form with file upload, or an HTTP Request that fetches a document. You define your schema once on our platform, and we return the exact structured data you need under json.data.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Per-Field Prompting:&lt;/strong&gt; Instead of one generic prompt for the whole document, you write a specific description for each data point you want to extract. This gives the model precise instructions per field – like telling it exactly what "billing period" means on your invoices versus guessing from context. The more specific your field descriptions, the more accurate your results.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Transparent Pricing:&lt;/strong&gt; 1 request = 1 request. No complex token conversion math, and no guessing what your pipeline will cost. Our free plan includes 50 API requests per month – enough to build and test your workflows before committing.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Zero Maintenance:&lt;/strong&gt; We handle all the AI model updates in the background. If a vendor completely changes their invoice layout, your n8n workflow keeps running without you needing to fix anything.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  🚀 How to get started
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;n8n Cloud:&lt;/strong&gt; Search for "easybits Extractor" in the node panel – it's ready to use immediately.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Self-hosted:&lt;/strong&gt; Go to Settings → Community Nodes → Install → enter &lt;code&gt;@easybits/n8n-nodes-extractor&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Set up your extraction schema for free at &lt;a href="https://go.easybits.tech/cn" rel="noopener noreferrer"&gt;easybits.tech&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Drop the node into your canvas and connect it to any node that outputs a file!&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For more details on configuration options and input types, check out our &lt;a href="https://extractor.easybits.tech/documentation/integration" rel="noopener noreferrer"&gt;n8n integration guide&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  🛑 Put your current setup to the test
&lt;/h2&gt;

&lt;p&gt;We've been running this in production for a while now, and we're confident it holds up – but we'd love for you to challenge it. If you have a gnarly, multi-page document that keeps breaking your current extraction setup, run it through easybits and see how it compares.&lt;/p&gt;

&lt;p&gt;Let us know what you think, what features you'd like to see next, or if you run into any edge cases.&lt;/p&gt;

&lt;p&gt;Happy building!&lt;br&gt;
Felix&lt;/p&gt;

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