{
  "type": "table.run.completed",
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "timestamp": "2023-11-07T05:31:56Z",
  "data": {
    "run_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "table_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "workspace_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "organization_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "source": "<string>",
    "failure_reason": "<string>",
    "created_at": "2023-11-07T05:31:56Z",
    "completed_at": "2023-11-07T05:31:56Z",
    "counts": {
      "complete": 1,
      "errored": 1,
      "cancelled": 1
    }
  }
}

API Reference

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.

WEBHOOK

table.run.completed

{
  "type": "table.run.completed",
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "timestamp": "2023-11-07T05:31:56Z",
  "data": {
    "run_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "table_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "workspace_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "organization_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "source": "<string>",
    "failure_reason": "<string>",
    "created_at": "2023-11-07T05:31:56Z",
    "completed_at": "2023-11-07T05:31:56Z",
    "counts": {
      "complete": 1,
      "errored": 1,
      "cancelled": 1
    }
  }
}

Body

application/json

type

any

required

string<uuid>

required

Equal to the webhook-id HTTP header. Stable across retries; use for receiver-side deduplication.

timestamp

string<date-time>

required

Event time (when the business action happened), set once at publish and replayed on retries. NOT the dispatch time, which lives in the webhook-timestamp HTTP header and is recomputed per send.

data

object

required

Terminal counts for a table operation. Aggregate counts only, never child-id arrays, so payload size is constant regardless of run width.

Show child attributes

Response

200

Receiver acknowledged.

Guide

Event reference

Table run completed

Body

Response