Create and Reuse Prompt Templates

When to Use a Template

Create a prompt template when the same request works well and you expect to run it again. Good templates include recurring reports, inbox triage, account research, content briefs, meeting preparation, and support follow-up drafts.

Do the first version manually with your Super Agent or a focused agent. Save it only after the output, tool access, approval rules, and format are clear enough for another teammate to reuse.

Write the Reusable Prompt

Start with the goal, source material, expected output, and any connected apps the agent should use. Include the audience, deadline, tone, and approval rule when those details affect the result.

Replace changing details with obvious placeholders such as customer name, date range, account owner, source link, or destination channel. Keep the stable instructions in the template so users only fill in what changes from run to run.

Save the Template

After a successful run, save the request as a reusable prompt template from the prompt or template controls in your workspace. Use a name that describes the outcome, not the underlying tool.

Add a short description that explains when to use it and what information the user must provide. If the template depends on Gmail, Slack, Linear, Stripe, or another app, mention that dependency in the description.

Test Before Sharing

Run the saved template with a small, realistic example. Confirm the agent asks for missing required inputs, uses the right tools, respects approval rules, and returns the expected format.

Open the trace, the step-by-step run log, if the result is inconsistent. Update the template with the missing context, stricter formatting, or a clearer fallback question, then rerun the same test.

Reuse and Maintain Templates

Use the template whenever the same workflow comes up. Fill in only the placeholders or changed context, then review the result before approving any external message or record update.

Update templates when the process, connected app, output format, or owner changes. Archive templates your team no longer uses so the library stays easy to scan.

When a template runs reliably on a predictable cadence, turn it into a scheduled job so the work can run automatically with the same instructions.

Related Guides

Read "Schedule Recurring Tasks and Automations" when a proven template should run on a schedule or app trigger.

Read "Connect Apps and Tools to Your Agents" before creating templates that depend on connected business systems.

Read "Read an Agent Trace" when you need to debug tool access, missing inputs, or inconsistent template output.