Credit Usage
Credits are consumed per row, per action. On a table with ten action columns that adds up faster than it feels. Settings → Credit Usage is where you see what actually spent them.
What it shows
- Credits used this billing cycle and the balance remaining
- A breakdown by action or integration
- Which workspace or table consumed them
How to open it
- Open Settings from your avatar in the top-right
- Under Workspace Settings, click Credit Usage
Reading it
Check it in this order when the balance drops faster than expected:
- Which action tops the list? Waterfall enrichments call several providers per row — see Find Work Email.
- Is Auto-run on somewhere it should not be? Every imported row triggers every column.
- Any auto update columns? Those charge again on every refresh, whether or not the value changed.
- Duplicate rows? The same company enriched twice costs twice — dedupe before you enrich.
Bringing spend down
- Filter to your ICP before running any paid column
- Test prompts on five rows, not five thousand
- Connect your own API keys for the providers you already pay for
- Turn off refreshes on fields that never change
Common use cases
- Find the column responsible when the balance drops faster than expected
- Forecast next month’s usage from what this month actually cost
- Decide which providers are worth bringing your own key for
- Check what a large run cost before repeating it
- Report spend per workspace when you run tables for different clients
Best practices
- Check it right after a large run, not at the end of the billing cycle
- Compare actual spend against your Est. per lead estimate — a big gap means a gate is not firing
- Look at refreshes and duplicate rows before blaming a provider’s price
- Trace the top action back to the table it ran in; the cost is usually one column, not the whole build
- Check here before every plan upgrade
Where to next
- Credits — how each action is charged
- Plan & Billing — plan, top-ups, invoices