Skip to main content
Indent can work as a data analyst for your team — querying your databases, investigating discrepancies, building charts, and writing up findings. Ask a question in plain English and Indent handles the schema exploration, query writing, and presentation. Best with: Databases. Add Slack when the work starts in a team thread.

Querying and exploration

Connect your databases — PostgreSQL, BigQuery, Snowflake, and others — from the Database Access page. Once connected, you can ask questions in plain English. Indent searches the schema, inspects tables, writes the query, and presents the results. If something goes wrong — a column name is off, a join doesn’t match — Indent corrects itself and reruns. You can ask follow-up questions against the same data, refine the query, or pivot to a different table without starting a new session. Results are displayed inline alongside the SQL that produced them, and you can download them as CSV.

Visualizations and reports

When the results are better understood as a chart, Indent can generate visualizations inline — bar charts, line charts, stacked comparisons, and more. This is useful for usage trends, growth metrics, or anything you’d otherwise pull into a spreadsheet to graph. You can also ask Indent to write up a full report or analysis from the data it’s queried. For example, asking for a case study on a customer’s product usage will produce a written summary with key stats, pull quotes, and supporting charts — all from the same session.

Kick it off from Slack

Mention @indent in any Slack channel and ask a data question directly. Indent picks it up, runs the queries, and responds in the thread. This is especially useful for ad-hoc requests from teammates who don’t want to context-switch into another tool — they ask in Slack, and the answer shows up in Slack.

From analysis to code

When an investigation surfaces a bug or a gap in application logic, the same session can continue into a code fix. Because Indent already has the context — the queries, the data, the root cause — it can move straight into the codebase and open a pull request. See Code for how that flow works.