Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.cellbot.chat/llms.txt

Use this file to discover all available pages before exploring further.

Custom Actions let you extend your AI assistant with webhook integrations. Define HTTP endpoints that the AI can call during conversations to check inventory, query external systems, or trigger workflows.
Custom Actions is available on Pro Plus.

​
How It Works

  1. Define an action — give it a name, description, endpoint URL, and parameters
  2. The AI learns when to use it — based on your description
  3. During a conversation, the AI calls your endpoint and uses the response to help the customer
The AI treats your custom actions as additional capabilities alongside its built-in features.

​
Creating an Action

FieldDescription
Display NameHuman-readable name (e.g. “Check Inventory”)
Action NameA short identifier for the action
AI DescriptionTell the AI when and why to use this action
Endpoint URLYour webhook URL (must be HTTPS)
HTTP MethodGET or POST
ParametersNamed parameters the AI will extract from the conversation

​
Parameters

Each parameter has:
  • Name — A descriptive name for the value
  • Type — String, Number, or Boolean
  • Description — Helps the AI understand what to extract from the conversation
  • Required — Whether the AI must have this value before calling

​
Example: Check Inventory

Say you want the AI to check part availability. You’d create an action like:
  • Name: Check Inventory
  • Description: Check if a specific part is in stock. Use when a customer asks about part availability.
  • Endpoint: https://api.yourshop.com/inventory/check
  • Parameters: Part name and device model
When a customer asks “Do you have iPhone 15 Pro screens in stock?”, the AI will pick up the relevant details from the conversation, call your endpoint, and relay the answer back to the customer.

​
Response Format

Your endpoint should return JSON. The AI will interpret the response and present it conversationally. There’s no required schema — the AI is flexible enough to handle most JSON structures.

​
Security

  • Endpoints must use HTTPS
  • Requests are time-limited to prevent slow endpoints from blocking conversations
  • Call counts are tracked per action for monitoring
  • Actions can be toggled active/inactive without deleting

​
Use Cases

  • Inventory checks — Real-time stock availability
  • CRM lookups — Check customer history or loyalty status
  • Warranty validation — Verify warranty status by serial number
  • External pricing — Query a third-party pricing API
  • Workflow triggers — Kick off processes in Zapier, Make, or n8n