add_table_exporter
Add an exporter to a table by mapping exporter parameters to table columns or static values, enabling per-row data enrichment.
Instructions
Add an exporter (CRM/destination) to a table with a parameter-to-column mapping.
IMPORTANT — mapping format: Each key is an exporter 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.
WORKFLOW:
Call get_exporter_details to see the parameter names.
Call get_table_columns to see available column names.
Build the mapping using column names (not UUIDs).
The returned exporter_id from this call is the TABLE-EXPORTER id — use it with run_table_exporter (NOT the original exporter_id).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| table_uuid | Yes | The UUID of the table | |
| exporter_id | Yes | The exporter ID to add (from search_exporters or get_exporter_details) | |
| mapping | Yes | Parameter-to-column mapping. Keys = exporter param names. Values = { type: "mapping", value: "column-name" } or { type: "simple", value: "static-value" } | |
| launch_strategy | No | When to trigger: 'run_on_click' (manual) or 'run_on_update' (auto on row change). Default: 'run_on_click'. | |
| authorization | No | ID of the API key / OAuth connection to use. Required for exporters that need user authorization. If omitted, the system auto-selects the first available key. | |
| custom_body_template | No | Custom JSON body template. Column values are referenced via {column_internal_name} placeholders. When provided, mapping is ignored. |