Hex
Connect Hex and your assistant can turn your dashboards into insights — search your Hex projects, run an analysis by asking a question, and bring the results into your briefs, docs, and replies — so the numbers that live in Hex show up where you actually work.
Everything runs as you: analyses run only against the Hex projects and data connections your Hex role already allows.
What’s included
With Hex connected, your assistant can:
- Search your projects — find the right Hex project for a question
- Run an analysis — start a Hex Thread to ask a data question in plain English
- Follow up — continue a Thread with more questions in the same context
- Read the results — pull the analysis results back as text and numbers
Connecting Hex
- Go to Integrations
- Find Hex and click Connect
- Authorize Town in Hex (sign in when prompted)
- Return to Town
Town connects through Hex’s official MCP server (app.hex.tech/mcp) in one click — no API keys or setup. On the Hex side, this requires a Team or Enterprise workspace and an Explorer role or higher. Analyses run only against the data connections your Hex role already allows.
What your assistant can do
| Capability | What it does | Makes changes? |
|---|---|---|
| Search projects | Find a Hex project by name or topic | No |
| Start an analysis Thread | Ask a data question — Hex runs the analysis | Runs an analysis |
| Continue a Thread | Ask follow-ups in the same Thread | Runs an analysis |
| Read Thread results | Read the messages and results of a Thread | No |
Hex Threads are the same ask-a-question flow you’d use in Hex, with approval rules on running them. Your assistant doesn’t edit your existing projects, notebooks, or dashboards, and it returns analysis results as text and numbers — not chart image exports.
Use cases
Data in your meeting prep
Walk into calls with the numbers:
- Before a customer meeting, pull their usage picture from Hex — seats, activity, adoption
- Add what changed since last time to your brief
Watch the metrics
Catch shifts early:
- Run your watchlist each morning and flag what moved
- Get the “why” attached, not just the number
Ask your data anything
Skip opening a notebook:
- “How many workspaces activated last week?” — a Hex analysis, started and summarized for you
- “Send the team last week’s retention numbers” — pulled from Hex, delivered to Slack or email
Owed updates and docs
Turn analysis into an artifact:
- “Draft the weekly metrics update” — pulled from Hex, written in your voice
- “Turn the growth analysis into two paragraphs for the board doc”
Example routine
A routine that preps customer calls with real usage data:
Before each customer meeting:
1. Search Hex for the customer's usage project
2. Start a Thread to pull their seats, activity, and adoption
3. Compare with the last time we met
4. Send me a brief an hour ahead with what changedBest practices
Analyses take a moment. Running a Thread kicks off a real analysis in Hex — it may take time to finish before results come back. Give routines room for that.
Point to the right project. If a question is ambiguous, name the project or metric so your assistant runs the analysis you mean.
Results are numbers, not charts. Hex returns analysis results as text and numbers your assistant can summarize — it doesn’t export the chart image itself.
Troubleshooting
Can’t connect
- Confirm your Hex workspace is Team or Enterprise with an Explorer role or higher
- Make sure you’re signing in to the correct Hex workspace
Can’t find a project
- Verify the project exists and your Hex role can access it
- Try searching by topic or metric instead of the exact project name
An analysis returns nothing or errors
- The question may need a specific project — name it and try again
- Confirm the underlying data connection is available to your Hex role
- Give the analysis time to finish; complex questions run longer
Related
- Integrations overview — How integrations give your assistant context
- Context and memory — How your assistant remembers and reuses what it learns
Town