Skip to main content
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

ComponentDescription
QueryRun a query against a data source using your ontology metrics and dimensions
SearchSearch a knowledge base for relevant documents or passages
LookupFind a specific entity across your data sources

​
Logic components

ComponentDescription
ConditionBranch the workflow based on a true/false check (e.g. “if revenue > threshold”)
LoopRepeat a set of steps for each item in a list (e.g. for each overdue invoice)
FilterNarrow down a dataset before passing it to the next step
TransformReshape or format data between steps

​
Action components

ComponentDescription
Send emailDeliver formatted content to one or more recipients
Post to SlackSend a message to a Slack channel or user
WebhookCall an external URL with a payload
Update recordWrite back to a connected data source
Run skillExecute 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)