Cells

Workflows use a notebook-style editor where each query is composed of cells. Cells let you mix executable code with documentation, making your workflows easier to understand and maintain.

Cell types

Code cells

Code cells contain SQL that executes against your data sources. Each code cell is part of a query and contributes to the query's result. You can split a complex query across multiple code cells within the same query for readability.

-- Example: a code cell querying transaction data
SELECT
  customer_id,
  transaction_date,
  amount,
  store_location
FROM sales.transactions
WHERE transaction_date >= {{start_date}}

Text cells

Text cells contain markdown-formatted notes and documentation. They do not execute - they exist to explain what the surrounding code does, document assumptions, or provide context for other team members.

Text cells are useful for:

• Explaining the purpose of a query
• Documenting business logic or data assumptions
• Adding notes about data quality or known issues
• Providing instructions for parameter values

AI assistant

Press Ctrl+I (or Cmd+I on Mac) in a code cell to open the AI assistant. The assistant can help you write SQL by describing what you want in plain language. It is aware of your available data layers and can generate queries, suggest transformations, or help debug issues.

Working with cells

• Add cells - insert new code or text cells at any position within a query
• Reorder cells - drag cells to change their position
• Delete cells - remove cells you no longer need

Using parameters in code cells

Code cells can reference workflow parameters using double-brace syntax:

SELECT *
FROM sales.transactions
WHERE region = {{region}}
  AND transaction_date BETWEEN {{start_date}} AND {{end_date}}

When the workflow runs, parameter values are substituted into the query.