What is Clay bring your own API key?
Bringing your own API key to Clay connects a supported integration to an account you control with that provider. Provider usage can then be billed through that external account. This differs from using a Clay-managed connection and does not make the whole workflow free.
By LeadHaste Editorial · AI-assisted editorial review ·
Two account arrangements
Clay-managed integrations provide access without separately supplying credentials for each supported provider. Some integrations also accept your own account, while others support only the managed option. Clay's current account and credit documentation distinguishes platform orchestration from provider data or AI usage. Check the specific action and current plan before estimating the cost; a provider connection does not automatically remove every Clay charge.
External billing remains external
If a supported action uses your external account, the provider's balance, permissions, limits and billing rules still matter. A successful connection test does not establish that a large run is affordable. Our recommendation is to identify the account owner, expected workload and spending boundary before enabling automatic execution. Keep an eye on both systems when diagnosing cost or quota errors, since the failure may occur outside Clay.
Choose the right connection
Name shared connections clearly so another operator can distinguish client-owned, personal and team accounts. Clay documents reconnecting an existing connection when replacing its credentials, and separately repointing columns when switching between distinct connections. Those changes can affect workflows and scheduled runs using the connection. Check the dependent actions before changing credentials rather than treating the connection as an isolated setting.
Keep secrets out of table data
Store credentials through the supported connection controls rather than ordinary cells, public examples or exported notes. Test with a small, non-sensitive record and verify which account handled the request. If access must be withdrawn, coordinate the credential change with the account owner and confirm the effect on dependent actions. Clear ownership makes the integration easier to hand over and avoids accidentally charging a personal or unrelated client account for shared production work.
Sources
Useful next steps
Related terms
Put the pieces into a system you own.
Explore your ICP and campaign fit on a free discovery call, then decide what your outbound operation needs.
Book your free ICP review →