add_table_enrichment
Add an enrichment to a table by mapping enrichment parameters to table columns, using static values or column references that resolve per row.
Instructions
Add an enrichment to a table with a parameter-to-column mapping.
IMPORTANT — mapping format: Each key is an enrichment parameter name. Each value is one of: • { "type": "mapping", "value": "" } — read value from a table column per row. Use the human-readable column name (e.g. "email"). The server accepts column names directly. • { "type": "simple", "value": "" } — pass the same hardcoded value for every row. IMPORTANT: simple values can embed column references using {column_internal_name} syntax (e.g. "Find the industry of {column1}"). The internal_name for each column is shown by get_table_columns. At runtime, these placeholders are replaced with actual column values per row. You can also use human-readable column names (e.g. {Company Website}) — the server will auto-resolve them to internal names. Use {?column_name} to mark a column reference as optional (row won't fail if the column is empty).
WORKFLOW:
Call get_enrichment_details to see the parameter names.
Call get_table_columns to see available column names and their internal_names.
Build the mapping using column names (not UUIDs). For text/textarea parameters that should incorporate column data, use "simple" type with {column_internal_name} placeholders in the value.
The returned enrichment_id from this call is the TABLE-ENRICHMENT id — use it with run_table_enrichment (NOT the original enrichment_id).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| table_uuid | Yes | The UUID of the table | |
| enrichment_id | Yes | The enrichment ID to add (from search_enrichments or get_enrichment_details) | |
| mapping | Yes | Parameter-to-column mapping. Keys = enrichment param names. Values = { type: "mapping", value: "column-name" } or { type: "simple", value: "static-value" }. Simple values can embed {column_internal_name} placeholders (e.g. "Research {column1}") that are resolved per row at runtime. You can use human-readable column names in placeholders — the server resolves them. | |
| launch_strategy | No | When to trigger: 'run_on_click' (manual) or 'run_on_update' (auto on row change). Default: 'run_on_click'. |