How to Automate PDF Generation From Notion

{/ synced-from-notion — do not edit manually /}

Need to turn Notion records into finished documents without copying each field by hand? You can automate PDF generation from Notion by linking a database to a template, then choosing when each file should be made. We’ll walk through the setup with PDFOutput, including field mapping, review steps, and batch runs.

Step 1: Choose a Notion Database and Identify the Documents to Automate

Goal: Start with a database that holds the details your document needs. Each row should represent one document, such as a quote, inspection report, contract, or certificate.

Pick a repeated document with a stable layout. If staff already type the same details into a file for every new client, order, or inspection, that process is a good place to start. A one-off letter that changes every time may not need automation.

Review the document and list each changing value. An invoice might need an invoice number, client name, issue date, line items, and amount. A safety report might need an inspection date, site, findings, and reviewer. Add a Notion property for each value you want to place in the output.

Keep property names clear and consistent. Names such as Client_Name and Invoice_Amount are easy to match to template fields. Keep dates as date properties and totals as number or formula properties when that fits your data.

If details live in separate databases, link them with a relation. A relation connects one record to another. A rollup brings a value from the related record into the main database, such as a client address or a sum of line items. Notion databases organize records and properties.

Before building the workflow, check a few sample records. Fill in the fields you expect to use, and confirm linked data appears where it should. If every document needs a different set of facts, first decide whether you need separate databases or a shared one with clear document types.

> 📌 Key Takeaway: Start with one recurring document and one well-filled record. A small test makes field and layout issues easier to spot.

Step 2: Prepare a Document Template and Match Notion Properties

Goal: Set the page layout once, then leave clear spaces for the values that change by record.

PDFOutput accepts a Google Document, Word file, existing PDF, or Notion page as a template. Choose the format that suits the document you already use. A fixed letterhead may work well as a PDF template. A report with sections you expect to edit may be easier to maintain as a document.

Add a placeholder wherever a Notion value should appear. Write each one with double curly brackets, like {{Client_Name}} or {{Invoice_Amount}}. The placeholder name must match the related Notion property. Spaces, underscores, and capital letters matter, so copy the property name rather than typing it from memory.

Think through the page as a reader will. Put the document title near the top. Keep the date and reference number easy to find. For invoices or orders with related line items, leave room for those rows to appear. A long customer name or address can change the way a line wraps, so test with a record that has fuller details.

You can use relations and rollups when a document needs data from connected databases. For example, an order record might link to a supplier and a list of products. Check that those linked databases are connected for the workflow, then confirm the related values appear in the preview.

For multi-page files, check page breaks and footers as well as the first page. Use a sample with a longer description or several line items. The point is to catch layout problems before staff rely on the generated file.


When the fields are ready, connect the Notion database and template in PDFOutput. Map each property to its matching placeholder, then preview one record. For more detail on turning Notion records into files, see How to Convert Notion to PDF Automatically.

Step 3: Connect PDFOutput and Choose How Documents Will Be Generated

Goal: Link the source database to the template and choose a trigger your team can follow.

In PDFOutput, create a new connection and grant access to the Notion page that contains your database. Select the database you prepared, then add the chosen template. Next, choose the primary database record that will supply the fields for the document.

Map the properties to their placeholders. Set the file name using a property that identifies the record, such as an invoice number or report title. Choose where the generated file should be stored. PDFOutput can place files back in the Notion database and can also save them to a selected Google Drive folder.

Now choose how generation starts. Use a database button when a person should review a record and create its file on demand. Use the GeneratePDF status property when a team works from a queue. Mark the approved row Ready to Generate, and PDFOutput processes that record.

PDFOutput also supports these status choices:

• Generate Page: turn the Notion page into a PDF.
• Generate PDF and Doc: create a PDF and Google Document.
• Generate E-Signed Doc: create an e-signed PDF in the database workflow.
• Preview: create a Google Document preview before making the final PDF.

Pick a trigger that matches the work. A button is useful when a staff member approves each customer-facing file. A status change gives the team a visible ready queue. Scheduled runs can suit recurring work, such as reports that need to be generated on a set cadence. Keep a human review step if the file must be checked before it leaves your team.

Some teams build a custom workflow through an API. That route needs technical work, but a no-code setup avoids writing that integration yourself.

