Document Categorizer Agent
Deprecated. This agent has been superseded by the Categorizer agent, which accepts documents and any other input type via named inputs. Existing workflows using Document Categorizer continue to work, but new workflows should use the Categorizer instead.
The Document Categorizer agent classifies documents into predefined categories based on their content. It analyzes the document text and assigns the most appropriate category from your configured list.
Use Cases
- A document-processing workflow needs to route documents to different handling paths based on type (e.g., invoices, contracts, reports).
- You want to auto-tag incoming documents for downstream processing.
- You need to triage a document inbox by content type.
Inputs
| Input | Type | Description |
|---|---|---|
documents | Documents | One or more documents to categorize. |
text_input | Text (optional) | Supplemental text to consider alongside the documents. Useful when metadata or extracted fields should influence categorization. |
At least one of documents or text_input must be provided.
Outputs
| Output | Type | Description |
|---|---|---|
category | Category | The assigned category name. |
Each category produces a branch edge on the GWE canvas.
Configurations
| Parameter | Description | Default |
|---|---|---|
| Categories | List of category definitions with names and descriptions. | Required |
| Fallback category | Category assigned when no category matches with sufficient confidence. Set to "Fallback" and cannot be changed once set. | Required |
| Qualification criteria | Deterministic rules for categories. Requires a JSON Extractor agent connected upstream. | None |
How to Use This Agent
Route incoming documents to the correct processing pipeline:
document_trigger -> document_categorizer
-> [invoice] -> extract_entities -> accounting_workflow
-> [contract] -> extract_entities -> legal_review
-> [report] -> document_synthesis -> respond
-> [other] -> human_collaborationMigrating to Categorizer
The Categorizer agent replaces Document Categorizer with broader input support. To migrate:
- Replace the Document Categorizer node with a Categorizer node.
- Wire your document source to the Categorizer's named inputs.
- Re-create your category list and fallback category.
- Test the workflow to verify classification behavior is preserved.
Related Agents
- Categorizer -- the recommended replacement. Accepts any input type via named inputs.
- Text Categorizer -- for plain text classification.
- Thread Categorizer -- for support ticket thread classification.