Playbook components

Playbooks are built from components — modular pieces that you connect into a workflow. Each component type handles a different part of the automation.

Data components

Component	Description
Query	Run a query against a data source using your ontology metrics and dimensions
Search	Search a knowledge base for relevant documents or passages
Lookup	Find a specific entity across your data sources

Logic components

Component	Description
Condition	Branch the workflow based on a true/false check (e.g. “if revenue > threshold”)
Loop	Repeat a set of steps for each item in a list (e.g. for each overdue invoice)
Filter	Narrow down a dataset before passing it to the next step
Transform	Reshape or format data between steps

Action components

Component	Description
Send email	Deliver formatted content to one or more recipients
Post to Slack	Send a message to a Slack channel or user
Webhook	Call an external URL with a payload
Update record	Write back to a connected data source
Run skill	Execute an agent skill as part of the workflow

How components connect

Components are arranged in sequence. Each component receives the output of the previous step and passes its own output forward. Branching components (like Condition) create parallel paths that can merge back together downstream.

Trigger
  → Query (get overdue invoices)
    → Loop (for each invoice)
      → Condition (is amount > $10,000?)
        → Yes: Send email to account manager
        → No: Post to Slack channel
    → Transform (summarize results)
      → Send email (weekly summary to leadership)

Overview

Data Platform

Ontology

Agent Space

Playbooks

Playbook components

Data components

Logic components

Action components

How components connect

​Data components

​Logic components

​Action components

​How components connect

Data components

Logic components

Action components

How components connect