AI Ticket Tagger & Prioritizer workflow blueprint

Inputs for the Ticket Tagger & Prioritizer workflow

Provide the following information when starting this workflow. Required inputs are validated before the first workflow stage runs.

• Ticket Text

  Required

  Support ticket content

  Type: String

• Customer Tier

  Optional

  Customer tier (free, pro, enterprise)

  Type: String

Input template

This request shape is generated from the blueprint's input schema. Angle-bracket values are placeholders; defaults and examples appear only when the source blueprint defines them.

{
  "ticket_text": "<required string>",
  "customer_tier": "<optional string>"
}

How the Ticket Tagger & Prioritizer AI workflow works

This support blueprint uses a dag workflow with 2 agents, 0 functions, and 0 MCP servers. This catalog blueprint is available by request; contact GraphN to discuss access and customization for your use case.

1. 1

   Ticket Classifier

   Agent using Ticket Classifier

2. 2

   Priority Scorer

   Agent using Priority Scorer

Blueprint resources and prerequisites

These are the actual agents, functions, and MCP servers declared by the blueprint. If an MCP server connects to an external system, configure the required connection and credentials in your GraphN workspace before running the workflow.

Workflow output contract

The completed workflow makes the following output available to downstream steps, applications, or API clients: