Skip to content

Connecting Salesforce

Cora can read your Salesforce records, in the missions you choose. It is read-only. Cora can look up records, run queries and read the related records your own Salesforce login can see, and she cannot create, change or delete anything.

Salesforce needs a little set-up first, because it does not let an app such as Cora register itself. Three people take part, once each:

  1. Your Salesforce admin turns on Salesforce’s read-only server and makes one External Client App for Cora (step 1).
  2. A Cora org admin enters that app’s consumer key and secret, with your My Domain address, on the Connections page (step 2).
  3. Each person then connects their own Salesforce login and shares it with Cora in their missions (step 3).

After that it works like Connecting with the service’s sign-in, and each connection is personal: see Personal connections for the rules. This page uses an invented company, Kestrel Cycles, whose Salesforce My Domain is kestrelcycles.my.salesforce.com.

  • Salesforce Enterprise Edition or above. A free Developer Edition org works too, which is handy for a trial.
  • A Salesforce admin who can change Setup.
  • MCP turned on for the Cora organisation (see Connecting an MCP server), and Connect turned on by the operator.

Step 1: your Salesforce admin sets up Salesforce

Section titled “Step 1: your Salesforce admin sets up Salesforce”
  1. In Salesforce, open Setup and search for MCP Servers (under API Catalog).
  2. Turn on platform/sobject-reads. It is off by default. It can take a couple of minutes to start.

Only turn on sobject-reads. Cora uses no other Salesforce server.

Get the callback address first: a Cora org admin finds it on the Salesforce card in the Organisation setup section of Salesforce’s page on Cora’s Connections page (step 2). It ends in /v1/oauth/callback.

  1. In Setup, open External Client App Manager and choose New External Client App. It must be an External Client App: Salesforce does not let a Connected App sign in to its MCP servers.
  2. Give it a name, such as Cora AI, and a contact email.
  3. Under API (Enable OAuth Settings), choose Enable OAuth.
  4. Callback URL: paste the callback address from Cora, exactly.
  5. OAuth scopes: add exactly these two, and no others:
    • the MCP scope, mcp_api;
    • Perform requests at any time (refresh_token, offline_access), so the sign-in can be renewed.
  6. Under Flow Enablement, leave every box off.
  7. Under Security, turn on:
    • Require Proof Key for Code Exchange (PKCE);
    • Require secret for Web Server Flow;
    • Require secret for Refresh Token Flow;
    • Issue JSON Web Token (JWT)-based access tokens for named users.
  8. Save.
  9. Optional, under Policies: choose who may use the app (for example Admin approved users are pre-authorized, with a permission set for the people who will connect), and how long a sign-in lasts.

A new or changed app can take up to 30 minutes to start working. Until then Salesforce says it does not know the app, and Cora says so too. Wait and try again.

Open the app in External Client App Manager, then Settings, OAuth Settings, and choose Consumer Key and Secret. Salesforce may ask for a verification code. Copy both and give them to the Cora org admin in a safe way, such as a password manager. Do not email or chat them.

Also note the org’s My Domain address: in Setup, search for My Domain and copy the Current My Domain URL, for example kestrelcycles.my.salesforce.com. A sandbox looks like kestrelcycles--uat.sandbox.my.salesforce.com, and a Developer Edition org like kestrel-dev-ed.develop.my.salesforce.com.

  1. In Cora, open Connections on the left rail. Under Needs an admin to set up first, press Set up beside Salesforce. The first section of its page, Organisation setup, has the Salesforce card. It shows the callback address to give your Salesforce admin.
  2. Choose Set up and fill in:
    • My Domain address: for example kestrelcycles.my.salesforce.com (or the sandbox or Developer Edition address);
    • Consumer key;
    • Consumer secret.
  3. Choose Save.

The secret goes straight to the secrets store. Cora never shows it again: the card says only Secret set and the date. Cora uses the app only for your organisation, and only to sign in at that exact My Domain address.

Later you can:

  • Replace secret: when your Salesforce admin makes a new consumer secret. People’s connections keep working.
  • Change: for a different app or a different Salesforce org. Everyone’s Salesforce connection then says Needs reconnect, because their sign-ins belong to the old app.
  • Remove: Cora deletes the secret and stops using every Salesforce connection in the organisation at once.
  1. Open Connections on the left rail and press Connect beside Salesforce.
  2. In the Account section, choose Connect…. The short name (salesforce) and your organisation’s server address are filled in for you. If Organisation setup says Waiting for an org admin, ask one of the org admins it names to do step 2.
  3. In the dialog choose Connect. Salesforce’s own page opens in a new window. Sign in with your normal Salesforce login and choose Allow.
  4. The window closes by itself and the card shows your connection. Finish the sign-in in the same browser you pressed Connect in.
  5. In the Shared with missions section, choose + Share in a mission and pick a mission. Cora can then read Salesforce in that mission, and in no other.

Each person can have one Salesforce connection, and a mission can use one.

Then ask Cora in the mission’s dialogue, for example: “Which of our accounts in Victoria have an open opportunity over $50,000?” or “Show the last five contacts added for Northwind Traders.”

Cora sees only what your own Salesforce login can see, with its sharing rules and field security. Her Salesforce tools are a fixed list of names that only read, kept by Cora herself, not by Salesforce’s labels:

  • the list of objects and each object’s fields;
  • SOQL queries and searches across records;
  • a record’s related records, and the records you used recently;
  • who you are signed in as.

A tool that is not on the list is never switched on, never shared in a mission and never given to Cora, even if Salesforce adds one later. She cannot create, change or delete a record, or change any setting.

  • Every tool call counts against your org’s daily Salesforce API limit. A busy mission uses some of it. Your Salesforce admin can see it under Company Information.
  • Salesforce has said it will charge for MCP use through Flex Credits, and will ask for each agent to be registered. Your organisation pays any Salesforce charges. We will tell you before anything you need to do changes.

The card says Needs reconnect when the sign-in has ended (your Salesforce admin revoked it, or it expired under the app’s policy), or when a Cora org admin changed or removed the sign-in app. Cora skips the connection until you choose Reconnect and sign in again.

  • “Salesforce is not set up for your organisation yet”: a Cora org admin needs to do step 2.
  • “The service does not know your organisation’s sign-in app yet”, or Salesforce’s page says the client identifier is invalid: the app was made or changed less than 30 minutes ago, or the consumer key is wrong. Wait, then try again; if it still fails, ask the org admin to check the key.
  • “The service did not accept your organisation’s sign-in app secret”: the consumer secret is wrong. Ask the org admin to choose Replace secret.
  • Salesforce’s page says the redirect_uri does not match: the callback address in the External Client App is not exactly the one on the Salesforce card.
  • The consumer secret and everyone’s tokens are kept in the secrets store. They never appear in the database, logs, audit entries, prompts or on any page. The API renews tokens; Cora’s worker holds a current access token for one step only.
  • One organisation’s app is used only for that organisation, and only for its own My Domain address.
  • Cora never sees your Salesforce password. You sign in on Salesforce’s page.
  • Only you can use your connection. Org admins can see who owns which connection and where it is shared, and can stop sharing or remove one for safety.
  • Disconnect asks Salesforce to cancel the access, deletes the stored tokens and stops Cora using it in every mission.