Data purchases and workflow actions are separate cost dimensions
Clay is relevant to teams orchestrating enrichment across multiple providers. Its official pricing explanation separates Data Credits for purchased information from Actions for work performed by the platform. Bringing an external provider key can therefore shift the data bill outside Clay without removing all platform usage.
We have not verified one price and allowance combination for the same plan, billing cycle and add-ons. Confirm the Action allowance and Data Credit allowance together rather than combining figures from different configurations. A useful evaluation specifies the exact enrichment steps, provider charges, orchestration actions, unsuccessful-result rules and rollover boundaries. This is a data-workflow comparison, not evidence that a small team needs a more elaborate stack.
Price one small workflow end to end: input row, provider lookup, fallback attempt and result export. Record which step uses Actions, which buys Data Credits and which charges an external provider. A cheaper provider result may still sit inside a workflow with additional platform actions.
Best for
Teams with repeatable multi-provider enrichment workflows. Buyers who can separate platform actions from data charges.
May not fit
Simple one-off work that does not justify orchestration overhead.
Plans & cost terms
Launch or Growth — quoted configuration
Unknown- Price
- Unknown · Unknown
- Uploaded contacts (stock cap)
- Unknown
- Included team members
- Unknown
- Included client workspaces
- Unknown
- Messages / month
- Unknown
- Connected sending accounts
- Unknown
- API access
- Unknown
- CRM integration
- Unknown
- Included credit actions and allowance period
- Unknown · Unknown
- Credit action
- Data Credits purchase information; Actions meter platform orchestration
- Credit expiry
- Actions reset each cycle; Data Credit rollover is tier-specific. Verify the selected quote.
- Vendor credit / plan refund rules
- Unknown
- Tax treatment of this quote
- Unknown
- Minimum commitment (months)
- Unknown
Exact paid configuration and allowances have not been pinned to one quote. A bring-your-own-key flow may still consume Actions; third-party bills remain separate.
Unlimited account connections do not mean unlimited messages. Verification does not guarantee inbox placement.
Trade-offs to check
External provider billing may remain in addition to platform usage. Actions and Data Credits have different rollover rules.
Questions to settle before buying
- What exact plan, billing cycle and allowances does the written quote cover?
- Which workflow steps consume Actions and which consume Data Credits?
- What provider bills remain with external keys?
- How does this tier handle no-result actions and rollover?
- Could a simpler direct data purchase solve the task?
Cancellation, access & export
Confirm how to export entitled table outputs and how workflow, Action and Data Credit access changes when the plan is reduced.
Price context
Tax treatment has not been verified. Check the selected billing cycle, currency and final amount before purchasing. Unknown values are not zero or unlimited.
Evidence boundary
Source-based procurement analysis; no hands-on comparative performance test or outcome guarantee.
Sources & evidence
Checked dates describe our review of the source. They are not publication dates or hands-on tests.
