Salesforce
Integration · CRM and sales
Salesforce automation with AI agents: what it can do.
An AI agent can query and update Salesforce records such as leads, contacts, opportunities and cases through Salesforce’s APIs, and react to record changes. Access runs through a dedicated integration user and a connected app, and is limited by your edition, your org’s API allowance and its permission sets.
What can an agent do in Salesforce?
Salesforce exposes standard and custom objects through its REST and other APIs, so an agent can work with the same records your team uses, including any custom fields your admin has added.
| Object | What an agent can do |
|---|---|
| Leads | Create leads from conversations, enrich them from approved sources, score and route them. See [lead qualification](/use-cases/lead-qualification/). |
| Accounts and contacts | Match an inbound message to the right account before answering, and keep details current. |
| Opportunities | Summarise activity, flag deals with no recent contact, prepare next-step tasks for the owner. |
| Cases | Classify incoming support requests, suggest a reply from your knowledge base, and route by product or urgency. See [customer support](/use-cases/customer-support/). |
| Reports | Pull data for a weekly pipeline or service summary written in plain language. See [report generation](/use-cases/report-generation/). |
What does a Salesforce integration need?
- An edition that includes API access. Not every edition does by default, so confirm with your Salesforce account team or admin.
- A dedicated integration user, so the agent’s changes are attributed to it and not to a colleague. Salesforce offers a specific licence type for API-only integration users on many editions.
- A connected app (or Salesforce’s newer external client app) to handle authentication, with only the OAuth scopes needed.
- A permission set granting access to the exact objects and fields involved, with field-level security for anything sensitive.
- A sandbox to build and test in before touching production.
Apps listed on AppExchange go through Salesforce’s security review. An integration built only for your org does not.
Plan the build with your Salesforce admin from the start. They own the permission sets and existing automation, and they will need to approve the integration user and connected app in production. Doing that early avoids the common situation where a working integration sits waiting on access changes for weeks.
What are the limits and gotchas?
- API request allowance: each org has a rolling daily limit on API calls, shared by every integration. An agent that polls carelessly can starve your other tools. Prefer events (such as change data capture or platform events) over polling.
- Validation rules and automation: your org’s existing Flows, triggers and validation rules run when the agent saves a record. Test against them, or the agent’s updates will fail or set off unexpected processes.
- Customisation: most Salesforce orgs are heavily customised. Expect scoping to include a review of your objects and fields, not just the standard ones.
- Data residency: where your Salesforce data is hosted depends on your contract. Your agent and its AI model are a separate processing step to document.
Before you connect Salesforce: a checklist.
Connecting Salesforce safely
0 of 8 done
Flow, Salesforce’s own AI, or a custom agent?
Salesforce Flow covers rule-based automation inside Salesforce, and your admin may already know it well. Salesforce also sells its own AI agent product, Agentforce, which is worth evaluating if most of the work stays inside Salesforce and your licences include it.
A custom agent makes more sense when the work spans systems outside Salesforce (WhatsApp, your booking system, accounting), when you want to choose the AI model, or when the job is a narrow one where a dedicated build is cheaper than new licences. Our build vs buy guide goes through that decision.
Which workflow should you start with?
Salesforce projects grow quickly, so pick one workflow with a clear owner and a measurable result. Two good candidates:
- Inbound lead handling. The agent replies to new web or WhatsApp enquiries, asks the qualifying questions, and creates a lead with the answers in structured fields. Measure time to first response and the share of leads sales accepts.
- Case triage. The agent reads new cases, sets category and priority, and drafts a first reply for an agent on your service team to approve. Measure how often the category was right and how much time the draft saved.
Both write to a small number of fields, which keeps the permission set small and the testing manageable. Our scoping guide covers how to turn either into a brief.
Common questions
Can the agent see every record in our org?
Only what its user can see. Salesforce applies the integration user’s profile, permission sets, sharing rules and field-level security to every API call. Give that user access to the objects and fields the workflow needs, and nothing more, and test with the user’s own permissions rather than an admin’s.
Will it work with our custom objects and fields?
Yes, custom objects and fields are available through the API like standard ones, as long as the integration user has access. Part of scoping is listing which fields the agent reads and writes, because custom fields often carry the business rules that matter most.
How does this fit with an existing Salesforce partner?
Work with them. Your Salesforce partner or admin knows your org’s automation and data model, and changes to permission sets or Flows should go through them. A custom agent sits outside Salesforce and connects through the API, so the two pieces of work can run side by side.
Bring us the task.
Tell us what happens today, which tools are involved and where it goes wrong. On a free 30-minute review, we’ll work out whether an agent, an automation or neither is the right fix, and what a sensible first release would be.
Start a project.

Book a call or send us a message. We read everything.
tash@neu.ie
Working with teams in Ireland and worldwide.
Free 30-minute AI review.