forcedotcom/sf-skills / plugins/builder/integration/skills/integration-connectivity-generate
integration-connectivity-generate
VerifiedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use integration-connectivity-connected-app-configure), Apex-only logic (use platform-apex-generate), data import/export (use platform-data-manage), or CDC channel-membership metadata such as PlatformEventChannel, PlatformEventChannelMember, or EnrichedField (use integration-eventing-cdc-configure).
assets/external-credentials/jwt-external-credential.externalCredential-meta.xml
View on GitHub<?xml version="1.0" encoding="UTF-8"?>
<!--
External Credential Template: JWT (API 61+)
Use Case: JWT Bearer authentication for server-to-server
- Machine-to-machine authentication
- Service account integrations
- High-security API access
API Version: 61.0+ (Spring '24+) REQUIRED
Prerequisites:
1. Create certificate in Setup → Certificate and Key Management
2. Register public key with external system
3. Configure JWT claims as required by external API
Setup Steps:
1. Replace all {{placeholder}} values
2. Upload certificate to Salesforce
3. Deploy to org
4. Create Named Credential referencing this External Credential
File Location: force-app/main/default/externalCredentials/{{CredentialName}}.externalCredential-meta.xml
-->
<ExternalCredential xmlns="http://soap.sforce.com/2006/04/metadata">
<label>{{CredentialLabel}}</label>
<!-- JWT Authentication Protocol -->
<authenticationProtocol>Jwt</authenticationProtocol>
<!--
JWT Configuration Parameters
-->
<!-- Issuer claim (iss) - typically your client ID or service identifier -->
<externalCredentialParameters>
<parameterName>issuer</parameterName>
<parameterType>SigningCertificate</parameterType>
<parameterValue>{{CertificateName}}</parameterValue>
</externalCredentialParameters>
<!-- Subject claim (sub) - the identity being asserted -->
<externalCredentialParameters>
<parameterName>subject</parameterName>
<parameterType>Custom</parameterType>
<parameterValue>{{SubjectIdentifier}}</parameterValue>
</externalCredentialParameters>
<!-- Audience claim (aud) - intended recipient of the JWT -->
<externalCredentialParameters>
<parameterName>audience</parameterName>
<parameterType>Custom</parameterType>
<parameterValue>{{AudienceUrl}}</parameterValue>
</externalCredentialParameters>
<!-- Token endpoint for JWT exchange -->
<externalCredentialParameters>
<parameterName>tokenEndpoint</parameterName>
<parameterType>AuthProviderTokenEndpoint</parameterType>
<parameterValue>{{TokenEndpoint}}</parameterValue>
</externalCredentialParameters>
<!-- JWT Expiration (in seconds) -->
<externalCredentialParameters>
<parameterName>expirationOffset</parameterName>
<parameterType>Custom</parameterType>
<parameterValue>3600</parameterValue>
</externalCredentialParameters>
<!-- Named Principal for JWT auth -->
<principals>
<principalName>{{PrincipalName}}</principalName>
<principalType>NamedPrincipal</principalType>
<sequenceNumber>1</sequenceNumber>
</principals>
<!--
JWT Token Flow:
1. Salesforce creates JWT with claims (iss, sub, aud, exp)
2. JWT signed with certificate private key
3. JWT sent to token endpoint
4. External system validates signature with public key
5. Access token returned
6. Access token used for API calls
Custom Claims:
Add additional externalCredentialParameters with parameterType="Custom"
to include custom claims required by your external system.
-->
</ExternalCredential>
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |