Run your Salesforce org
with a governed agent
Lunen agents query, report on and update Salesforce through Salesforce's hosted MCP servers, in a chat or on a schedule. Every call runs as the member who connected, inside their field-level security and sharing rules, and follows the policy you set for each tool.
Stop working the forecast
one list view at a time
The agent reads opportunities, accounts and cases, and makes the changes you trust it with. You decide, tool by tool, what runs on its own and what waits for a person.
Without Lunen: Getting ready for the forecast call means building a report, exporting it, and asking each rep what changed since last week.
With Lunen: Ask what is in commit this quarter and what moved. The agent queries your opportunities, reads their field history, and answers by owner and stage.
Without Lunen: Open opportunities sit past their close date until someone runs the cleanup report.
With Lunen: A scheduled agent finds every open opportunity with a close date in the past, reads its latest activity, and moves the date when the activity says so, on its own or once a sales manager approves.
Without Lunen: Before a renewal call, a rep clicks through the account, its contacts, open opportunities and cases to piece the story together.
With Lunen: Ask about the account. The agent pulls it with its open opportunities, cases and contacts in one query and writes the brief.
Without Lunen: Giving an AI assistant Salesforce access usually means an integration user with broad permissions, a token in a config file, no policy on what it can change, and no record of who asked.
With Lunen: Each member signs in to Salesforce as themselves. Field-level security, object permissions and sharing rules apply to every call, and Lunen's audit log records who acted and what was approved.
Ask your Salesforce org a question
Ask in plain language and get answers from live Salesforce data, with the same identity, policies and audit log behind every call.
Forecast questions
Ask anything...
Claude Sonnet 4.6What you can do in Salesforce
Work an agent can take on once Salesforce is connected, whether you ask in a chat or put it on a schedule.
Forecast review
Ask what is in commit and best case this quarter. The agent totals opportunities by owner and stage and reads field history to show what moved.
Close date cleanup
Find open opportunities with a close date in the past, read the latest activity on each, and update the date or flag it for the owner.
Account briefs
Pull an account with its open opportunities, cases and key contacts into one brief before a renewal call or a QBR.
Lead hygiene
Find leads missing an owner, a source or a rating, and fill them in from rules you describe.
Case escalation
Find high-priority cases with no response in a day and reassign them to the right queue, with every change in the run log.
Follow-up tasks
Turn a rep's call notes into follow-up tasks on the right opportunity, assigned to the right owner with a due date.
Connected through Salesforce's MCP servers
Salesforce runs the MCP servers on its own platform. An administrator activates one and adds it to Lunen once, and each member then signs in to Salesforce as themselves.
A policy on every Salesforce tool
Each tool on the server has its own place in a Lunen policy. Let queries run unattended and send creates, updates and deletes to a person first, or trust an agent end to end.
Salesforce
- soqlQueryAllow
- findAllow
- getObjectSchemaAllow
- getRelatedRecordsAllow
- createSobjectRecordApprove
- updateSobjectRecordApprove
- deleteSobjectRecordApprove
Pick the server that fits
Salesforce offers fixed bundles: reads only, reads with create and update, deletes, or all of them. A team that only needs answers can connect a server that can't change anything.
Your data model, not a generic one
The agent reads your org's schema before it queries, so custom objects and custom fields work the same way standard ones do.
No integration user
Members sign in through an External Client App you control. Salesforce issues each of them their own token, and a permission set can limit who may connect.
Connected in three steps
- 1In Salesforce Setup, open MCP Servers under API Catalog and activate the server you want.
- 2Create an External Client App with the mcp_api and refresh_token scopes and Lunen's callback URL, then copy its consumer key and secret.
- 3In Lunen, add the server in Settings, then MCP Registry, with that key and secret. Members connect from Connected Services.
Why run your Salesforce agents in Lunen
It acts as the person
Each member signs in to Salesforce as themselves. Field-level security, object permissions and sharing rules apply to every call an agent makes for them.
You decide what runs on its own
Every Salesforce tool has its own policy. Allow the queries a trusted agent runs end to end, and set updates and deletes to Approve so a reviewer sees the record and fields first.
In a chat or on a schedule
Ask about an account when you need an answer, or put the same work on a schedule so close dates are cleaned up before the forecast call.
One record for every tool
Salesforce calls land in the same audit log as every other tool: who acted, which agent ran, what was approved, and which model answered.
Put an agent on your forecast
Lunen is in early access with a small group of design partners. Tell us how your team works in Salesforce and we'll set up a call.