Skip to main content
POST
Preview or run a Milian AI automation action

Authorizations

Authorization
string
header
required

API key (fam_..., created under Settings → API Keys) or an OAuth 2.0 access token (fam_at_...). REST operations also require API Access for the credential's workspace. Keys can be restricted to scopes such as assistants:read, calls:write, campaigns:write, automations:read, dashboards:read, dashboards:write, leads:write, segments:write, loop:read, loop:write, phone_numbers:write, sip_trunks:write, knowledge:write, voices:read, billing:read, billing:write, settings:write, platform:read, platform:write; a *:write scope implies the matching *:read. Automation and dashboard endpoints also accept the legacy calls:* scope. Keys without scope restrictions have full access within the workspace's available capabilities.

Body

application/json
action
enum<string>
required
Available options:
ai.classify,
ai.check_condition,
ai.score,
ai.detect_labels,
ai.analyze
config
object
required
context
object
dry_run
boolean
default:true

Response

Success envelope. Execution returns success, optional error and data. data includes accepted/uncertain status, results by question key, nullable values and credits. Preview returns dry_run=true without model usage.