Team vs Agent

AgentTeam
Primary useConversational personaRole / job config + automation surface
Has voice + memory?YesOptional
GHL workflow webhook?No (removed 2026-05-07)Yes (canonical)
OpenAI-compatible endpoint?YesYes
MCP endpoint?YesYes
Routines?YesYes
Webhook_id?—Yes — immutable 8-char alphanumeric

What lives inside a team

  • A slug + a name.
  • A webhook_id (assigned on create, immutable, the URL slug GHL uses).
  • Prompts and supporting markdown files (see prompts).
  • An allowed_spokes list — same shape as agents.
  • Routines (scheduled prompts).
  • An MCP endpoint at POST /api/team/<slug>/mcp — see team MCP deep dive.
  • Integration URLs (closebot, vapi, retell, custom, ghl, mcp, run, openai).

When to pick a team over an agent

  • You need a GHL workflow webhook → team. (Required.)
  • You want an automation surface that several agents can dispatch to → team.
  • You want a conversational persona with its own identity / memory → agent.