Output file naming
Templates can define an output filename pattern so generated files follow a consistent naming rule. Built-in tokens are {template}, {id}, {date}, {timestamp}; reference any template field by its stable id (e.g. {vendor_name}).
Last updated
Templates can define an output filename pattern so generated files follow a consistent naming rule. Built-in tokens are {template}, {id}, {date}, {timestamp}; you can also reference any template field by its stable id (e.g. {vendor_name}).
What you need
- A template
How patterns work
The pattern is a string with {token} placeholders. At autofill time, each placeholder is replaced with the resolved value.
The four built-in tokens:
{template}— the template's name{id}— the case identifier{date}— today's date (YYYY-MM-DD){timestamp}— full Unix-millisecond timestamp
Plus any of this template's field IDs as a token. The field ID is the stable snake-case key the field stores under — usually a lowercased version of the display name with underscores. A field named Vendor Name has the ID vendor_name, so the token is {vendor_name}. Spaces and capitalization in the original display name don't carry over: {Vendor Name} won't resolve.
Step by step
- Open the template.
- Click Settings in the template studio.
- Find Output filename pattern.
- Enter a pattern. For example:
{vendor_name}-invoice-{invoice_number}.pdf - Click Save.