Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
forcedotcom avatar

Building Sf Integrations

  • 523 installs
  • 787 repo stars
  • Updated August 5, 2026
  • forcedotcom/afv-library

This is a copy of building-sf-integrations by forcedotcom - installs and ranking accrue to the original listing.

building-sf-integrations is a Salesforce AFV skill that configures Named Credentials, External Services, REST/SOAP callouts, Platform Events, and CDC with 120-point scoring for developers wiring external systems into Sal

About

building-sf-integrations is a forcedotcom/afv-library Claude Code skill for Salesforce integration architecture and runtime plumbing with a 120-point scoring rubric. The skill covers Named Credentials, External Credentials, External Services, REST and SOAP callout patterns, Platform Events, and Change Data Capture, and triggers when developers touch .namedCredential-meta.xml or set up CDC channels. It explicitly excludes Connected App OAuth configuration, Apex-only logic, standard CRM data import, and PlatformEventChannel membership metadata that belongs in sibling AFV skills. Developers reach for building-sf-integrations when standing up secure outbound callouts, event-driven integrations, or CDC subscriptions in a Salesforce org. The scoring model gives agents a concrete checklist instead of ad hoc integration advice, reducing misconfigured credentials and unsafe callout patterns in enterprise orgs.

  • 120-point integration architecture scoring rubric
  • Handles Named Credentials, External Credentials, and .namedCredential-meta.xml files
  • Guides REST/SOAP callout patterns and External Service registration from OpenAPI specs
  • Designs Platform Events and Change Data Capture event-driven flows
  • Enforces sync vs async integration pattern decisions with clear tradeoffs

Building Sf Integrations by the numbers

  • 523 all-time installs (skills.sh)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/forcedotcom/afv-library --skill building-sf-integrations

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs523
repo stars787
Last updatedAugust 5, 2026
Repositoryforcedotcom/afv-library

How do you configure Salesforce Named Credentials and callouts?

Correctly configure Salesforce Named Credentials, External Services, REST/SOAP callouts, Platform Events, and Change Data Capture using battle-tested architecture

Who is it for?

Salesforce developers implementing outbound REST/SOAP integrations, Platform Events, or Change Data Capture in enterprise orgs.

Skip if: Developers configuring Connected App OAuth or writing Apex-only business logic should use configuring-connected-apps or generating-apex instead.

When should I use this skill?

A task sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or edits .namedCredential-meta.xml.

What you get

Scored integration designs, Named Credential metadata, External Service definitions, and Platform Event or CDC channel configurations.

  • Scored integration design
  • Named Credential metadata
  • CDC and Platform Event configurations

By the numbers

  • Uses a 120-point scoring rubric for Salesforce integration architecture

Files

SKILL.mdMarkdownGitHub ↗

building-sf-integrations: Salesforce Integration Patterns Expert

Use this skill when the user needs integration architecture and runtime plumbing: Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, CDC, and event-driven integration design.

When This Skill Owns the Task

Use building-sf-integrations when the work involves:

  • .namedCredential-meta.xml or External Credential metadata
  • outbound REST/SOAP callouts
  • External Service registration from OpenAPI specs
  • Platform Events, CDC, and event-driven architecture
  • choosing sync vs async integration patterns

Delegate elsewhere when the user is:

  • configuring the OAuth app itself → configuring-connected-apps
  • writing Apex-only business logic → generating-apex
  • deploying metadata → deploying-metadata
  • importing/exporting data → handling-sf-data

---

Required Context to Gather First

Ask for or infer:

  • integration style: outbound callout, inbound event, External Service, CDC, platform event
  • auth method
  • sync vs async requirement
  • system endpoint / spec details
  • rate limits, retry expectations, and failure tolerance
  • whether this is net-new design or repair of an existing integration

---

Recommended Workflow

1. Choose the integration pattern

NeedDefault pattern
authenticated outbound API callNamed Credential / External Credential + Apex or Flow
spec-driven API clientExternal Service
trigger-originated calloutasync callout pattern
decoupled event publishingPlatform Events
change-stream consumptionCDC

2. Choose the auth model

Prefer secure runtime-managed auth:

  • Named Credentials / External Credentials
  • OAuth or JWT via the right credential model
  • no hardcoded secrets in code

3. Generate from the right templates

Use the provided assets under:

  • assets/named-credentials/
  • assets/external-credentials/
  • assets/external-services/
  • assets/callouts/
  • assets/platform-events/
  • assets/cdc/
  • assets/soap/

4. Validate operational safety

Check:

  • timeout and retry handling
  • async strategy for trigger-originated work
  • logging / observability
  • event retention and subscriber implications

