Guides
Get your first win in 10 minutes
Connect one tool, let HiveBase build your Brain, and get a real, sourced result — fast.
You don't need to configure anything elaborate to feel what HiveBase does. Connect a single source, and within minutes you'll have a searchable company Brain and your first agent-drafted result — every claim traceable to where it came from.
The 10-minute path
Connect one tool you already live in (Slack, Gmail, or your meetings). That's enough for HiveBase to build context and show you a real result. Add the rest later.
- 01Connect one tool~2 min · read-only
- 02Brain builds claimsTyped + sourced
- 03Ask a real questionGet a cited answer
- 04First task runsDrafted, held for approval
- 01
Connect one tool
~2 min · read-only
- 02
Brain builds claims
Typed + sourced
- 03
Ask a real question
Get a cited answer
- 04
First task runs
Drafted, held for approval
The 10-minute path at a glance
Four moves, none of them setup-heavy. Here's where the time goes and what you walk away with.
| Step | Time | What you do | What you get |
|---|---|---|---|
| 1. Connect | ~2 min | Authorize one tool, read-only | A live signal source |
| 2. Brain builds | ~3–5 min | Nothing — it reads history for you | Typed, sourced claims |
| 3. Ask | ~1 min | Ask a question in plain language | A cited answer, not a link dump |
| 4. First task | ~1 min | Review what it drafted | An agent result, held for approval |
1. Connect your first source
Open Integrations
From the app, go to Settings → Integrations and pick one source. Slack, Gmail, or a meeting recorder give HiveBase the most signal fastest.
Authorize read access
HiveBase requests read access first. Nothing is written back to your tools until you explicitly turn that on later.
Let the Brain build
HiveBase reads recent history and extracts typed claims — accounts, decisions, people, dates — with a source link on every one. This takes a few minutes.
Not sure which to connect?
Pick the tool where your team actually talks. Slack lights up the Brain fastest; meetings add the richest context per signal; Gmail is best if customers live in your inbox. You can't pick wrong — start with one and add the rest from Connect your tools.
2. Ask the Brain something real
Once the Brain has context, ask it a question you'd normally dig through tools to answer. Try one of these:
| You ask | What you get back |
|---|---|
| "What changed with Acme this week?" | A sourced summary of recent signals, with links |
| "What did we decide about pricing?" | The decision, who made it, and when — with evidence |
| "What's blocking the launch?" | Open risks pulled from messages, docs, and meetings |
Every answer cites its sources. If two sources disagree, HiveBase holds the contradiction for review instead of guessing.
3. Watch your first task run
HiveBase doesn't just answer — it acts. When it spots something actionable (a churn risk, a follow-up, a draft worth writing), it creates a task and starts it.
You stay in control
Agent work that changes something outside HiveBase — sending an email, pushing code, updating a CRM — pauses for your approval. See Trust & safety for exactly what's reversible and what asks first.
Connect over MCP instead?
If you'd rather drive HiveBase from Claude, Cursor, or your own agent, you can connect over MCP in well under five minutes:
claude mcp add hivebase --transport http https://mcp.hivebase.ai/{
"mcpServers": {
"hivebase": { "url": "https://mcp.hivebase.ai/" }
}
}See the Developer quickstart for the full walkthrough.
You're in. What's next
Connect the rest of your stack
Add GitHub, Linear, your CRM, and more so the Brain sees your whole company.
Invite your team
Bring teammates in so everyone shares the same context.
See how the Brain works
Understand typed claims, provenance, and why every answer is sourced.
Set your safety net
Decide what agents can do on their own and what always asks first.
First governed run
Draft → approval → receipt — once, end to end.
Google Workspace
Gmail, Calendar, and Drive setup when email is your signal.