Run a column
Run enrichment capabilities against rows in the open table. Scope the batch from the toolbar Run menu, or turn on auto-run so rows you add later run on their own.
Email Finder
Toolbar Run opens a compact menu: pick scope (first 10, all unenriched or error, or force overwrite), then confirm spend when approval is required.
Manual vs auto-run
| Mode | Behavior |
|---|---|
| Manual-run | You choose when to run from Run or the column menu. This is the default. |
| Auto-run | Rows added after you turn it on run on their own. Rows already in the table and edits to existing rows never trigger it. |
Turn on auto-run
- Open Run in the table toolbar and choose Auto-run….
- Set rows at a time (1 to 100) and rows a day.
- Review what it will do, then choose Turn on.
Auto-run runs the table's enrichment columns on the rows its current view keeps. It stays on until you open Auto-run… and choose Turn off. Only people who manage integrations see the option.
| Workspace | Where it runs | Who pays |
|---|---|---|
| Local | On this computer while Appenda is open | Your own API keys |
| Cloud | In the cloud, with the desktop closed | Workspace credits |
Cloud tables can also be configured through the API. Moving a local workspace to the cloud turns its auto-run off, because the money source changes; turn it on again in the cloud.
What auto-run does on its own
- Columns run in order: a column waits while a column it reads still has rows queued.
- The status bar shows the run mode, for example Auto-run · 12 queued.
- When the day's row cap is reached it pauses until the next day (UTC).
- It stops, with the reason in the status bar, when a run cannot go ahead: a missing API key, a run that needs approval, or a column or view that changed since you turned it on. Save it again from Auto-run… to resume.
- Stop on an auto-run batch cancels the rows still queued. Answers already returned are kept, and auto-run stays on for the rows you add next.
Run menu scopes
Open Run in the table toolbar (Play icon, right cluster):
- First 10 rows: runs the first 10 rows again, including rows that already have a result
- Run rows…: runs the rows you pick again, including rows that already have a result
- All unenriched or error: runs rows with no result or a failed one, and skips cells that already succeeded
- Force (overwrite all): re-run every visible row; needs confirmation
A row with a missing input is never sent and costs no credits, whichever scope you pick.
The menu shows the capability name and provider logo, not a generic "enrichment column" label.
Column header Run uses the same scopes for that field only.
Preview and approval
Paid workspaces may require approval before credits spend or external egress. You see a preview of row count and cost class before execution when policy requires it.
See Approvals and Permissions.
While a job runs
- Status chrome shows progress for the active table run.
- Stop cancels pending queue work only.
- Responses already returned from the provider are written and kept.
- Shared Appenda credits exhausted mid-job stop the remainder hard.
When the job finishes, one entry appears in Version control.
Result details
Click an enrichment cell to open the result inspector: capability label, HTTP status, nested JSON (expand objects; copy per field or copy-all for the row payload). Use prev/next row chevrons to walk the column.