Integrations · CRM & Sales
Put an AI employee to work in Salesforce.
The CRM many mid-market and enterprise sales teams run on. Your AI employee connects to it over Salesforce's web API, works at the approval level you set, and logs every action it takes.
What an AI employee can do in Salesforce
- Your follow-up agent logs every call and email on the Salesforce opportunity, so reps stop typing notes after hours.
- It moves stalled opportunities to the right stage and tells the owner which ones went quiet this week.
- It drafts the next email for each open opportunity and waits for approval before sending.
An example in Salesforce
A commercial roofing contractor gets a call from a property manager about leaks on two warehouse roofs. The agent answers, asks where the leaks are and how long they have been there, and checks Salesforce for an existing Account. It finds the management company, adds the caller as a Contact under it, and opens an Opportunity at the first stage with both addresses in the description. It creates a Task for the estimator to walk the roofs and logs the call on the Opportunity. In the CRM, the property manager's record shows the call summary, the open opportunity and the site visit waiting on a person.
What stays with your people
Your estimators decide the scope and the price, and your sales lead decides which opportunities are worth chasing.
The connection
- How it connects
- Over Salesforce's web API (HTTPS), or an MCP server where one exists. Its key is stored as a secret, scoped to the job, and never written into the AI employee's instructions. Set it up yourself in the Studio, or have us do it.
- What it reads and writes in Salesforce
- Lead, Contact, Account, Opportunity, Task, Case.
- Approval level
- Off, suggest, draft or autonomous, granted by you task by task. Outbound texts and deletions never pass draft.
- On the record
- Every call it makes to Salesforce is logged with what it did and when, so a person can pick up where it left off.
Industries that often run Salesforce
Questions about Salesforce
- Does the agent need admin access to Salesforce?
- No. It gets its own user with a profile or permission set that covers only the objects and fields its job touches, usually Leads, Contacts, Opportunities and Tasks. Your admin sets that up and can narrow it at any time.
- Will it change our opportunity stages or validation rules?
- It works inside the stages, required fields and rules you already have. If you want it to move stages on its own, you say which moves; otherwise it proposes the change and a person makes it.
- Can it work with our custom objects?
- Yes, if its job needs them. AgentWorks builds the agent around how your org is set up, custom objects and fields included, and scopes access to just those.
