Salesforce + Connect AI
Query Salesforce objects from any AI agent or application. Connect AI handles OAuth, SOQL translation, schema discovery, and rate-limit backoff.
Account
Contact
Opportunity
Lead
Case
User
Task
Custom__c
+ 200 more
-- Ask Claude Code (or any MCP-aware agent): -- -- "In Salesforce, list the top 25 Healthcare accounts by annual -- revenue, with a count of their open opportunities." -- -- Claude generates and runs this SQL via the queryData MCP tool. -- Standard SQL -- translated to SOQL transparently. SELECT a.Name, a.AnnualRevenue, COUNT(o.Id) AS open_opps FROM [Salesforce].[Salesforce].[Account] a LEFT JOIN [Salesforce].[Salesforce].[Opportunity] o ON o.AccountId = a.Id AND o.StageName != 'Closed Won' WHERE a.Industry = 'Healthcare' GROUP BY a.Name, a.AnnualRevenue ORDER BY a.AnnualRevenue DESC LIMIT 25
Tutorials by AI surface
Working integrations for Salesforce + every supported AI surface.
Known quirks
Things that are easy to miss the first time you connect Salesforce to an agent.
Queries returning more than 2,000 rows automatically route through the Bulk API, which is asynchronous. Agent prompts that expect immediate results need to either chunk queries with LIMIT or handle the async polling pattern explicitly.
Custom objects appear as Salesforce.YourObject__c. Connect AI auto-discovers them on each connection, but newly added custom objects may take up to 10 minutes to appear in getCatalogs output.
For row-level security, configure per-user OAuth on the Connect AI connection. Without it, the agent runs under the connection-owner’s identity and may surface records the requesting user shouldn’t see.
Salesforce field-level security is honored by Connect AI. If an agent queries a field the connection identity can’t read, the field is returned as NULL rather than raising, which can silently degrade agent reasoning. Log query results during development.
Long-form recipes from the CData Knowledge Base.
Full API reference, authentication guides, and configuration details.