Skip to content

:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.

832 B
Raw Blame

SQL in an analysis

When the deliverable is a notebook, build the analysis in it as you go, not after. Create the notebook first with a title and the question, then add each query that a reported number depends on as a SQL cell (notebooks-add-cell with cell_type: 'sql'). A finished run returns the columns and a row preview, while a run that is still going returns only its status: wait for the result, and read it before you write the prose that interprets it.{throwaway_checks}

{fix_in_place}

  • Don't retype a cell's result as a markdown table. The cell already shows the table; the prose says what it means.
  • To chart a result, set visualization on the SQL cell. Don't save a separate SQL insight for a chart that lives in the notebook; save an insight only when the user wants it outside the notebook. {run_later}