Search and discover available data enrichments. Use this to find the right enrichment for a specific task (e.g., "linkedin profile", "email finder", "company data"). Returns a list of matching enrichments with their IDs, descriptions, required parameters, and pricing. Results are sorted by recommendation rank (best options first). BYOK providers that the user has not connected are automatically excluded.

Get detailed information about a specific enrichment, including all required and optional parameters, response fields, pricing, and data source. Use this before running an enrichment to understand what parameters are needed.

Execute a data enrichment with the provided parameters. Automatically handles async execution and polling, returning final results. Results are cached for 24 hours to reduce costs. Subject to spending limits (DATABAR_MAX_COST_PER_REQUEST, DATABAR_MIN_BALANCE). For paginated enrichments, use the pages parameter to fetch multiple pages (each page is billed separately).

Execute an enrichment on multiple inputs at once. Provide an array of parameter objects. Subject to spending limits. For paginated enrichments, use the pages parameter to fetch multiple pages per record (each page per record is billed separately).

Get available choices for a select/mselect enrichment parameter. Supports search and pagination. Use this when get_enrichment_details shows a parameter with choices.mode = "remote". For inline choices, the values are already included in get_enrichment_details.

Search available waterfall enrichments. Waterfalls try multiple data providers in sequence until one succeeds, maximizing data retrieval success rate.

Execute a waterfall enrichment that tries multiple providers until one succeeds. Subject to spending limits.

Execute a waterfall enrichment on multiple inputs at once. Subject to spending limits.

Create a new table in your Databar workspace. Optionally specify a name, column names, and number of empty rows. By default creates columns column1/column2/column3 and 0 rows.

List all tables in your Databar workspace. Returns table UUIDs, names, and timestamps.

Get all columns defined on a table. Returns column names, types, and identifiers.

Get rows from a table with pagination and optional filtering. Returns up to 100 rows per page by default (max 500). Supports Airtable-style structured filters with 5 operators: equals, contains, not_equals, is_empty, is_not_empty. Multiple filters use AND logic.

Insert new rows into a table (max 100 per request). To add new columns to an existing table, set options.allow_new_columns to true — any column name in fields that does not exist yet will be auto-created as a text column.

Update specific fields on existing rows by row ID (max 100 per request).

Insert or update rows by matching key (max 100 per request).

List all enrichments configured on a table.

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:

1. Call get_enrichment_details to see the parameter names.

2. Call get_table_columns to see available column names and their internal_names.

3. 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.

4. The returned enrichment_id from this call is the TABLE-ENRICHMENT id — use it with run_table_enrichment (NOT the original enrichment_id).

Trigger an enrichment or waterfall to run on a table. By default runs on all rows. Optionally specify row_ids to run on specific rows, and run_strategy to control row selection. Works for both enrichments (from add_table_enrichment) and waterfalls (from add_table_waterfall). Subject to spending limits.

Add a waterfall to a table. A waterfall tries multiple data providers in sequence until one returns a result.

WORKFLOW:

1. Call search_waterfalls to find the right waterfall (e.g. "email_getter", "person_getter").

2. Note the waterfall identifier, available_enrichments (provider IDs), and input_params.

3. Call get_table_columns to see available column names.

4. Build the mapping: keys are waterfall param names, values are column names.

5. The returned id is the TABLE-WATERFALL id — use it with run_table_enrichment to trigger a run.

List all waterfalls installed on a table. Returns waterfall IDs that can be used with run_table_enrichment.

Search and discover available data exporters (CRM/destination integrations). Use this to find the right exporter for pushing data to external services (e.g., "Google Sheets", "HubSpot", "Salesforce"). Returns a list of matching exporters with their IDs and descriptions.

Get detailed information about a specific exporter, including its required parameters and output fields. Use this to understand what parameters are needed before adding the exporter to a table.

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:

1. Call get_exporter_details to see the parameter names.

2. Call get_table_columns to see available column names.

3. Build the mapping using column names (not UUIDs).

4. The returned exporter_id from this call is the TABLE-EXPORTER id — use it with run_table_exporter (NOT the original exporter_id).

List all exporters configured on a table. Returns exporter IDs that can be used with run_table_exporter.

Trigger an exporter to run on a table. By default runs on all rows. Use run_strategy to control row selection. Subject to spending limits.

Permanently delete a table and all its data.

Rename an existing table.

Delete specific rows from a table by their row IDs.

Add a new column to an existing table.

Rename an existing column on a table.

Delete a column from a table.

Create a new folder to organize tables in your workspace.

List all folders in your workspace.

Rename an existing folder.

Delete a folder. Tables inside the folder are NOT deleted.

Move a table into a folder, or remove it from its current folder by passing folder_id as null.

Get the current user's credit balance and account information.