Connecting Your Data
InaiAgents are only as good as the data they can see. Connect your project tools so InaiBridge can build its canonical record.
Supported sources
| Source | Status | On-demand ingest node |
|---|---|---|
| Jira | Supported — powers the Portfolio and briefings | Roadmap |
| Asana | Supported | Yes — Ingest Source |
| Azure DevOps | Supported | Yes — Ingest Source |
All three sources feed InaiBridge's canonical record and can be reasoned over by InaiAgents. Asana and Azure DevOps can additionally be pulled on demand from a workflow using the Ingest Source node; an on-demand Jira ingest node is on the roadmap.
Connecting a source
You connect a source by adding its credentials to your organization's secret store. Credentials are encrypted at rest and are never shown back or included in any agent output.
- Jira — an account email and API token (Basic auth), plus your Jira base URL.
- Asana — a personal access token and the workspace to read.
- Azure DevOps — a personal access token (PAT), plus your organization and project. Authenticating with a Microsoft Entra service principal is on the roadmap for enterprise deployments; today the connector uses a PAT.
Once the credentials are stored, ingestion reads your work items and maps them into one consistent internal record — regardless of which tool they came from — so every InaiAgent can reason over that data. For Asana and Azure DevOps you can also trigger a pull on demand with the Ingest Source node.
Your data stays scoped to your org
Connected data and the intelligence built from it are scoped to your organization. See Projects & workflows for how organization scoping works.