Salesforce

Self-serve

salesforce.comPartialUpdated 27 Oct 2026 · yesterday

You can connect your own org through an External Client App (ECA) in under an hour. Letting any customer's org connect is harder. Since Spring '26 you can't create new Connected Apps by default, so you have to ship your ECA in a second-generation (2GP) managed package. Each customer org then installs that package, or its admin approves your app. Salesforce doesn't review the app unless you want an AppExchange listing.

Your work: 1–3 days
Waiting on Salesforce: None
First user connects: Today, in about 30–60 minutes, using a free Developer Edition org and a Local ECA

3 not confirmed 12 sources Why this tier How did it go?

.md JSON

Use with your agent

Set up a Salesforce OAuth app for our integration, as far as you can.
Guide: https://oauth-guide.akshatsethi.com/apps/salesforce.md (updated 27 Oct 2026)

Self-serve. Hands-on work: 1–3 days. Waiting on Salesforce: none.

Check these exist first:
- Salesforce org with ECA permission [human]
- Redirect URI [agent]

Needed later, not now:
- Dev Hub org and namespace org (for launch)
- Salesforce CLI (for launch)
- Customer admin cooperation (for launch)

Steps, in order:
1. [human] Sign up for a Developer Edition org
2. [agent] Create an External Client App. In Setup, open External Client App Manager and create a new app. Choose Local for single-org testing, or Packaged if you will distribute it. Enable OAuth and enter your redirect URI. Watch out: New Connected Apps are disabled by default since Spring '26. Don't follow older guides that tell you to create one in App Manager.
3. [human] Copy consumer key and secret into your client
4. [agent] Test a connection with your own org. Run the authorization code flow, approve access, and call an API endpoint using the returned instance_url. Watch out: Changes to ECA settings may take a few minutes to apply.
5. [human] Set up a Dev Hub and register a namespace
6. [agent] Package the Packaged ECA in a 2GP package. Create the ECA in the Dev Hub with Distribution State set to Packaged. Then use the CLI to create a managed package, retrieve the ECA metadata, create a package version and promote it to released. Leave the global OAuth settings out of the package and keep them in the Dev Hub. Watch out: One community report says a packaged ECA failed in subscriber orgs with OAUTH_AUTHORIZATION_BLOCKED 'Cross-org OAuth flows are not supported'. Check how the OAuth link is configured in an installed test org before you launch.
7. [human] Give customers the package install URL
8. [human] Optionally submit for AppExchange security review

Rules:
- Do [agent] steps yourself. Steps in Salesforce's dashboard need a browser I'm signed in to; without one, give me the exact clicks and values instead, then carry on with the code.
- At each [human] or [provider] step, stop and tell me exactly what's needed.
- Never put client secrets in chat, code or commits. I paste them into our OAuth client or secret manager myself.
- Claims marked Inferred or low confidence in the guide are unverified. Check them and tell me what you find.
- If the guide doesn't match what you see (a page, field or requirement), tell me and report it so it gets fixed: POST https://oauth-guide.akshatsethi.com/api/reports with {"app": "salesforce", "step": 2, "message": "what you saw"} (step is optional), or call the report_problem MCP tool. Never put secrets or personal data in a report.
- When setup ends (users can connect, or it's waiting on Salesforce's review) or you can't get past a step, report how it went so the guide improves: POST https://oauth-guide.akshatsethi.com/api/reports with {"app": "salesforce", "outcome": "worked" | "waiting" | "stuck", "step": 3, "message": "what happened"}, or call the report_setup MCP tool. Stopping for me at a [human] step isn't stuck: don't report that.
- Finish with what's done, the redirect URI and scopes used, and what's left before public launch.

Paste into Claude Code, Cursor or any agent.

Salesforce

Plan

SetupBefore you start

BuildYour org

LaunchCustomer orgs

Why self-serve

When you get stuck

Not confirmed

Sources

Feedback

Salesforce

Plan

SetupBefore you start

BuildYour org

LaunchCustomer orgs

Why self-serve

When you get stuck

Not confirmed

Sources

Feedback