Repository navigation
Add an n8n invoice workflow with binary PDF and error paths - #87
Merged
Merged
Conversation
krflol
marked this pull request as ready for review
October 9, 2026 00:42
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automation users can POST invoice JSON to an imported n8n workflow and receive a styled PDF attachment. The downloadable local Compose kit includes the renderer, editable HTML/CSS, licensed fonts, and a client. The workflow uses built-in nodes and separates successful binary PDFs, validation errors, and unavailable-service errors.
The private renderer shares the bounded Fullbleed 2.5.20 invoice handler with the Lambda starter. n8n and Python images are pinned by digest. This is a local integration example; production authentication, durable jobs, output storage and delivery remain application responsibilities.
Validation: the exact ZIP passes actual n8n import/publish, HTTP workflow execution, browser editor checks, independent PDF content/geometry/raster checks, pagination, decimal totals, literal markup, concurrent data isolation, rejected input, renderer unavailability, and recovery. CI PDFs match the public-wheel Windows baseline. Container and volume cleanup is checked. The strict docs build and desktop/mobile ZIP, standalone JSON and sample PDF checks pass. No n8n marketplace approval, hosted delivery, or production-capacity claim is made.