> ## Documentation Index > Fetch the complete documentation index at: https://docs.famulor.io/llms.txt > Use this file to discover all available pages before exploring further. # Get automation run > One automation run with its step log: every executed step's action, status, input (the step's configuration as saved, before templates are filled in), output, error and timing, plus the trigger payload that started the run. Steps are ordered oldest first; a step inside a loop appears once per item. Use it to find out why a run failed. **Required scope:** `automations:read` (or `calls:read`). ## OpenAPI ````yaml /api-reference/openapi.json get /automations/{id}/runs/{runId} openapi: 3.1.0 info: title: Famulor API version: 1.0.0 description: >- REST API for Famulor. Authenticate with an API key (`fam_...`, created under **Settings → API Keys**) or an OAuth 2.0 access token (`fam_at_...`) as a Bearer token. Every response uses a consistent envelope: `{ "data": ... , "meta": { ... } }` on success and `{ "error": { "code", "message" } }` on failure. List endpoints paginate with `?limit=` (default 50, max 200) and `?offset=`; `meta.pagination.total` carries the total match count. REST operations require API Access through the workspace plan or a recurring add-on. Without it, regular operations return `403 api_access_required`. The invoice-payment and billing-portal operations remain available with a valid `billing:write` credential after a failed plan payment so an authorized owner, admin, or billing member can recover billing. The same customer-facing capabilities are available as MCP tools at `https://app.famulor.io/mcp` (Model Context Protocol, streamable HTTP) using the same credentials, scopes, and workspace access. MCP availability is controlled separately by Connect AI / MCP, not by API Access. servers: - url: https://app.famulor.io/api/v1 description: Hosted platform. - url: https://{domain}/api/v1 description: White-label tenant domain — same paths, tenant branding. variables: domain: default: app.famulor.io description: Your white-label tenant domain. security: - bearerAuth: [] tags: - name: Account description: Self-inspection of the calling credential. - name: Migrations description: Preview and import data from supported legacy platforms. - name: Assistants description: Create and manage voice assistants. - name: Tools description: >- Reusable tools (HTTP APIs and external MCP servers) assistants can call mid-conversation. - name: Voices description: Browse the text-to-speech voice library. - name: Calls description: Start outbound calls and read call history, transcripts and recordings. - name: History description: Unified conversation history across calls, messaging and assistant emails. - name: Campaigns description: Outbound calling campaigns with a compliant power dialer. - name: Leads description: Manage Audience contacts across campaigns, channels and Call QA metrics. - name: Segments description: >- Saved, dynamic lead filters — reusable audience definitions used for Audience search and campaign lead assignment. - name: Suppression description: Cross-channel marketing opt-outs and active workspace suppression records. - name: Callbacks description: >- Scheduled callbacks booked by the Schedule callback tool across voice, chat, and email. - name: Phone Numbers description: Marketplace numbers and customer-provided numbers. - name: Famulor Loop description: >- Personal business-phone access, directory, presence, devices, and Loop call recents. - name: SIP Trunks description: Bring your own SIP provider and numbers. - name: Carrier Connections description: Connect a supported carrier account and import its existing phone numbers. - name: Knowledge Bases description: RAG knowledge bases and documents for assistants. - name: Settings description: Workspace-level settings such as caller-memory defaults. - name: Billing description: Balance and transaction ledger of the API key's workspace. - name: Automations description: >- Native workspace automations — list, create, update, trigger. Requires Automations in the workspace plan. - name: Milian Missions description: Recurring jobs that Milian runs unattended on schedule. - name: Integrations description: >- Calendar integrations (Cal.com, Calendly, Acuity Scheduling, Google Calendar, Outlook, native booking engine). Assign them to assistants to provide availability and booking tools, plus provider-supported appointment lookup, cancellation, and rescheduling. - name: Bookings description: >- Native booking engine — event types with weekly availability, public booking pages at /book/{workspace}/{slug}, and the bookings they produce. - name: Dashboards description: >- Custom analytics dashboards, reusable widgets, and tenant-scoped performance analytics. Requires Custom dashboards in the workspace plan. - name: Catalog description: >- Read-only platform catalogs — available models, supported assistant languages, and prompt templates. - name: Simulations description: Assistant simulation tests (plan-gated). - name: Versions description: Assistant configuration version history. - name: Caller IDs description: Outbound caller ID verification. - name: Widgets description: Web widget connectors. - name: Messaging description: >- Telegram, Slack, and Messenger text bots linked to assistants (Chat SDK). Includes conversation delay, inactivity end, and conversation-ended webhooks. - name: QA description: Cohort AI Quality Assurance runs over call transcripts. - name: White Label description: >- Manage white-label customer accounts, defaults, credit transfers and customer plan offers. Each endpoint documents its required scope and workspace eligibility. - name: API Keys description: >- Self-service API keys for the calling workspace or a same-brand workspace where the credential's user is owner/admin. A key can only mint further keys with a scope subset of its own. - name: Workspaces description: >- List visible workspaces, create an additional workspace for the key owner, and mint a dedicated credential for a selected owner/admin workspace. - name: SMS description: Outbound SMS from workspace phone numbers. - name: Milian description: >- Ask Milian, the AI co-worker in your workspace, and start voice sessions with it. - name: Translation description: >- Live translation sessions that interpret a conversation between two languages. paths: /automations/{id}/runs/{runId}: get: tags: - Automations summary: Get automation run description: >- One automation run with its step log: every executed step's action, status, input (the step's configuration as saved, before templates are filled in), output, error and timing, plus the trigger payload that started the run. Steps are ordered oldest first; a step inside a loop appears once per item. Use it to find out why a run failed. **Required scope:** `automations:read` (or `calls:read`). operationId: getAutomationRun parameters: - name: id in: path required: true schema: type: string format: uuid description: Automation ID. - name: runId in: path required: true schema: type: string format: uuid description: Run ID (from List automation runs). responses: '200': description: The run and its steps. content: application/json: schema: type: object required: - data properties: data: $ref: '#/components/schemas/AutomationRunDetail' example: data: run: id: f1b2c3d4-0000-4000-8000-000000000031 automation_id: e1b2c3d4-0000-4000-8000-000000000030 status: failed trigger_event: call.completed error: 'Email step failed: recipient address is missing' started_at: '2026-10-07T09:41:02Z' finished_at: '2026-10-07T09:41:03Z' created_at: '2026-10-07T09:41:01Z' credits_charged: 0 automation_name: Lead follow-up trigger_payload: event: call.completed timestamp: '2026-10-07T09:41:01Z' data: call_id: c1b2c3d4-0000-4000-8000-000000000010 summary: Caller asked for a quote. steps: - id: a1b2c3d4-0000-4000-8000-000000000041 run_id: f1b2c3d4-0000-4000-8000-000000000031 node_id: action-1 action: condition status: completed input: left: '{{data.status}}' operator: equals right: completed output: branch: true error: null started_at: '2026-10-07T09:41:02.100Z' finished_at: '2026-10-07T09:41:02.140Z' created_at: '2026-10-07T09:41:02.100Z' - id: a1b2c3d4-0000-4000-8000-000000000042 run_id: f1b2c3d4-0000-4000-8000-000000000031 node_id: action-2 action: email.send status: failed input: to: '{{data.email}}' subject: Your quote output: {} error: 'Email step failed: recipient address is missing' started_at: '2026-10-07T09:41:02.150Z' finished_at: '2026-10-07T09:41:02.900Z' created_at: '2026-10-07T09:41:02.150Z' steps_truncated: false '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '429': $ref: '#/components/responses/RateLimited' '503': $ref: '#/components/responses/RequestProtectionUnavailable' components: schemas: AutomationRunDetail: type: object properties: run: allOf: - $ref: '#/components/schemas/AutomationRun' - type: object properties: trigger_payload: type: object additionalProperties: true description: >- The event that started the run: `{ event, timestamp, data }`. steps: type: array items: $ref: '#/components/schemas/AutomationRunStep' description: Executed steps, oldest first (at most 500). steps_truncated: type: boolean description: True when the run executed more steps than are returned. AutomationRun: type: object description: >- One execution of an automation (without its trigger payload — see Get automation run). properties: id: type: string format: uuid readOnly: true automation_id: type: string format: uuid readOnly: true status: type: string enum: - queued - running - completed - failed - cancelled description: '`queued` → `running` → `completed` or `failed`.' trigger_event: type: string description: >- What started the run, e.g. `call.completed`, `webhook.inbound`, `manual`. error: type: - string - 'null' description: Why the run failed (usually the failed step's error). started_at: type: - string - 'null' format: date-time finished_at: type: - string - 'null' format: date-time created_at: type: string format: date-time credits_charged: type: number description: Credits charged for AI steps of this run. automation_name: type: - string - 'null' description: Name of the automation. AutomationRunStep: type: object description: One executed step of a run. properties: id: type: string format: uuid readOnly: true run_id: type: string format: uuid readOnly: true node_id: type: string description: ID of the step's node in the automation graph. action: type: string description: >- Step type, e.g. `http.request`, `email.send`, `condition`, `loop.on_items`, `app.execute`. status: type: string enum: - pending - running - completed - failed - skipped input: type: object additionalProperties: true description: The step's configuration as saved (templates not filled in). output: type: object additionalProperties: true description: What the step returned. error: type: - string - 'null' started_at: type: - string - 'null' format: date-time finished_at: type: - string - 'null' format: date-time created_at: type: string format: date-time ErrorEnvelope: type: object description: Error envelope returned by every /api/v1 endpoint on failure. required: - error properties: error: type: object required: - code - message properties: code: type: string enum: - unauthorized - forbidden - api_access_required - not_found - invalid_request - rate_limited - conflict - telephony_configuration_error - telephony_unavailable - destination_forbidden - internal_error - service_unavailable description: >- Stable, machine-readable error code. `service_unavailable` is returned by POST /bookings and GET /booking-event-types/{id}/slots specifically when the availability engine could not be reached (see AvailabilityOrProtectionUnavailable). message: type: string description: Human-readable description of the error. responses: Unauthorized: description: Missing, invalid, expired or revoked API key / access token. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' example: error: code: unauthorized message: Invalid API key. Forbidden: description: >- The credential lacks the required scope or role, or the workspace does not have the required capability. content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' examples: scopeDenied: summary: Required scope is missing value: error: code: forbidden message: >- This API key is missing the required scope "assistants:write". apiAccessRequired: summary: API Access is not available value: error: code: api_access_required message: >- API Access is not available for this workspace. Review Settings → Plan. NotFound: description: Resource not found (or it belongs to another workspace). content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' example: error: code: not_found message: Assistant not found RateLimited: description: Too many requests. Retry after the indicated delay. headers: Retry-After: description: Seconds to wait before retrying. schema: type: integer minimum: 1 content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' example: error: code: rate_limited message: Too many requests. Retry after the indicated delay. RequestProtectionUnavailable: description: Request protection is temporarily unavailable. headers: Retry-After: description: Seconds to wait before retrying. schema: type: integer minimum: 1 content: application/json: schema: $ref: '#/components/schemas/ErrorEnvelope' example: error: code: internal_error message: Request protection is temporarily unavailable. securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: API key description: >- 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. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.