Deprecated Agents

The following agents have been superseded by newer implementations. They remain available for backward compatibility but should not be used in new workflows. When you open a workflow containing a deprecated agent, a yellow warning banner appears on the agent node.

Migration Guide

Deprecated AgentReplacementNotes
Intent ClassifierCategorize Conversations and RouteRenamed and enhanced with example query matching, multi-intent detection, and human collaboration. Existing workflows continue to work.
External Tool CallerIntelligent ActionsRenamed and expanded to support 200+ integrations. Existing workflows continue to work.
Text Categorizer (v0)CategorizerThe Categorizer (v1) accepts any input type via named inputs, not just text. Existing Text Categorizer workflows continue to work.
Document CategorizerCategorizerThe Categorizer accepts documents via named inputs alongside other data. Existing Document Categorizer workflows continue to work.
search/v0Knowledge SearchThe v0 search action is deprecated. Migrate to the current Knowledge Search agent.
respond_with_sources/v0Respond using Search ResultsThe v0 respond action is deprecated. Use the current Respond using Search Results agent.
combine_search_results/v0Combine Search ResultsMigrate to the current version.
combine_text_with_sources/v0Combine TextMigrate to the current version.
fixed_response/v0Fixed ResponseMigrate to the current version.
custom_agent/v0Custom AgentMigrate to the current version.
generate_document/v0Generate DocumentMigrate to the current version.
rule_validation_with_documents/v0Rule ValidationMigrate to the current version.
json_mapper/v0JSON ExtractorMigrate to the current version.
general_hitl/v0Human CollaborationMigrate to the current version.

Identifying Deprecated Agents in Existing Workflows

When editing a workflow that contains a deprecated agent, the GWE canvas displays a yellow warning banner on the agent node: "You are using an agent version that is deprecated." The validation system also flags deprecated agents during pre-deploy checks.

To migrate:

  1. Note the deprecated agent's input and output bindings.
  2. Replace the action with the recommended replacement from the table above.
  3. Rewire the inputs and outputs -- the replacement agents typically accept the same or similar bindings.
  4. Test the workflow to verify behavior is preserved.

For additional detail on deprecated action versions and migration patterns, see the internal agent reference supplement.

Last updated: Jul 3, 2026