Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 06:00 UTC
| 1 | ## How do I set up custom OAuth credentials for Salesforce? |
| 2 | |
| 3 | Use your own Salesforce app when you want your app name on the consent screen, your own scopes, or control over the org's app policies. New orgs use External Client Apps; older orgs can still use Connected Apps. |
| 4 | |
| 5 | ### Create the Salesforce app |
| 6 | |
| 7 | If you don't have an org to test in, sign up for a free [Salesforce Developer Edition](https://developer.salesforce.com/signup). |
| 8 | |
| 9 | **Option A: External Client App** |
| 10 | |
| 11 | 1. In Salesforce, click the gear icon → **Setup**. Search **App Manager** in **Quick Find** and open it. |
| 12 | 2. Click **New External Client App**. Enter an **App Name** (the **API Name** fills in), a **Contact Email**, and keep **Distribution State** as **Local**. |
| 13 | |
| 14 |  |
| 15 | |
| 16 |  |
| 17 | |
| 18 | 3. Expand **OAuth Settings** and check **Enable OAuth**. |
| 19 | 4. Set **Callback URL** to `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the auth config's `oauth_redirect_uri` field. |
| 20 | 5. Add OAuth scopes. The default auth config requests `full`, `refresh_token`, and `openid`, so select **Full access (full)**, **Perform requests at any time (refresh_token, offline_access)**, and **Access unique user identifiers (openid)**. |
| 21 | 6. Under security, keep **Require Secret for Web Server Flow** and **Require Secret for Refresh Token Flow** checked. Uncheck **Require PKCE** unless you plan to use PKCE. |
| 22 | |
| 23 |  |
| 24 | |
| 25 | 7. Save. Open the app's **Settings** tab → **OAuth Settings** → **Consumer Key and Secret** and copy the **Consumer Key** (client ID) and **Consumer Secret**. |
| 26 | |
| 27 | **Option B: Connected App** |
| 28 | |
| 29 | 1. In Setup, search **External Client App Settings** in **Quick Find** and turn on **Allow creation of Connected Apps**. Then click **New Connected App**. |
| 30 | |
| 31 |  |
| 32 | |
| 33 | 2. Enter a **Connected App Name** and **Contact Email**. |
| 34 | |
| 35 |  |
| 36 | |
| 37 | 3. Under **API (Enable OAuth Settings)**, check **Enable OAuth Settings** and set **Callback URL** to `https://backend.composio.dev/api/v1/auth-apps/add`. |
| 38 | 4. Add the same scopes as in Option A: `full`, `refresh_token, offline_access`, and `openid`. Add others such as `api` or `id, profile, email` if your tools need them. |
| 39 | 5. Keep the web server flow and refresh token flow enabled with **Require Secret for Web Server Flow** checked, and save. Salesforce can take about 10 minutes to provision a new Connected App. |
| 40 | 6. In **App Manager**, open the app's row menu → **View** → **Manage Consumer Details**, verify your identity if asked, and copy the **Consumer Key** and **Consumer Secret**. |
| 41 | |
| 42 |  |
| 43 | |
| 44 |  |
| 45 | |
| 46 | ### Create the auth config in Composio |
| 47 | |
| 48 | 1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-salesforce), go to **Auth Configs** → **Create** and select **Salesforce**. Salesforce Data 360 and Salesforce Service Cloud are separate toolkits. |
| 49 | |
| 50 |  |
| 51 | |
| 52 |  |
| 53 | |
| 54 | 2. Choose **OAuth 2.0** and **Your Own Credentials**. Paste the Consumer Key as the client ID and the Consumer Secret as the client secret. Keep the redirect URI as the value you registered in Salesforce. Click **Create Auth Config**. |
| 55 | |
| 56 |  |
| 57 | |
| 58 | 3. Click **Connect Account** and fill in the connection fields: |
| 59 | - **Subdomain**: the part of your Salesforce URL before `.salesforce.com`. Most orgs can keep the default `login`; Composio detects your instance after you sign in. If your org requires My Domain login, enter the My Domain part, such as `acme.my` for `acme.my.salesforce.com` (search **My Domain** in Setup). For a sandbox, enter `test`. |
| 60 | - **Instance endpoint**: the API version path. Keep the default `/services/data/v67.0` unless your org needs another version. |
| 61 | |
| 62 | 4. Sign in to Salesforce, review the permissions, and click **Allow**. Confirm the account shows **Active** on the auth config's **Connected Accounts** tab. |
| 63 | |
| 64 | See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow. |
| 65 | |
| 66 | ### IP allowlists |
| 67 | |
| 68 | If the app uses **Enforce Refresh Token IP Allowlist**, or your org restricts logins with **Login IP Ranges** or **Network Access** trusted IPs, add the four [Composio outbound IP addresses](/docs/security/outbound-ips). For an External Client App, open **External Client App Manager**, choose **Edit Settings** from the app's row menu, expand **OAuth Settings**, and under **Refresh Token IP Allowlist** click **+** for each address, with the same value as the start and end IP. Add the addresses and wait 30 to 45 minutes before you turn on enforcement. Otherwise token refreshes fail with `IP restricted by the app developer` (see below). |
| 69 | |
| 70 |  |
| 71 | |
| 72 |  |
| 73 | |
| 74 | Some orgs also set **Limit Idle Refresh Token Time-to-Live (TTL)** to 30 days. In those orgs, a connection that isn't used for 30 days expires and has to be reconnected. |
| 75 | |
| 76 | ## `URL_NOT_RESET` usually means Salesforce subdomain was not configured and defaulted to `login` |
| 77 | |
| 78 | `URL_NOT_RESET` can happen when the Salesforce org requires a specific My Domain value but the connection is using the generic `login` default or an incomplete subdomain. The default `login` value is fine for most Salesforce flows, but for org-specific failures recheck the Salesforce domain/subdomain values on the connection, pass the correct My Domain subdomain, and retry on the latest toolkit version if the issue was seen on an older pinned version. |
| 79 | |
| 80 | ## Why do I see `OAUTH_APPROVAL_ERROR_GENERIC` or `app must be installed into org` in Salesforce OAuth? |
| 81 | |
| 82 | These errors usually mean Salesforce is blocking OAuth because the connected app has not been installed or approved for the org. The user may see `OAUTH_APPROVAL_ERROR_GENERIC`, or the callback URL may include `error=invalid_client&error_description=app+must+be+installed+into+org`. |
| 83 | |
| 84 | Ask a Salesforce org admin to approve or install the connected app. In Salesforce Setup, search for **External Client App Settings** or **OAuth Connected App Usage**, find the app, and use the install/approval action shown by Salesforce. After the admin approves the app, the user should retry the OAuth connection. |
| 85 | |
| 86 |  |
| 87 | |
| 88 |  |
| 89 | |
| 90 | ## Why do I see `invalid_grant` with `ip restricted by app developer`? |
| 91 | |
| 92 | Your Salesforce connected app or external client app only accepts requests from trusted IP addresses, and Composio's request came from an address that isn't on the list. New connections fail during OAuth, and existing connections expire when their tokens refresh. |
| 93 | |
| 94 | Add all four [Composio outbound IP addresses](/docs/security/outbound-ips) to the app's IP allowlist, including its refresh token IP allowlist if it has one. Add each address as its own range, with the same start and end IP. Alternatively, set the app's IP relaxation policy to relax IP restrictions. |
| 95 | |
| 96 | After you update the allowlist, ask affected users to reconnect. Connections that expired don't recover on their own. |
| 97 | |
| 98 | ## Salesforce allows only five active refresh tokens per user per app |
| 99 | |
| 100 | Salesforce allows only five active refresh tokens per user per connected app. When the same Salesforce user connects a sixth time, Salesforce can revoke the oldest refresh token, which makes older Composio connected accounts fail with token errors. If the consent screen says you've already granted access five times, clicking **Allow** revokes the oldest approval. To keep that connection, click **Deny** and revoke an approval you no longer need first. Also check whether the user changed their password, revoked the app, changed connected app refresh-token policy away from `valid until revoked`, or has org-level session policies that invalidate tokens. |
| 101 | |
| 102 | ## How do I query relationships like Pricebooks and Opportunities? |
| 103 | |
| 104 | Use SOQL subqueries to traverse relationships. For example, Products → Pricebooks → Opportunities: |
| 105 | |
| 106 | ```sql |
| 107 | SELECT Id, Name, |
| 108 | (SELECT Id, Quantity, UnitPrice, TotalPrice, PricebookEntry.Product2.Name FROM OpportunityLineItems) |
| 109 | FROM Opportunity |
| 110 | ``` |
| 111 | |
| 112 | ## What happens to deprecated Salesforce tools? |
| 113 | |
| 114 | Deprecated tools continue to work until removed. Check tool descriptions for "DEPRECATED:" markers. |
| 115 | |
| 116 | ## Why can't I find items I created in Salesforce? |
| 117 | |
| 118 | Created records may not appear in a given Salesforce view. Use search to confirm they exist. |