Queue designer schema, enums, conditionals, and live options
Call this before creating or editing a queue. The response is intentionally descriptive for developers and AI agents: schema.channels tells which endpoint id to use when a channel is selected (call/phone uses available_endpoints.call[].id, facebook uses page_id, instagram uses instagram_business_id); schema.conditional_by_mode tells which settings are shown or omitted for autopilot, copilot, and human_first; schema.flow lists overflow, escalation, knowledge-gap, callback, and working-hours enums; schema.routing_rules lists IF -> THEN trigger requirements. agents, users, contact_fields, target_queues, and knowledge_gap_queues are live workspace choices.
Authorizations
Use a Bearer token to access these API endpoints. Example: "Bearer {your-token}"
Query Parameters
Current queue being edited. When supplied, queue targets exclude this queue and knowledge-gap targets also require Human First or Copilot channels.
Optional channel filter for available_endpoints. Accepted keys: call, whatsapp, facebook, instagram, sms, email. Aliases: phone/voice -> call, messenger -> facebook, ig -> instagram.