Integrations
Asana
betaConnect Asana to map authorized workspaces, then stamp projects to watch. Connect, watch, Brain, and writeback are separate gates.
Asana is a keep-your-board plug-in beside the Linear beachhead: connect, then confirm which projects to watch before monitoring. Connecting completes OAuth and maps access you authorized — it does not by itself mean full project sync, Brain seeding, or two-way writeback.
| Stage | What it means |
|---|---|
| Connect | OAuth succeeds; HiveBase can see authorized workspaces. |
| Watch | You confirm (stamp) specific projects via Update; HiveBase monitors those for task activity. |
| Brain | Indexing into the Brain is separate from connect — not automatic solely because OAuth completed. |
| Writeback | Creating or updating Asana tasks from HiveBase follows certification and your trust & safety approval model. |
How monitoring works
After you connect and stamp projects, Asana task events for watched containers can flow into HiveBase via webhooks (deduplicated). Outbound writes, when enabled, pass an approval gate.
What each stage does
| Stage | What moves |
|---|---|
| Connect | Authorized workspace mapping via OAuth. |
| Watch | Task created/updated events, assignee changes, custom fields, attachments, and comments for stamped projects — via webhooks, deduplicated. |
| Brain | Not implied by connect alone; indexing is a separate gate. |
| Writeback | Sparse task fields — only after live certification, then approval-gated (propose-first). Not implied by connect or Stamp. |
Key features
Real-time watch (after confirm)
Asana webhooks for confirmed projects — created/updated, assignee changes, custom fields, attachments, and comments — are received and deduplicated.
Connect ≠ Brain
Connecting Asana does not claim an automatic full Brain seed. Watching projects and any Brain indexing are gated separately.
Fail-closed writeback
Writeback stays dark until certified. When a certified path is enabled, HiveBase can create/update supported fields under your approval settings.
Propose-first outbound
Outbound changes follow your autonomy settings (propose-first; earn auto per action class) before they reach Asana.
Connecting Asana to HiveBase
Connect Asana from your workspace settings. Credentials are stored per company.
Open Data Sources
In HiveBase, go to Settings → Integrations → Data Sources.
Connect Asana
Find Asana and click Connect Asana to start the OAuth flow.
Authorize with Asana
You'll be redirected to Asana's OAuth consent screen. Review the access HiveBase requests and approve to grant access.
Confirm projects to watch
You're returned with Asana connected. Use Update to select the projects HiveBase should watch. Connect does not mean full sync, automatic Brain indexing, or live writeback.
Credentials are scoped per company
Asana credentials are stored per company, so the connection applies to your workspace — not to an individual user across workspaces.
Watching and writeback
- Inbound (watch). After you confirm projects, task events arrive as webhooks and are deduplicated. That is monitoring — not a claim that the whole workspace is synced or indexed into Brain.
- Outbound (writeback). Fail-closed until a path is
live_certified. When enabled, HiveBase writes supported fields back to Asana under your approval model (propose-first).
Certified write paths may use create-only, update-only, or create-or-update strategies depending on the work. Treat that as the ceiling, not a claim that every strategy is live today.
Outbound changes are fail-closed, then approval-gated
Writeback is not live from connect or Stamp. When a certified path is enabled, outbound changes follow your autonomy settings — review the trust & safety guide.
Disconnecting Asana
You can disconnect Asana from the same place you connected it.
Open Data Sources
Go to Settings → Integrations → Data Sources in HiveBase.
Disconnect Asana
Find the Asana connection and disconnect it. HiveBase stops receiving Asana task events and stops writing changes back to Asana. Your stored credentials for the connection are removed.
FAQ
Does connecting Asana start two-way sync?
No. Connect maps authorized access. You still confirm projects to watch. Writeback is separate and approval-gated — not implied by OAuth alone.
Does connect seed the Brain?
No. Connect does not mean automatic Brain indexing. Watching confirmed projects and any Brain indexing are separate gates.
Which fields does HiveBase write back to Asana?
Only on a live-certified write path: title, description, status, priority, due date, assignees, and project. That is the ceiling — not a claim every field is live today.
Will HiveBase change tasks in Asana without my say-so?
Writeback stays fail-closed until certified. When enabled, it follows your autonomy settings (propose-first). See the trust & safety guide.
Are credentials shared across my whole company?
Credentials are stored per company, so the connection is scoped to your workspace.