Identify where a prompt template is used across your org. When you view references for a template, you can see the flows, agents, and other components that depend on that template.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, and Unlimited Editions with the Einstein for Platform, or Einstein or Agentforce for Sales or Service add-on, or Agentforce Foundations |
Prompt templates are foundational building blocks that power multiple features and automations across your org. A single template can be referenced in multiple flows, agents, or custom code. Without visibility into these dependencies, updating or deleting a template can accidentally break downstream integrations and disrupt critical business processes.
Template References adds important guardrails so you can:
- Understand impact before changes: See everywhere a template is used before you modify, deactivate, or delete the template.
- Prevent breaking changes: Identify dependencies that break if you remove a template.
- Manage the template lifecycle safely: Understand which templates are actively used versus deprecated.
- Plan template updates: Know which dependent components need updates when you change a template's response format.
Key Concepts
Active Templates and Reference Restrictions
- You can't delete a template version that's currently in use and has active references.
- You can't change the response format of an active template if the template has existing references.
- To update a response format, first remove or update all existing references.
References can include:
- Flows: Flows using the Prompt Template action.
- Agents: Agents and subagents referencing the template.
- Other integrations: Other components using the template.
Template references are automatically displayed in these scenarios:
- Attempting to delete a template: A references modal shows current references before you can delete the template.
- Attempting to deactivate a template version: A references modal shows current active references before you can deactivate the template version.
- Modifying a template response format: A warning appears if the template has existing references.
- Viewing template dependencies: Some orgs have additional views to see template usage across the org.
- View Template References
Use Template References to identify where a prompt template is used and safely remove those dependencies before making changes. - Remove a Template Reference in a Flow
Remove dependencies on a prompt template so you can safely delete or modify the template without breaking other components. - Remove a Template Reference in an Agent
Remove dependencies on a prompt template so you can safely delete or modify the template without breaking other components. - Remove a Template Reference in an Apex Class
Remove dependencies on a prompt template so you can safely delete or modify the template without breaking other components.