Agiled Docs

Worker templates are preconfigured starting points for common AI worker jobs.

Use templates when the job is close to a known pattern. Use a custom worker when the process, context, or tool permissions are unique to your team.

Templates speed up setup, but they do not replace review. The generated worker still needs to match your records, terminology, permissions, and approval rules.

Create From a Template

Open AI Workers.
Select Worker Templates.
Review each template's description.
Check its prompt context and callable tool categories.
Select Use template.
Review the generated worker in the editor.
Adjust instructions, context, tools, status, and max iterations before using it.

Start in draft. A template should not become active until you have checked the generated worker against your workspace records, permissions, and review process.

Review Before Saving

Templates are a starting point, not a final approval. Always confirm the worker has only the context and tools needed for the job.

Review instructions line by line and remove anything that does not match your workspace. Check whether the template assumes certain fields, statuses, modules, or integrations.

Also check the intended reviewer. If the template produces advice that affects customers, money, HRM, contracts, or record updates, decide who must approve the output before the worker is used broadly.

Context and Tools

Each template shows:

Prompt context, which controls the workspace data included in the prompt.
Callable tools, which controls what the worker can call while running.

Keep the starting permission set narrow. A template that works for one team may include context or tools your workspace does not need. Remove broad context sources and write tools until the worker has passed a small test.

Remove Assumptions

Templates can assume common statuses, fields, or review steps. Replace those assumptions with your workspace's actual record names, approval process, and safe-stop rules before enabling the worker.

Keep The First Run Narrow

Use the smallest useful record set for the first run. A single stale ticket, overdue invoice, draft task, or test contact is enough to prove whether the template understands your workspace. Broad context should come later, after the worker has produced useful output and the reviewer knows how to stop it.

If the template suggests customer-facing messages, payments, HRM decisions, or record updates, keep approval required until those suggestions have been reviewed in real runs.

Test Before Enabling

Run the worker on one safe record or narrow context. Review the output, tool usage, and run detail before enabling broad usage or scheduled automation.

Compare the output with the source record. If the worker missed important context, guessed at missing data, or recommended unsafe next steps, revise the instructions or remove tool access before running it again.

Keep the worker inactive until a reviewer confirms the first test output is useful, accurate, and limited to the intended job.

Template Fit Checklist

Before using a template, confirm:

The job matches the template's purpose.
The prompt uses record names your team recognizes.
Context sources are necessary.
Tool access is no broader than needed.
The reviewer is clear.
The first test uses safe data.

When to Use Custom Instead

Use a custom worker when the template assumes the wrong record type, status model, tone, approval process, or tool access. It is better to start custom than to keep editing a template until the original purpose is no longer recognizable.

Use Worker Templates