What you need
- An account with each provider you want to use, with API access on your plan with that provider.
- The owner or admin role to add an account (the form lives inside Tables, not in Settings). Members can then use the accounts in their columns.
- About 5 minutes per provider.
Overview
AgentSDR supports 15 providers. Each has its own connection (an API key, or a client ID and secret for Snov.io), verified with a live call before it is saved. Connections belong to your organization, are encrypted withINTEGRATION_CREDENTIALS_KEY, and are never sent back to the browser. There is no environment fallback.
Credits are billed by the vendor. Each enrichment run spends credits or units on your own account with that provider. AgentSDR adds no markup, does not convert credits to money and shows no per-run price. Watch usage in the provider’s dashboard and test a column on 10 rows before running a whole table.
The providers
The Returns column summarizes what each provider can look up; the setup screen shows the exact inputs and outputs of every action. Where a row says “see the provider’s docs”, follow the link: that vendor moves its API key page often.
Connect a provider account
1
Get the API key from the provider
Use the table above. Copy it right away if the provider shows it only once.
2
Open the enrichment catalog in a table
In a table, click Actions, then Add enrichment. Search with Search providers and enrichments…. Providers you have connected show a green dot and Connected. The rest are greyed out.
3
Choose the provider
Click it. If you have not connected it, you see Connect (provider) to use its actions and the note “Your credentials will be verified before the integration is enabled.”
4
Add the account
Click Add account. Enter an Account name (optional: it defaults to “(provider) account”) and the credential field(s) the provider asks for. A required field is marked with a red asterisk. Click the help link next to the form to open the vendor’s page.
5
Save
AgentSDR makes a live call to the provider to verify the credentials. If it fails, nothing is saved and the form shows the reason. When it works the provider shows Connected.
Several accounts per provider
You can add more than one account for the same provider, for example one per client or per plan. The Account dropdown in a column’s setup lists every account for that provider (an unverified one is marked “verification required”), and each column keeps its own choice. There is no automatic rotation or fallback: a column uses the account you selected.Check that it works
The provider shows a green dot and Connected in the catalog. Add one of its actions to a table and click Save & run 10 rows to see real results.
Troubleshooting
(Provider) rejected this API key.
(Provider) rejected this API key.
The provider answered that the key is wrong, revoked or without API access. Copy it again from the provider’s page. Snov.io says “Snov.io rejected this client ID or client secret.”
(Provider) rate-limited verification. Try again shortly.
(Provider) rate-limited verification. Try again shortly.
The vendor throttled the check. Wait a minute and try again.
(Provider) could not verify this account right now. Try again shortly.
(Provider) could not verify this account right now. Try again shortly.
The vendor had an error. Try again later.
(Provider) could not be reached. Check your connection and try again.
(Provider) could not be reached. Check your connection and try again.
Your server could not reach the vendor. Check outbound internet access.
This Apollo key does not have permission to read the current user profile.
This Apollo key does not have permission to read the current user profile.
The Apollo key is scoped too narrowly. Create a new key in Apollo with access to that endpoint, or set it as a master key (some Apollo actions, such as listing users, need one).
A field is required, or the account name is too long
A field is required, or the account name is too long
You see “(field label) is required” for an empty credential and “Account name is too long” past 120 characters.
Runs are refused for a column
Runs are refused for a column
If the account is later disabled, unverified, or its credentials cannot be read, runs for that column are refused with a message to reconnect. Add the account again.
Next
Enrichment in Tables
Add enrichment columns and run them.
Tables
Statuses, retries and runs.
Integrations overview
All integrations and how credentials are stored.
OpenRouter
The AI side of columns.