Core Concepts

A short mental model of how InaiBridge works.

Sources

A source is a project tool you connect — Jira, Asana, or Azure DevOps. InaiBridge reads your work items from each source.

One canonical record

Every source maps into a single, consistent internal representation. That means your intelligence spans all your tools at once — a risk in Jira and a slipping initiative in Azure DevOps are reasoned about together, not in silos.

Different sources expose different levels of detail, so InaiBridge records how trustworthy each signal is. A tool that only reports "done / not done" is labeled as lower-confidence than one with rich status and dates — and InaiBridge never inflates a signal beyond what the source actually supports.

Workflows and nodes

Work in InaiBridge is composed on the Canvas as workflows — graphs of nodes connected together. A node might pull in a source, run an agent, or send a result onward.

Projects and organization

Your workflows are organized into projects, and every project belongs to your organization — the tenant boundary that scopes your connected data, secrets, and intelligence. You see your own projects by default and can switch to view your organization's shared projects. See Projects & workflows.

InaiAgents

An InaiAgent is InaiBridge's grounded intelligence — reasoning over your connected data to produce briefings and answers anchored in real records. It's a capability with several surfaces, not a single button: it shows up as the Project Briefing (a grounded multi-tier briefing), Jiggle (a grounded conversational companion), and — on the Canvas — a grounded InaiAgent node you can drop into a workflow.

Don't confuse that node with the plain Agent node. The Agent node is a general-purpose LLM step (you set its model and prompt); the InaiAgent node is grounded — it reasons over your data, cites its sources, and abstains when the data can't support an answer. The distinction that matters is grounded (InaiAgent) versus plain LLM (Agent). See Nodes and InaiAgents.