Skip to main content

Overview

Router actions are backend-defined and fetched by Bud admin from /routers/actions. The response provides action categories, parameter definitions, output definitions, icons, colors, descriptions, and validation metadata.

Action Metadata

Each action includes metadata similar to:
FieldDescription
typeStable action type used in router steps
nameHuman-readable action label
descriptionExplanation shown in the editor
iconOptional icon for action cards
colorOptional display color
paramsParameter schema rendered in the configuration panel
outputsOutput names available to downstream configuration

Supported Parameter Types

The router editor supports a broad set of parameter renderers:
TypePurpose
string, number, booleanBasic scalar fields
select, multiselectFixed or dynamic option lists
json, templateStructured configuration and templated values
rangeNumeric range controls
model_ref, cluster_ref, project_refBud resource references
endpoint_ref, endpoint_ref_listSingle or multiple endpoint references
endpoint_weighted_listWeighted endpoint routing configuration
endpoint_ordered_listOrdered fallback endpoint configuration
provider_ref, credential_ref, cloud_model_refProvider-backed integrations
branchesDecision branch configuration
content_rule_list, string_listRule and list inputs

Router DAG API Shape

When saving a router, the UI converts editor steps into dag_config:
{
  "name": "support-routing-router",
  "description": "Routes support prompts to the best endpoint",
  "entry_step": "step_signal",
  "steps": [
    {
      "step_id": "step_decision",
      "action_type": "decision_rules",
      "name": "Choose Route",
      "params": {},
      "conditions": [],
      "depends_on": [],
      "next_steps": ["step_algorithm"]
    }
  ],
  "parameters": [],
  "outputs": {}
}

Router Resource Fields

FieldDescription
idRouter identifier
project_idOwning project identifier
nameRouter name used by the UI and API snippets
descriptionRouter summary
tagsOptional colored labels
iconDisplay icon
dag_configRouter graph configuration
statusdraft, active, or inactive
step_countNumber of configured steps
created_atCreation timestamp
modified_atLast modification timestamp

Validation

Action parameters can be validated through /routers/actions/validate. Bud admin also performs client-side checks for required fields, empty arrays in required list parameters, ranges, string lengths, patterns, and conditional field visibility.