The raw key is shown only once. Store it in a secret manager.Available scopes cover channel reads, conversation reads/writes, handoff creation, custom tools, tool logs, and WhatsApp templates.To disable a credential, select Revoke and confirm. Revocation is irreversible.
For a tool named get_order_status, a successful conversation follows this sequence:
The customer asks, “Where is order A-1003?”
The assistant calls the tool with { "order_number": "A-1003" }.
Your backend returns structured order data.
Playground shows Action completed: get order status. A live Conversations timeline shows the compact operator receipt Action completed.
The assistant turns the tool result into a natural customer reply.
The action receipt and raw tool output are operator-only. Customers receive the assistant’s final response, not the receipt. For a complete request, response, receipt, and final-message example, see Custom AI Tools.
Open Activity logs to inspect tool, status, endpoint, response status, duration, request, redacted headers, response, and error details.If a receipt shows Action failed, open its activity log before retrying. Confirm whether the failure came from invalid arguments, authentication, timeout, a non-2xx backend response, or malformed output. Do not assume that a mutating action completed.
Grant the narrowest API scopes and tool permissions possible. Treat copied keys and tool secrets as production credentials.
Each tool-call attempt consumes one credit, separately from any completed AI response. See how Visito credits work for counting examples.
