Printing records to PDF

Turn a record into a branded PDF — an invoice, a quote, a work order, a certificate. You design a template once against a table, then any record in that table can be rendered from it: downloaded, saved onto the record as an attachment, or generated and emailed automatically by an automation. A template is a stack of blocks Templates are built from a handful of blocks, in the order you want them on the page: • Header — your logo and organisation name from account branding, with meta rows on the right (invoice number, dates). • Title and Text — free wording that can carry {{record.fieldKey}} tokens, plus {{record.name}}, {{workspace.name}} and {{today}}. • Field rows — a label and a value, straight off the record. • Line items — a table of the records that link to this one, with the columns and number formats you pick. • Totals — the money at the bottom, with one row emphasised. A token you spell wrong renders as nothing rather than printing raw braces onto a customer's invoice. Line items come from your relations The line-items block walks the same link as subitems: a Relation field on the child table pointing back at this record. Point an invoice at its line items, or a job at its visits, and the rows appear in the order they were created. Values print the way they read in the app — a Relation shows the customer's name rather than an id, and a Rollup shows its computed total — so a PDF never leaks the plumbing underneath. Getting the PDF out From a record you can download it, or save it onto the record in an attachment field, where it behaves exactly like a file someone dragged in. An automation can do both without anyone pressing anything: add a Generate a PDF step, choose the template, and either save it to a field, email it to {{record.email}}, or both. That is the difference between "we can make invoices" and "invoices send themselves when the job is marked done". What it looks like The PDF wears your brand, not RowFold's — the logo, organisation name and accent colour come from account branding, and there is no RowFold marking anywhere on the page. Paper size is A4 or Letter per template. The designer previews the real thing: it renders an actual PDF from a real record rather than an HTML impression of one, so what you approve is what your customer receives. Tips • Preview against a record that has line items and a filled-in address — an empty record makes every layout look fine. • Give the emphasised totals row to the number people actually look for: the amount due, not the subtotal. • PDFs are made fresh each time, so correcting a typo on the record fixes every future copy — but not one already saved as an attachment or already emailed. Good to know • A template belongs to one table. It cannot render a record from another table, and the picker only offers templates that fit. • A deleted table's templates go to Trash with it and come back when it is restored. An automation still pointing at a template that has been deleted fails with a named error in its run history rather than silently doing nothing. • Attachment fields cap at 10 files and 10 MB each — a long PDF saved repeatedly will eventually fill the field. • Line items are capped at 300 rows per PDF; past that, a PDF is the wrong tool and a report is the right one. Who can do what • Anyone who can see a record can make a PDF from it; saving one onto the record also needs permission to edit that attachment field. • Only workspace Admins can create or edit templates, because a template decides which fields end up in front of a customer. • A field hidden from you prints as a dash rather than its value, so a PDF keeps its shape and the gap is visible.