Skip to main content
Config Workflows are Traceport’s visual flow builder for designing how your AI requests are processed, routed, and handled. Instead of hardcoding provider logic in your application, you define it visually as a graph of connected nodes.

​
What Are Config Workflows?

Each Config Workflow is a versioned, publishable flow that defines:
  • How incoming requests are routed to different AI providers
  • What plugins run before or after model calls (e.g., PII detection, content moderation)
  • What branching logic determines the next step based on model output
  • How fallbacks and retries are handled when providers fail
Think of Config Workflows as programmable middleware for your AI requests — defined visually, versioned automatically, and deployed without code changes.

​
Example: Email Job Listings

Here’s a real Config Workflow that processes job application emails: This workflow:
  1. fetch_gmail (Plugin) — Fetches incoming emails
  2. cv_scorer (Router) — Routes the email to an AI model for CV scoring
  3. score_route (Branch) — Branches based on the score:
    • score > 7 → Send intro invite + check Calendly slots + update calendar
    • score < 7 → Put on hold
    • no CV → Request missing documents
  4. Various Plugin nodes execute the final actions (send mail, update Calendly, etc.)

​
Node Types

Config Workflows support several node types. See the Nodes Reference for full details.

Router

Routes requests to AI models. Configure the provider, model, and prompts.

Branch

Conditional logic with IF / ELSE IF / DEFAULT paths based on expressions evaluated against node outputs.

Plugin

Execute actions like PII detection, content moderation, API calls, email sending, and more.

​
Getting Started

1

Create a Config

Navigate to Configs in the sidebar and click Create New Config.
2

Design Your Flow

Add nodes to the canvas by clicking the + button. Connect nodes by dragging edges between them.
3

Configure Nodes

Click any node to open its settings panel. Set routing targets, branch conditions, or plugin configurations.
4

Publish

Click Publish to make the version active. Published versions handle live traffic.

Nodes Reference →

Learn about all available node types — Router, Branch, and Plugin.