Skip to main content

Use published templates

Published templates can be assigned to AI Employees or selected directly in workflows. The worker uses the template’s description and instructions to determine whether it fits the task and how source information should be mapped.

Before you delegate work

Confirm that:
  • The template is published.
  • Its description clearly distinguishes it from similar templates.
  • Required fields and source information are documented.
  • The worker has access to the template and permitted source material.
  • A reviewer is responsible for the generated document.

Assign a template to a worker

1

Open the worker

From Workforce, select the worker that will use the template.
2

Open Templates in the skill tree

Review available and already assigned templates.
3

Assign the template

Add only templates relevant to the worker’s role. Too many similar choices can make selection less reliable.
4

Test a representative request

Provide realistic source material and confirm that the worker chooses and populates the intended template.

Delegate document work

A useful delegation includes four parts: The worker can then gather permitted source information, select an assigned template, populate the document, and return the result.
Do not assume missing information. Require the worker to ask a question, apply an approved default, or mark the field for review.

Use a template in a workflow

Use the Populate Template block when the template is part of a repeatable process.
1

Add the block

Add Populate Template at the point where the document should be created.
2

Select a published template

Choose the exact template instead of relying on dynamic selection.
3

Connect source values

Map validated data from earlier steps, uploaded files, or approved connected applications.
4

Handle the output

Send the generated file to a review step, save it to an approved location, or pass it to the next workflow block.
5

Test failure paths

Verify behavior when a required value is missing, a file cannot be read, or generation fails.

Supported source material

Depending on the worker’s assigned capabilities and permissions, source information can come from:
  • Uploaded documents and images
  • Forms, spreadsheets, and CSV files
  • Connected inboxes and message threads
  • Document Stores
  • Earlier workflow steps
  • Approved connected business applications
Access remains controlled by the worker’s assignments and security policies.

Review generated documents

Before approving or distributing a document, check:
  • The correct template and version were used.
  • Names, dates, amounts, identifiers, and addresses match the source.
  • Required fields are complete.
  • Optional and conditional sections appear correctly.
  • Formatting and page layout are intact.
  • No unsupported facts were added.
  • The output satisfies the process owner’s review criteria.

Improve unreliable output

If results are inconsistent:
  1. Make the template description more specific.
  2. Clarify field instructions and formatting requirements.
  3. Reduce overlap with similar assigned templates.
  4. Improve the delegation and source material.
  5. Add validation before template population.
  6. Retest each conditional path.

PDF templates

Configure fixed-layout forms and field instructions.

DOCX templates

Configure variables, conditions, loops, and equations in Word documents.