> ## Documentation Index
> Fetch the complete documentation index at: https://docs.traceport.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Config Workflows

> Build visual routing flows with plugins, routers, branches, and fallback logic.

**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.

<Frame>
  <video autoPlay loop muted playsInline src="https://mintcdn.com/traceport/ZXBNThc7kv_3RvjA/images/configs.mp4?fit=max&auto=format&n=ZXBNThc7kv_3RvjA&q=85&s=4e59cbd9e2de51d0ce4559840a2d6ab0" className="w-full rounded-lg" data-path="images/configs.mp4" />
</Frame>

## 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

<Info>
  Think of Config Workflows as programmable middleware for your AI requests — defined visually, versioned automatically, and deployed without code changes.
</Info>

## 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](/config-workflows/nodes) for full details.

<CardGroup cols={3}>
  <Card title="Router" icon="route">
    Routes requests to AI models.  Configure the provider, model, and prompts.
  </Card>

  <Card title="Branch" icon="code-branch">
    Conditional logic with IF / ELSE IF / DEFAULT paths based on expressions evaluated against node outputs.
  </Card>

  <Card title="Plugin" icon="plug">
    Execute actions like PII detection, content moderation, API calls, email sending, and more.
  </Card>
</CardGroup>

## Getting Started

<Steps>
  <Step title="Create a Config">
    Navigate to **Configs** in the sidebar and click **Create New Config**.
  </Step>

  <Step title="Design Your Flow">
    Add nodes to the canvas by clicking the **+** button. Connect nodes by dragging edges between them.
  </Step>

  <Step title="Configure Nodes">
    Click any node to open its settings panel. Set routing targets, branch conditions, or plugin configurations.
  </Step>

  <Step title="Publish">
    Click **Publish** to make the version active. Published versions handle live traffic.
  </Step>
</Steps>

<Card title="Nodes Reference →" icon="shapes" href="/config-workflows/nodes" horizontal>
  Learn about all available node types — Router, Branch, and Plugin.
</Card>