Leads, accounts, and contacts
Read approved fields, match identities, check duplicates, and propose records.
Integration workflow
AI Agents for Salesforce
Use Salesforce context for sales and service workflows while respecting object permissions, validation rules, record ownership, and consequential field changes.
What agents can do with Salesforce
Use the system inside a bounded workflow
✓Qualify and route leads using approved CRM fields.
✓Prepare account, contact, opportunity, case, and activity updates.
✓Monitor defined pipeline or service conditions and notify owners.
Objects and actions
Be explicit about what the connection can read or change
Opportunities and activities
Summarize activity and prepare reviewed stage, task, note, or next-step changes.
Cases and queues
Classify permitted cases, draft context, and route them according to service rules.
Common business workflows
Realistic ways to use Salesforce
Lead conversion preparation
Validate required fields, match existing accounts, recommend routing, and present the conversion package for sales review.
Opportunity hygiene
Identify stale next steps or conflicting dates, draft updates from source activity, and ask the owner to approve changes.
Agents and use cases
Connect Salesforce to a defined business job
CRM Assistant
View details →Lead Qualification Agent
View details →Pipeline Monitoring Agent
View details →Related outcome-led workflows
Permissions and security
Start with least privilege
Connection access should be limited to the resources and actions needed for the chosen workflow.
✓Use least-privilege object, field, and record access.
✓Restrict exports, deletions, setup access, and sensitive customer fields.
✓Keep communication consent separate from CRM read or write permission.
Connection notes
Plan for schema, identity, limits, and failure
✓Map custom objects, fields, record types, validation rules, flows, triggers, owners, and duplicate rules.
✓Use a sandbox or limited permission set for workflow validation.
✓Treat failed validations and ambiguous matches as review items.
Human controls
Review before consequential action
Approval gates keep accountable owners involved when a workflow could affect customers, money, permissions, records, or external communication.
✓Require human approval for opportunity value, stage, forecast, owner, conversion, deletion, and bulk changes.
✓Show reviewers the source, prior value, proposed value, and downstream automation risk.
FAQ
Questions to answer before connecting Salesforce
Can an agent bypass validation rules?
No. The workflow should respect configured platform rules and surface rejected changes.
Should opportunity stages update from a call summary alone?
Material stage changes should be proposed with source context and approved by the accountable owner.
Plan a controlled Salesforce workflow.
Discuss the objects, permissions, approvals, and business outcome your implementation needs.