Skip to content

Salesforce

Artific Connect · Salesforce gives a key four tools over Salesforce's own REST API: run a SOQL query, read one record, create a record and update a record. Salesforce's remote MCP server needs the customer's own org to admit a third party's OAuth client, which is not one-click and unverified today, so this bundle reaches the REST API instead, run as your organisation's own integration user rather than as a named person. It installs from the Marketplace like any other bundle.

What you get

One toolset, salesforce, holding the four connectors, plus a skill that tells the model SOQL basics and what to confirm before writing.

What you supply at install

Every call runs against your org's own My Domain, one host under all four connectors, so this bundle asks for it once:

  • salesforce_my_domain — paste https://<your-mydomain>.my.salesforce.com with your own My Domain filled in. Every connector below adds its own path to this one address (a query's /services/data/v61.0/query, a record's /services/data/v61.0/sobjects/{sobject}/{id}, and so on) — you never see or edit those paths yourself.

And salesforce_credential, your own External Client App on the OAuth 2.0 client-credentials grant, with an integration user assigned to it in Salesforce's own setup:

{
  "type": "oauth_client_credentials",
  "token_url": "https://<your-mydomain>.my.salesforce.com/services/oauth2/token",
  "client_id": "<consumer key>",
  "client_secret": "<consumer secret>"
}

token_url must name the same My Domain as salesforce_my_domain above. Core does not derive one from the other — a credential's fields are always supplied whole, never templated from a parameter — so a mismatch here authenticates against the wrong org, or nothing at all.

Until both are supplied the subscription waits at needs configuration.

Before it works

Your administrator has to allow your org's My Domain host in the key's own egress policy.

What your Salesforce admin sets up

In Setup, create an External Client App, enable OAuth, turn on the Client Credentials Flow, and assign a running user (the "integration user") whose permissions decide what every call through this bundle may read or write. The consumer key and secret are what you paste above.

Good to know

  • Verified 2026-09-24 on help.salesforce.com: External Client Apps support the OAuth 2.0 client-credentials flow with an assigned integration user, and the token endpoint must be your org's own My Domain URL — login.salesforce.com and test.salesforce.com are refused for this grant.
  • Not verified: the exact SOQL API version to pin (v61.0 above); an org on an older or newer release may want a different one, and each connector's own path can be forked to change it.
  • The mark: this bundle's card still uses Artific's own placeholder. Salesforce's trademark and copyright usage guidelines require approval before a partner may display the logo, and this deployment has not sought it (checked 2026-09-24).