Overview
Agent Template suggestions in the AI Agents area are now generated by the Agents 2.0 engine. The result: templates more closely aligned with each pipe's context, higher execution capability, and less manual configuration to get a working agent up and running.
What's new?

- Agent Template suggestions are now powered by the Agents 2.0 engine
- Each template comes pre-configured as an Agent 2.0 — users only need to map specific fields and set triggers to activate
How does this help?
- Faster time to first active agent: pre-configured templates reduce setup effort
- Suggestions matched to the pipe's context: the engine reads the pipe's taxonomy and returns up to 6 relevant templates
Use cases
- Automatic triage in HR processes: an admin creates an onboarding pipe and receives a suggested agent that classifies incoming documents by type and routes them to the correct stage — no manual automation rules needed
- SLA monitoring in IT/ITSM operations: the agent suggested for a service desk pipe tracks open cards and triggers alerts or reassignments when deadlines are at risk
- Data validation in Procurement: admin of a purchase request pipe activates an agent that checks required fields and flags inconsistencies before a card moves to approval
- Summarization and categorization in legal processes: suggested agent for a contracts pipe extracts key information from attachments and auto-fills structured fields, reducing manual work for the team
- Intelligent routing in Customer Success: account management pipe receives a suggested agent that classifies requests by urgency and customer profile, directing them to the right owner without human intervention
Most relevant for
- Pipe admins setting up a new process who want to activate AI without starting from scratch
- Process operators in HR, Procurement, IT, and CS already using pipes but not yet exploring AI Agents
- Teams who experimented with AI Automations and want to evolve to agentic capability without reconfiguring everything manually
Plans and availability
Available for external customers on pipes with taxonomy configured.


