Skip to main content

Nodes

Nodes are the building blocks of a workflow. Each node has a type, a configuration, and connections to other nodes. Drag them from the node library onto the canvas, connect them, and configure each one.

Nodes fall into these categories.

Triggers​

Start a workflow.

  • Chat Input — start from a conversational message.
  • Webhook — start from an incoming HTTP call. The call is authenticated with a shared secret you configure, and the request body seeds the run.
  • Scheduled — start on a recurring schedule (cron).

Tools​

Do work.

  • Ingest Source — pull a connected source into InaiBridge's canonical store. Asana and Azure DevOps are supported here; choose the source in the node's configuration. (Jira data powers the Portfolio and briefings today; on-demand Jira ingest through this node is on the roadmap — see Connecting your data.)
  • RAG — retrieve grounded context from your project data.
  • RAG Ingest — chunk, embed, and load text into the vector store (the write-side pair to RAG).
  • Embedding Config — declare the embedding model a downstream RAG Ingest should use.
  • API Connect — call an external REST endpoint. The target host must be on your organization's allowlist.
  • MCP Connect — connect to an MCP server over HTTP/SSE, discover its tools, and call one. Authentication is supplied from your org's secret store.
  • Project Briefing — produce a grounded, multi-tier briefing over your connected project data. See Project Intelligence.

Transform​

  • Transform — reshape data between formats (JSON, CSV, XML) or through a template.

Agents​

  • Agent — an LLM agent that reasons over its input. You configure the model and the prompt.
  • InaiAgent — a grounded agent: it reasons over your data, cites its sources, and abstains when it can't. See InaiAgents.

Human-in-the-loop​

Pause a workflow for a person.

  • Custom HIL — a human approval gate. The run pauses and waits for a decision (approve, reject, or escalate), which is recorded to a signed decision record. Pending gates appear in the Inbox.
  • Customer Confirm — a confirmation gate for details that need a human sign-off.

Output​

Deliver results.

  • Chat Output — return the result to the conversation.
  • Send Email — deliver the result by email.

Configuring a node​

Select a node to open its configuration panel. Each node type exposes its own fields — for example, the Ingest Source node lets you choose which source to pull, and the Agent node lets you set the model and prompt. Where a field references a credential (such as an API key), it points at a value in your organization's secret store rather than holding the secret directly.

note

Some nodes carry a capability note in the product — for example, RAG runs on the built-in vector store today (other stores are roadmap). The node's configuration panel states these where they apply.