Skip to content

Document Templates

The Document Template tab (under System Configuration) is where you define reusable document templates that automations generate documents from. You give Nexa a title, a prompt, and a source file; Nexa converts the file into a typesetting template you can then configure, publish, and promote across environments. Authoring happens in the dev environment.

  1. Open System Configuration → Document Template and select ADD.

  2. In the Add Document Template panel, enter a Title and a Prompt describing what the document should produce.

  3. Upload a source document under Upload Document — only PDF, DOC, and DOCX files are accepted.

  4. Select Save. Nexa saves the template and starts generating its Typst content (the internal typesetting representation of your document).

Field Required Notes
Title Yes Display name for the template.
Prompt Yes Instructions describing the document to generate.
Upload Document Yes Source file; PDF, DOC, or DOCX only.

Each template carries a status:

  • Draft — created, not yet published. Editable.
  • Active — published; its content is locked.

Which actions appear depends on the template’s status and whether generated Typst content exists.

Action When available What it does
Edit Title Draft Rename the template.
Configure Template Content generated Opens the template configuration screen to map and adjust the layout.
Workflow Log Always Streams the generation workflow log for the template.
Publish Draft with content Locks the content and marks the template Active. This is irreversible.
Promote to next env Published (has a published slug) Opens a pull request that copies the template to the next environment.
Clone Active Creates an editable copy of the template.
Delete Draft Removes the template. Cannot be undone.

Promoting a published template opens a pull request in the nexa-workflow-automations repository that copies templates/<slug>/ from the current environment’s branch to the next environment’s branch. Nothing is overwritten until you review and merge that PR on GitHub. See Environments for the dev → test → prod flow and GitHub Integration for the underlying connection.