Salesforce, without opening Salesforce.
Read-only accounts, contacts, leads, opportunities and the reports your team already built.
In your channel
Ask Ray for something in Salesforce and it posts this card in the thread. One click, and the task you asked for carries on where it left off.
What Ray can and cannot do in Salesforce
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
Runs on its own
What Ray reads in Salesforce
- Get account
- Get contact
- Get lead
- Get note
- Get opportunity
- Get report instance
- Get user info
- List accounts
- List contacts
- List leads
- List notes
- List opportunities
- List reports
- Run report
- Search accounts
- Search contacts
- Search leads
- Search notes
- Search opportunities
- Search tasks
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Apply the lead assignment rules to Salesforce lead
- Link Salesforce contact
- Complete Salesforce task
- Add an account to Salesforce
- Add a contact to Salesforce
- Add a lead to Salesforce
- Add a note in Salesforce
- Create a Salesforce opportunity
- Create a Salesforce task
- Log a call in Salesforce
- Log an email in Salesforce
- Send an email from Salesforce
- Update Salesforce account
- Update Salesforce contact
- Update Salesforce lead
- Update Salesforce note
- Update Salesforce opportunity
- Update Salesforce task
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, and no setting turns that off.
Not on the list
Things Ray is never handed
These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.
- Delete account
- Close or abort job
- Execute global quick action
- Delete campaign
- Execute invocable action
How Ray works with Salesforce
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Salesforce
One click, right where you asked. Ray posts a connect card, you authorise Salesforce with your own account, and the work you asked for picks up where it left off.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Approve, and it lands
Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.
Priya
@Ray the checkout bug is back. Take a look in Salesforce, and tell Dana it is being looked at.
Apply the lead assignment rules to Salesforce lead
- Waiting on
- your approval
What does connecting Salesforce to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Salesforce and it can do the Salesforce part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
Every person on the team connects their own Salesforce account, so Ray can only reach what that person can already reach, and the history in Salesforce shows who actually asked.
Security and permissions
- You authorise Salesforce on its own login screen. Your password never passes through Ray.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- Disconnect Salesforce in a message, or uninstall Ray and every connection it held is revoked.
More crm & sales integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Salesforce.
Free to start, no credit card, and it asks before it acts.