Skip to main content
Conversational Agent Graphs handle real-time chat and voice. Users interact through connected channels or your own apps via the Chat API — routing, tools, and RAG logic live in Graph Studio.

Graph Studio

Design nodes, prompts, tools, and RAG on the canvas.

Channels

Web chat, WhatsApp, Slack, Teams, voice, email.

Deploy to channel

Wire a build to a connected channel environment.

Deploy as Chat API

HTTP chat endpoint for apps and backends.

​
What Conversational graphs do

Graph Studio with Test and toolbar

Graph Studio — Test panel for Conversational graphs

​
Supported channels

Configure channel credentials once under workspace Integrations, then assign a build during Deploy to Channel. See Channels overview.

​
Design workflow

  1. Create a Conversational Agent Graph from Workspace Home.
  2. In Graph Studio, add Start, Master Agent, and End nodes (Node types).
  3. Configure each agent node’s prompt, tools, and RAG (Agent configuration).
  4. Define variables for inputs the graph should capture across turns.
  5. Click Save, then Build to pin tool versions (Builds).
  6. Assign the build to DEV / UAT / PROD.
  7. Click Deploy and choose a target:
Test in Graph Studio with Test before promoting builds to PROD. Use Observability logs to trace conversation paths and refine prompts.

​
Deploy via Chat API

When you deploy as Chat API, Phinite exposes an HTTP endpoint backed by your pinned build. Your application sends user messages and receives agent responses — no channel webhook required.
  1. Create and Build your Conversational graph.
  2. Click Deploy → Deploy as Chat API.
  3. Select environment and build version.
  4. Copy the endpoint URL and authenticate with your workspace API key.
  5. Send chat payloads from your backend or mobile app.
See Deploy and Reference API for request formats.

​
Deploy via channels

  1. Connect the channel under workspace Integrations (Configure integrations).
  2. Build and assign to the target environment.
  3. Click Deploy → Deploy to Channel.
  4. Select channel, environment, and build.
  5. Complete webhook or OAuth steps shown in the modal.
See Deploy to a channel for per-channel details.

​
Best practices

  • Keep prompts focused — one clear mission per Master Agent node.
  • Capture structured variables early so downstream tool nodes have clean inputs.
  • Publish and pin tool versions before production builds.
  • Monitor session logs for failed tool calls and unexpected routing.