Looking for 1 more real workflow case from another n8n team

Help me Build my Workflow
, ,
1

I’ve now tested 2 anonymized workflow cases locally:

  • voucher validation
  • invoice extraction / strict schema validation

Both were useful.

Now I’m looking for 1 more real case, ideally from a different workflow or team, to see whether this kind of boundary is useful beyond those first examples.

What I’m testing is very narrow:
should the workflow continue downstream, or should it stop safely here?

Good examples would be things like:

  • classification / routing
  • compliance / policy checks
  • document extraction
  • anything where bad structured output creates real downstream cost

What I need:

  • 1 sample payload
  • 1 target schema
  • 1 short note on what breaks downstream if it passes incorrectly
  • polling or webhook preference

What I can return:

  • whether the run ended in succeeded or failed_safe
  • a short reason if relevant
  • a receipt reference

This is not broad onboarding and not a product pitch.
I just want one more real case from another workflow/team.

Public kit:

If sharing the full payload is hard, a short outline first is fine.
Reply here or DM me.

2

One useful case is invoice extraction before ERP/AP routing.

Example incoming payload:

{
  "file_url": "https://example.com/invoice_4821.pdf",
  "vendor_hint": "ABC Supplies",
  "received_at": "2026-06-01T10:15:00Z"
}

Target schema:

{
  "vendor_name": "string",
  "tax_id": "string|null",
  "document_date": "YYYY-MM-DD",
  "currency": "ISO_4217",
  "line_items": [
    {
      "item_description": "string",
      "quantity": "number",
      "unit_price": "number",
      "total_price": "number"
    }
  ],
  "subtotal": "number",
  "tax_amount": "number",
  "total_amount": "number"
}

Downstream risk if wrong:

  • wrong vendor routes the invoice to the wrong AP workflow

  • wrong currency or total creates bad approval/payment data

  • missing line items breaks reconciliation

  • subtotal + tax not matching total means the workflow should stop, not continue

For this kind of case, I’d want the boundary to return either:

completed

or:

failed_safe

with a reason like:

schema_invalid
totals_mismatch
missing_required_field
low_confidence_vendor

Polling is fine for this type of workflow because invoice extraction is not usually latency-critical. The important part is that the downstream ERP/AP step only runs after the schema and math checks pass.

1 Like