Integrations.
Three live providers. Operator-triggered imports. Continuous monitoring once the data is in. Here's exactly what Mijoro reads, when, and what it does with it.
The integration model
Mijoro uses an import-only architecture. You connect a provider, you trigger an import, the data lands in your Asset Vault. From that moment on, the platform reads it continuously — flagging signals, updating your knowledge layer, feeding every artifact going forward. Re-imports happen when you trigger them, not on a hidden schedule. You're always in control of what's flowing in.
Google Drive
Connect Drive via OAuth. The platform surfaces a native Drive Picker so you select files or whole folders. Selected files materialize into your Asset Vault — full text extracted, OCR fallback applied to scanned documents, document analysis run automatically. Mijoro reads every word, identifies the strategic entities, scores the document quality, and adds the contents to your run's evidence base.
Drive selections are sync-aware: files flagged sync_enabled get re-pulled when you trigger a re-import; files you haven't enabled stay frozen at their imported state.
QuickBooks
Connect QuickBooks via OAuth. The platform pulls eight financial surfaces on import:
- Customers — your full customer list with revenue concentration analysis
- Vendors — vendor relationships and spend patterns
- Chart of Accounts — the structure of your books
- P&L Detail — line-item profit and loss
- AR Aging — accounts receivable detail, the canonical churn signal
- AP Aging — accounts payable detail
- Customer Transactions — sharded for large books, dedupe-safe
- Vendor Transactions — same architecture
Each surface lands as both a raw JSON twin (for replay and audit) and a markdown twin (LLM-grounded narrative). The signal engine watches for burn-rate drift, runway shifts, revenue swings, customer concentration risk, expense anomalies — and surfaces what it finds on your Command Center the moment it appears.
Asana
Connect Asana via OAuth. The platform pulls projects, tasks, milestones, and workspace structure. Signal interpretation watches for execution slippage, scope creep, delivery risk — patterns most operators don't catch until quarter-end. The execution data feeds the operational sections of every dossier and boardroom report.
OAuth and re-imports
All three providers use standard OAuth 2.0 with PKCE. Tokens are encrypted at rest with AES-256-GCM. The platform stores refresh tokens, not raw credentials. Disconnecting an integration enqueues a background purge job that cascades through every artifact and removes the provider's data — the disconnect API returns immediately so you're not waiting; the cleanup completes in the background.
Re-imports overwrite the previous import for the same provider. The prior import is archived (not deleted) so you can roll back if something goes wrong with the new import.