Ingest into Table
Module · Stable
Land an extracted document into a table using the table’s bound ingestion recipe — field map, provenance, and idempotent upsert applied.
Takes the raw result of an Extract step and lands it into a custom table via that table’s own ingestion binding — so the flow never re-specifies the field map. The binding supplies how each recipe field maps to a column, stamps provenance (source document, recipe, confidence) onto the row, and upserts idempotently: by the binding’s business key when that field was read, else by the source document, so re-ingesting the same document updates its row instead of duplicating. A low-confidence extraction (needs_review) is HELD — never auto-written onto a key you may have misread — and reported via the held output for a review step to pick up. A value the destination column cannot type is dropped (listed in dropped), never failing the whole row. The table must have a recipe bound first (Table → Ingestion recipe).
When to use
Section titled “When to use”Use right after an Extract step to make a table the hands-free destination for documents — e.g. incoming_email → extract(recipe_key) → Ingest into Table, so an emailed invoice lands on the grid with zero clicks and a re-send upserts instead of duplicating. Bind the recipe on the table once; every flow then just names the table.
When not to use
Section titled “When not to use”When you already have a list of {column_key: value} rows to write (no extraction recipe involved), use Sync to Table. For a single hand-built row use Create Record. This step is specifically for landing an Extract result through a table’s bound recipe.
Inputs
Section titled “Inputs”Configured per use: table, extraction, source_doc_id, file_path.
Outputs
Section titled “Outputs”Auto-generated from the skill registry (load_skills()). Do not edit by hand.