5. Hand off deployment or implementation details

Use:

  • deploying-metadata for deployment
  • generating-apex for deeper service / retry code
  • generating-flow for declarative HTTP callout orchestration

---

High-Signal Rules

  • never hardcode credentials
  • do not do synchronous callouts from triggers
  • define timeout behavior explicitly
  • plan retries for transient failures
  • use middleware / event-driven patterns when outbound volume is high
  • prefer External Credentials architecture for new development when supported

Common anti-patterns:

  • sync trigger callouts
  • no retry or dead-letter strategy
  • no request/response logging
  • mixing auth setup responsibilities with runtime integration design

---

Output Format

When finishing, report in this order: 1. Integration pattern chosen 2. Auth model chosen 3. Files created or updated 4. Operational safeguards 5. Deployment / testing next step

Suggested shape:

Integration: <summary>
Pattern: <named credential / external service / event / cdc / callout>
Files: <paths>
Safety: <timeouts, retries, async, logging>
Next step: <deploy, register, test, or implement>

---

Cross-Skill Integration

NeedDelegate toReason
OAuth app setupconfiguring-connected-appsconsumer key / cert / app config
advanced callout service codegenerating-apexApex implementation
declarative HTTP callout / Flow wrappergenerating-flowFlow orchestration
deploy integration metadatadeploying-metadatavalidation and rollout
use integration from Agentforcedeveloping-agentforceagent action composition

---

Reference Map

Start here

  • references/named-credentials-guide.md
  • references/external-services-guide.md
  • references/callout-patterns.md
  • references/rest-callout-patterns.md
  • references/security-best-practices.md

Event-driven / platform patterns

  • references/event-patterns.md
  • references/platform-events-guide.md
  • references/cdc-guide.md
  • references/event-driven-architecture-guide.md
  • references/messaging-api-v2.md

CLI / automation / scoring

  • references/cli-reference.md
  • references/named-credentials-automation.md
  • references/scoring-rubric.md
  • scripts/README.md — automation scripts overview (configure-named-credential.sh, set-api-credential.sh)

Asset templates

  • assets/named-credentials/ — Named Credential XML templates (OAuth, JWT, Certificate, Custom auth)
  • assets/external-credentials/ — External Credential XML templates (OAuth, JWT)
  • assets/external-services/ — External Service registration template and operations guide
  • assets/callouts/ — REST sync, Queueable, retry handler, and HTTP response handler Apex templates
  • assets/platform-events/ — Platform Event definition, publisher, and subscriber templates
  • assets/cdc/ — CDC handler and subscriber trigger templates
  • assets/soap/ — SOAP callout service template and wsdl2apex guide
  • assets/endpoint-security/ — Remote Site Setting and CSP Trusted Site XML templates

Automation hooks

  • hooks/scripts/suggest_credential_setup.py — auto-suggests credential configuration steps when integration files are detected
  • hooks/scripts/validate_integration.py — validates integration patterns before agent responses

---

Output Expectations

When this skill completes an integration task, it produces:

1. Credential metadata — one or more files in assets/named-credentials/ or assets/external-credentials/ filled with org-specific values 2. Callout Apex class — a .cls file using the Named Credential pattern, with async/sync pattern chosen based on context 3. Event/CDC artifacts — Platform Event .object-meta.xml, subscriber trigger, or CDC config (when event-driven pattern is chosen) 4. Endpoint security metadata — Remote Site Setting and/or CSP Trusted Site XML files 5. Scoring report — 120-point score across 6 categories (Security, Error Handling, Bulkification, Architecture, Best Practices, Documentation) 6. Next step — a deployment or testing instruction for the generated artifacts

---

Score Guide

ScoreMeaning
108+strong production-ready integration design
90–107good design with some hardening left
72–89workable but needs architectural review
< 72unsafe / incomplete for deployment

Related skills

How it compares

Use building-sf-integrations for outbound callout and event plumbing; use querying-soql or handling-sf-data for CRM data tasks.

FAQ

What does building-sf-integrations score?

building-sf-integrations applies a 120-point scoring rubric to Salesforce integration architecture covering Named Credentials, External Services, REST/SOAP callouts, Platform Events, and Change Data Capture so agents produce auditable integration designs.

When should building-sf-integrations not trigger?

building-sf-integrations excludes Connected App OAuth setup, Apex-only logic without integration plumbing, standard CRM data import/export, and CDC channel-membership metadata such as PlatformEventChannel—those belong in sibling AFV skills like configuring-connected-apps or handl

Backend & APIsintegrationsbackend

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.