Step 4: Test the Workflow and Generate PDFs in Batches

Goal: Check a real output before you process a queue or a full set of records.

Run a preview with one complete record. Compare the resulting file with the source row. Check the person or company name, dates, amount, page breaks, and any related line items. Confirm that the filename makes sense and that the file appears in the place your team expects.

Then test an edge case. Use a longer name, a blank optional field, or a record with several related items. If the output has an empty placeholder, check spelling and capitalization first. If a related value is absent, check that the relation is set and the linked database is available to the workflow.

Watch this setup walkthrough before you test your own template:

Once the single-record test passes, try a small group before processing a larger set. PDFOutput supports batch generation, with batches of up to 100 PDFs in the referenced workflow. Check several files from the batch, not only the first one. A correct first result does not prove every record has complete data.

Bulk mail-merge is useful when each row needs its own copy of the same document layout. For example, a school can prepare certificates from student records, while a property team can generate reports from inspection entries. Each output uses the values from its matching Notion record.

If your team needs an editable file as well as a PDF, select the PDF and Google Document output option. PDFOutput can also create PPTX files. Word files are supported as template inputs, while the available generated formats include PDF, Google Docs, and PPTX.

Keep the batch step deliberate. Run it only after the relevant records are approved and the template has passed its checks.

Step 5: Make the Notion-to-Document Workflow Reliable

Goal: Make it clear who can start generation, what counts as ready, and where the result belongs.

Set a simple path for each record. For example, staff add the details, a reviewer checks the row, then the reviewer changes the status to Ready to Generate. That small pause helps prevent draft figures or incomplete terms from becoming a finished customer document.

Use clear status names and keep the output field easy to find. After generation, check that the record shows completion and that the file is attached in the right place. If the team stores a copy in Google Drive, use a folder structure people already understand, such as one folder per document type or work period.

Choose the trigger based on the work rhythm. A button fits one-off files created during a review or handoff. A status trigger works when staff move many records through the same approval queue. A scheduled trigger can help with repeat reports, but review the records it will include before setting it to run.

Set access with care. A document workflow may include client, staff, student, or supplier details. Give the connection access only to the pages and databases needed for the task, and check who can view the generated files in both Notion and the chosen storage folder.


When an output looks wrong, trace it from the source record to the template. First check whether the property has a value. Then compare the property name with the placeholder. If the field is correct, inspect relations, rollups, and the layout itself. For connection issues, technical teams can investigate the integration.

For signed files, decide who adds the signature and when. PDFOutput supports e-signed documents in the Notion workflow. Read the guide to adding e-signatures to PDFs generated in Notion before setting up that part of your process.

> 💡 Pro Tip: Keep one test record with long text and several related items. Use it after template edits to check that layout changes haven’t shifted key fields.

FAQ

Can I generate a PDF automatically when a Notion record is ready?

Yes. After you set up the connection, use PDFOutput’s GeneratePDF property and mark the record Ready to Generate. You can also use a database button for on-demand generation. Test the trigger on one record first, then use the same workflow for other approved records.

Can I use a Word file as my template?

Yes. PDFOutput accepts Word files, Google Documents, existing PDFs, and Notion pages as templates. Add placeholders in double curly brackets and match each placeholder to a Notion property. The generated file can be a PDF, Google Document, or PPTX.

Can PDFOutput create documents from more than one Notion database?

Yes. You can use relations and rollups to bring information from connected databases into the document. Connect the related databases and check that the main record points to the right linked rows. Then preview an example with related details before generating a batch.

Can I generate PDFs for many Notion records at once?

Yes. PDFOutput supports batch PDF generation. The referenced workflow handles batches of up to 100 PDFs at a time. Before a large run, confirm that records are ready and test a sample from the same set, especially if fields or related line items vary.

When should I use a button instead of a status trigger?

Use a button when a person should choose the moment a specific file gets made, such as after checking an inspection report. Use a status trigger when the team moves records through a shared queue. In both cases, define an approval point before generating a file that will be sent outside your team.

Conclusion

Start with one recurring document, one complete Notion record, and a matching template. Connect them in PDFOutput, preview the result, then add the trigger that fits your team’s approval process. Once that first workflow works, test a small batch before using it across the database.