# Automate PDF documents with nodulz

Source: https://nodulz.com/use-cases/document-generation

Language: en

> Editorial summary. Check the source page for current prices, availability and live data.

Receive a business event, retrieve its data, generate a PDF and archive it before sending it by email.

## The day-to-day need.

Confirmations and reports are often assembled manually: find the information, fill a template, export the document, then store and send it.

## Example: an order confirmation

A confirmed order triggers the workflow with its ID. Nodulz retrieves its items from PostgreSQL, generates the PDF confirmation, stores it in your S3 bucket and prepares the customer email.

## Without a workflow

The team reads the order, fills a template, exports a PDF, stores it and prepares an email.

## With nodulz

The order ID connects the source data, PDF generation, archiving and send request in one path.

## How nodulz solves the problem.

nodulz keeps the business record as the common thread. The document is generated from retrieved data, then the same file passes to the archive and email steps.

### Load the right record

The webhook receives an order ID. A PostgreSQL query retrieves the required details; the triggering event does not need to contain the entire record.

### Compose a document from data

The PDF node uses your template and workflow expressions to display contact details and order items. Content, layout and file name remain configurable.

### Reuse the same file

Amazon S3 archives the PDF under an order-related key. The Email node attaches that document; an archive failure should be handled before proceeding according to your rules.

## From trigger to outcome.

Webhook · PostgreSQL · PDF · Amazon S3 · Email

## What this workflow brings.

Generation, archiving and sending share one visible path. You can inspect the data used to assemble each document.

- A document generated from the record’s data.

- The same PDF for the archive and attachment.

- A processing path tied to the order ID.

## Keep control of the process.

Your template, file name and recipients remain under your control. Protect the webhook and choose a bucket access policy suited to the document’s data.

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)