Enrichments
Fill table fields from marketplace providers: email finders, company data, web research, and your own HTTP endpoints.
The Enrichments tab is a workspace catalog: flat capability rows with provider logos. Filter by category, connect BYOK providers, or add a column from a table.
Overview
Enrichments are columns on a table backed by a catalog capability. The Enrichments workspace tab is a directory where you browse what is available, connect API keys, and try capabilities in a sandbox.
Production runs usually start from an open table or from Agents when an agent launches a search or enrichment job.
Open the Enrichments tab
- Click Enrichments in the title bar (Layers icon, beside Version control).
- Browse flat capability rows: provider logo plus action label (for example Email Finder).
- Filter with Search and the category menu in the toolbar.
- Choose Connect on BYOK providers (including HTTP request) to store an encrypted workspace key.
Add a column from a table
- Open a table.
- Use + Field (or the column add flow) and pick Enrichment.
- Choose a capability from the catalog modal.
- Configure inputs in the table-scoped sidebar (maps source fields to provider inputs).
- Set Auto-run or Manual-run for the table.
See Run a column for batch scopes and Stop behavior.
Credits and keys
| Billing | When |
|---|---|
| Managed credits | Appenda-operated provider keys on paid plans; per-success pricing varies by endpoint |
| BYOK (0 credits) | Your encrypted API key; required for Custom HTTP and some integrations |
Shared-credit exhaustion stops remaining queued rows hard. Stop cancels pending work but keeps provider responses already returned.
What lands in version history
An approved enrichment batch writes one Version control commit when the job finishes, not one commit per row.
List-import search jobs follow the same rule: one commit when the job ends. Agents are the primary launcher for list import on paid workspaces.