Choose an Agent Type
Compare static, HTTP, and webhook agents before creating your first agent.
Choose the integration your conversation needs. All three types use Orbitali's managed voice runtime and can use uploaded knowledge and supported calling channels.
| Type | Choose it when | Prompt | Custom tools | Backend setup |
|---|---|---|---|---|
Static (static) | You need answers from saved instructions and knowledge | Saved | No custom HTTP or webhook tools | None for the conversation |
HTTP (http) | You want actions against existing APIs | Saved | Each tool calls its own endpoint | Provide endpoint URLs, methods, and authentication |
Webhook (webhook) | Your backend coordinates actions or supplies per-call instructions | Saved or dynamic | Tool events go to one Server URL | Implement an Orbitali webhook handler |
Examples: a business-hours assistant can be static; an order-status assistant can use HTTP tools; a receptionist that loads customer-specific instructions before answering can use a webhook.
Choose the type before creating the agent. It cannot be changed afterward. To switch types, create another agent and configure its tools and phone assignments. A static agent is a good first test, but choose HTTP or webhook immediately if you already need custom actions.
Agent type and prompt mode are different
agentType selects how custom integrations run. promptType selects where instructions come from:
staticprompts use saved identity and instructions. All three agent types support this mode.dynamicprompts are fetched from your Server URL at session startup. Only webhook agents support this mode.
A webhook agent with a static prompt is still a webhook agent. A static agent can use built-in knowledge retrieval; “static” does not mean it repeats a script. Connected MCP tools are managed separately through MCP Integrations.
Organization notifications work with every type
Call lifecycle webhooks report call start, end, and generated summaries for static, HTTP, and webhook agents. Configure them once in Settings → Webhooks. They do not require a webhook-type agent and do not replace custom tools or dynamic prompts.
Choose a creation path
- Dashboard: choose the agent type, then a template or blank configuration.
- REST API: explicitly send
agentType. Omitting it defaults towebhook. Follow API Getting Started. - Create with AI: the Conversational Agent Builder creates HTTP agents. It is a creation method, not a fourth agent type.
Continue with Create a Static Agent, Create an HTTP Agent, or Create a Webhook Agent.