Collectors

Decides which metrics get collected on which conversations (the config form of a collector). Its metrics: list references both custom metrics you defined and Roark’s system metrics, all by slug.

# yaml-language-server: $schema=https://roark.ai/roark-config.schema.json
kind: collector
name: consent-on-frontdesk
modality: call
status: ACTIVE
metrics:
  - consent_collection_consent_obtained
  - refund_policy_accuracy
filters:
  - conditions:
      - type: AGENT
        key: frontdesk
        operator: EQUALS

name is the slug config identity. displayName (optional) is the collector’s name as it appears in Roark, where spaces and capitals are allowed; it defaults to name. Set it to a collector’s exact existing name to bring one you created in the app under config (apply takes it over instead of creating a duplicate), for example displayName: "Credit Card Apr" with name: credit-card-apr.
modality is call or chat and is immutable once created (make a new collector to switch).
Metrics are referenced by their stable slug, not a UUID, and must be visible to the project and support the collector’s modality.
Filters are condition groups: groups OR together, conditions within a group AND. An AGENT condition’s key is a config-managed agent name (resolved on apply); every other type (CALL_SOURCE, CALL_PROPERTY, INTEGRATION) uses its key/value verbatim. Omit filters to score every matching conversation.

For the full field reference of every kind, see the Config DSL reference schema.

Getting Started

Simulations

Observability

Metrics

Config as Code

Autoimprove

Recipes

Integrations

Enterprise

SDKs & Developer Tools

Resources