Agent skill · forcedotcom

integration-connectivity-connected-app-configure

Salesforce Connected Apps and External Client Apps OAuth configuration with 120-point scoring. Use this skill to configure OAuth flows, JWT bearer auth, Connected Apps, and External Client Apps in Salesforce. TRIGGER when: user configures OAuth flows, JWT bearer auth, Connected Apps, ECAs, or touches .connectedApp-meta.xml / .eca-meta.xml files. DO NOT TRIGGER when: configuring Named Credentials for callouts (use integration-connectivity-generate), reviewing permission policies (use platform-metadata-deploy), or writing Apex token-handling code (use platform-apex-generate).

What it needs

About 6k tokens when loaded.

What this skill does

integration-connectivity-connected-app-configure: Salesforce Connected Apps & External Client Apps Use this skill when the user needs OAuth app configuration in Salesforce: Connected Apps, External Client Apps (ECAs), JWT bearer setup, PKCE decisions, scope design, or migration from older Connected App patterns to newer ECA patterns. Scope In scope: .connectedApp-meta.xml or .eca-meta.xml files OAuth flow selection and callback / scope setup JWT bearer auth, device flow, client credentials, or auth-code decisions Connected App vs External Client App architecture choices Consumer key / secret / certificate handling strategy Out of scope — delegate elsewhere: Configuring Named Credentials or runtime callouts → integration-connectivity-generate Deploying metadata to orgs → platform-metadata-deploy Writing Apex token-handling code → platform-apex-generate --- First Decision: Connected App or External Client App If the need is... Prefer --- --- simple single-org OAuth app Connected App new development with better secret handling External Client App multi-org / packaging / stronger operational controls External Client App straightforward legacy compatibility Connected App Default guidance: Choose ECA for new regulated, packageable, or automation-heavy solutions. Choose Connected App when simplicity and legacy compatibility matter more. Spring '26 note: creation of new Connected Apps is disabled by default in orgs. For new integrations, prefer External Client Apps unless Connected App compatibility is explicitly required. --- Required Inputs Ask for or infer: App type: Connected App or ECA OAuth flow: auth code, PKCE, JWT bearer, device, client credentials Client type: confidential vs public Callback URLs / redirect surfaces Required scopes Distribution model: local org only vs packageable / multi-org Whether certificates or secret rotation are required --- Workflow 1. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills forcedotcom/integration-connectivity-connected-app-configure--705054

View the source on GitHub

Browse the @skills marketplace