Key concepts

Core terminology used across Convoship.

ConceptDescription
WorkspaceMulti-tenant container; all Assistants, Agents, and secrets belong to one workspace.
AssistantScripted bot with intents, flow versions, and deployments (/app/assistants).
AgentAgentic bot with mission, tasks, tools, and playground (/app/agents).
IntentMatches user utterances and runs a dedicated sub-flow.
EntityCaptures a typed value from user input into a slot.
Slot / variableSession-scoped value filled by entities or set nodes.
ToolHTTP integration (URL, headers, body) with JSONPath output mapping.
Flow versionImmutable snapshot created when you publish; drafts autosave on every edit.
DeploymentChannel token (cdp_*) that authenticates the public embed runtime.
Workflow (graph)React Flow orchestration at /app/workflows/{id}/flow — publish, simulator, channels.
Workflow chainForm-based primitive chain at /app/workflows/chains/{slug}/edit — run, resume, webhook ingress.
Deploymentcdp_* bearer token for embed public runtime.
Import reviewApprove enriched import before first publish when enabled.

How runtime chooses a path

  1. Welcome event may fire on session start.
  2. User message is matched against intents (phrases + LLM fallback).
  3. Matched intent's sub-flow executes node by node.
  4. Entity nodes prompt until the slot is filled or max attempts reached.
  5. Service/tool nodes call HTTP APIs and map responses into variables.
  6. When no intent matches, fallback or small-talk handlers may respond.