---
title: "Querying and analyzing data"
description: "Ask questions in plain language and Indent writes read-only queries, returns downloadable results and charts, and writes up findings."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.indent.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Querying and analyzing data

Indent works as a data analyst for your team: it explores the schema, writes the query, runs it
read-only, and presents the results — no SQL from you.

## Query and explore

Connect a database from [**Settings → Integrations**](https://app.indent.com/settings/integrations).
Indent supports PostgreSQL, BigQuery, and ClickHouse. Databases are always organization-scoped. See
[Connecting your database](/connecting/databases).

Once a database is connected, ask a question in plain language. Indent searches the schema, inspects
tables, writes the query, and runs it read-only — it never writes to your database. If a column name
is off or a join doesn't match, Indent corrects itself and reruns. Results appear inline alongside
the SQL that produced them, and you can download them as CSV.

Ask follow-up questions against the same data, refine the query, or pivot to a different table in
the same session.

## Charts and reports

Indent generates charts inline when a result is clearer as a visualization — bar charts, line
charts, and stacked bar charts.

Indent also writes up a full analysis from the data it queried. Ask for a case study on a customer's
product usage and Indent produces a written summary with key stats, quotes, and supporting charts,
all from the same session.

## Start from Slack

Mention `@indent` in a Slack channel and ask a data question directly:

```
@indent How many organizations signed up last week, broken down by day?
```

Indent runs the queries and replies in the thread. See
[Working with Indent in Slack](/collaborating/working-in-slack).

## Move analysis into code

When an investigation surfaces a bug, the same session can continue into a code fix. Indent already
has the context — the queries, the data, the root cause — so it can move into the codebase and open
a pull request. See [Writing code](/working-with-indent/writing-code).

Source: https://docs.indent.com/working-with-indent/querying-data/index.mdx