Name it, point it at your redirect URLs, pick your scopes. We provision the external client app, hand you the client ID and secret plus a managed package link — no Salesforce setup screens, no partner paperwork.
No credit card, no partner application. Email code in, keys out.
Orbit Sync is ready
7 scopes · 2 redirect URLs
Client ID
3MVG9pRzvMkjMb6nZQhK4yTfNu2wLdEo
Secret
Copied — hidden••••••••••••••••••
01
Sign in with your email
One field, one code. No password to invent, no account form to fill in before you've seen the product.
02
Configure the app
Give it a name, add one or more redirect URLs, and pick what it can reach — data only, data plus sign-in, or everything.
03
Collect your keys
Your client ID (Salesforce's consumer key), its secret and a managed package link. Copy once; we hide the secret straight after.
API access, Refresh tokens, Browser sessions come with every app. The other 10 are yours to add — as a preset or one at a time.
Data only
3Read and write records
Moves data in and out of the CRM and refreshes its own tokens. Never learns who the user is. Best for backend syncs and scheduled jobs.
Data + sign-in
7Records, plus who's asking
Everything in Data only, plus the identity scopes — so people can sign in to your app with their CRM account.
Full access
13Every scope we support
Adds analytics, CMS content, maps and the rest. Quickest to get going — narrow it down before you ship to production.
Scopes without the guesswork
Three presets cover the common cases. Need something specific? Toggle any of the 13 scopes individually.
Copy-once secrets
Keys are masked the moment you copy them, so they can't sit on screen in a shared call. Rotate any time.
Redirect URLs you can edit
Ship to staging today, production next week. Add, edit or remove callback URLs after the app exists.
A managed package link
Every app comes with an install link for the managed package, ready to hand to your customers.
An external client app is Salesforce's framework for letting an outside application sign in to your org over OAuth 2.0. Like the older connected app, a Salesforce external client app holds the OAuth scopes, redirect URLs and the client ID and secret your integration uses — but it's the newer, metadata-based model Salesforce now recommends for new development.
Both hand your integration a consumer key and secret for OAuth, so functionally they overlap. The connected app is Salesforce's original, org-level model; the external client app is the newer replacement, packaged as metadata so it's versionable and easier to distribute. Salesforce is steering new integrations toward external client apps, and that's exactly what Appnigma provisions for you.
A connected app is the legacy way an SFDC org authorizes an external service — it stores the OAuth scopes, callback URLs and the consumer key and secret the service signs in with. The connected app platform predates external client apps, so if you're building something new, start with an external client app instead.
As soon as your external client app is created we show you the client ID — Salesforce calls it the consumer key — and its secret. Copy them once (we mask the secret straight after) and drop them into your OAuth configuration. You can rotate them any time from the app.
All the standard Salesforce OAuth scopes — API access, refresh tokens, OpenID Connect and the rest. Pick one of the three presets, or toggle any scope individually. Data-only, data plus sign-in, or full access: it's your call, and you can narrow it before you ship to production.
No. There's no partner application to fill in and no admin clicking through setup screens. Sign in with your email, name the app, add your redirect URLs and scopes, and collect your client ID and secret — most people are done in about two minutes.
Start with your email — the code we send is the only step between you and a working client ID and secret.