Documentation

Search documentation

Search guides, setup steps, troubleshooting, and product checklists.

AI Support10 min readUpdated May 5, 2026

AI Actions v1

Use endpoint-based actions safely with templates, tests, preview, logs, approvals, retries, secrets, and allowlists.

AI Actions v1 lets AI call approved API endpoints during a conversation. V1 is intentionally endpoint-based, not a complex connector/procedure builder. The priority is stability, safety, logs, and clear admin testing.

Safe design

  • Use read-only actions for order lookup, subscription status, appointment lookup, account metadata, and delivery tracking.
  • Require confirmation and/or approval for write actions such as cancel order, refund, update account, book appointment, or change subscription.
  • Never let AI guess required parameters. If a parameter is missing, it should ask the customer for that parameter.
  • Use action execution preview before production calls.
  • Review request, response, status, latency, failure reason, and retry count in logs.

Security controls

  • Secrets are stored server-side and masked in UI output.
  • Secrets can be rotated from action settings.
  • Outbound domain allowlist controls which hosts actions can call.
  • Failures are translated into readable explanations for admins.
text
Read order example: ask "What is the status of ORDER-12345?"
Write action example: ask "Can you cancel ORDER-12345 because the customer requested it?"
Expected behavior: read actions can run when required parameters are present; write actions require confirmation or approval.
Do not rebuild V2 yet

Advanced connectors, procedures, step builder, conditions, dry-run simulator, and temporary attributes are future V2 scope. Keep V1 reliable first.