> ## Documentation Index
> Fetch the complete documentation index at: https://docs.origami.chat/llms.txt
> Use this file to discover all available pages before exploring further.

# Table run completed

> Origami POSTs this event when a table operation (e.g. an API
enrichment batch) reaches a terminal state: complete, cancelled, or
failed.

`data.counts` carries aggregate terminal child-outcome counts
(`complete`, `errored`, `cancelled`), never child-id arrays, so
payload size is constant regardless of how wide the run was.
Correlate via `data.run_id` and read the durable status at
`GET /api/v2/tables/:tableId/runs/:runId`.

v1 emits this event only for API enrichment batches (`enrich=true`
on a v1 row insert or v2 upsert); agent-, UI-, and
lead-source-produced table runs are deferred.

**Default in the picker:** off.




## OpenAPI

````yaml /openapi-webhooks.yaml webhook table.run.completed
openapi: 3.1.0
info:
  title: Origami Webhooks
  version: '1.0'
  description: |
    Outbound events Origami POSTs to your servers when sequencer or table
    activity happens. Verify the `webhook-signature` header on every request
    before acting on the payload; see the signatures guide. Receivers
    MUST dedupe on the `webhook-id` header. Configure endpoints in
    **Settings → Developers → Webhooks**.
servers: []
security: []
paths: {}

````