Salesforce integration connectivity: Named Credentials, External Services, callouts, events and CDC
Generate Salesforce integration plumbing — credentials, REST/SOAP callouts, Platform Events, CDC — with a 120-point scoring rubric
- What
- Generate Salesforce integration plumbing — credentials, REST/SOAP callouts, Platform Events, CDC — with a 120-point scoring rubric
- Cost
- Free
- Needs
- a Salesforce org and the sf CLI (>= 2.0) plus jq (>= 1.6), npm (>= 9) and python3 (>= 3.10); knowledge of the integration's auth model helps
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @forcedotcom's expert skill for Salesforce integration architecture and runtime plumbing. It covers setting up Named Credentials and External Credentials, registering External Services from OpenAPI specs, outbound REST/SOAP callout patterns, and event-driven design with Platform Events and Change Data Capture (with clear routing rules for when to delegate to the sibling skills for Connected App setup, Apex-only logic, metadata deploy or CDC channel config). The workflow: choose the integration pattern from a decision table, pick a secure auth model (runtime-managed, never hardcoded secrets), generate from XML/Apex asset templates (credentials, callouts, platform events, CDC handlers, SOAP, endpoint security), validate operational safety (timeouts, retries, async strategy, observability), and score the result on a 120-point rubric across six categories (security, error handling, bulkification, architecture, best practices, documentation). Honest caveats: Salesforce-specific — useless outside the Salesforce platform; requires the `sf` CLI plus jq, npm and python3; the skill lives inside a plugin pack and expects its bundled assets and reference guides. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Salesforce integration connectivity is a free Muse skill for generating Salesforce integration plumbing: Named Credentials and External Credentials, External Services registered from OpenAPI specs, outbound REST and SOAP callout patterns, and event-driven design with Platform Events and Change Data Capture. It includes routing rules for delegating to sibling skills, scored with a 120-point rubric.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit e5164d9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Salesforce org and the sf CLI (>= 2.0) plus jq (>= 1.6), npm (>= 9) and python3 (>= 3.10); knowledge of the integration's auth model helps Install "Salesforce integration connectivity: Named Credentials, External Services, callouts, events and CDC" for me. It gives my agent @forcedotcom's integration-playbook: choose the right pattern (Named/External Credential + Apex or Flow, External Service from OpenAPI, async callout, Platform Events, CDC), generate the metadata and Apex from bundled templates, validate operational safety (timeouts, retries, async, logging), delegate to sibling skills when the task is Connected App setup, Apex-only logic or deployment, and score the result on a 120-point rubric. Apache-2.0 licensed. Repository: https://raw.githubusercontent.com/forcedotcom/sf-skills/e5164d94d7511c00fa02a5b8b60754b2361e178f/plugins/builder/integration/skills/integration-connectivity-generate/SKILL.md Pinned version: install the code at commit e5164d94d7511c00fa02a5b8b60754b2361e178f exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "integration-connectivity-generate". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. provide my org credentials and the endpoint/spec details for the integration). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- e5164d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.