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

Building Sf Integrations

  • 2.4k installs
  • 763 repo stars
  • Updated July 24, 2026
  • forcedotcom/sf-skills

building-sf-integrations designs Salesforce Named Credentials, External Services, callouts, Platform Events, and CDC integration patterns.

About

The building-sf-integrations skill covers Salesforce integration architecture and runtime plumbing including Named Credentials, External Credentials, External Services from OpenAPI specs, REST and SOAP callout patterns, Platform Events, and Change Data Capture. It owns metadata for namedCredential-meta.xml, outbound callouts, event-driven design, and sync versus async pattern selection while delegating Connected App OAuth, pure Apex logic, metadata deploy, and data import to sibling skills. The workflow chooses integration pattern by need, selects secure auth models without hardcoded secrets, generates from template assets under named-credentials, callouts, platform-events, and cdc folders, validates timeout retry and logging safety, and hands off deployment to deploying-metadata. High-signal rules forbid synchronous trigger callouts, require explicit timeouts, plan retries and dead-letter strategies, and prefer External Credentials for new development. Anti-patterns include missing request logging and mixing auth setup with runtime design.

  • Owns Named Credentials, External Services, Platform Events, and CDC design.
  • Never hardcode credentials; prefer Named and External Credential models.
  • Forbid synchronous callouts from triggers; use async patterns instead.
  • Template assets for callouts, platform events, CDC, and SOAP patterns.
  • Delegates Connected App OAuth to configuring-connected-apps skill.

Building Sf Integrations by the numbers

  • 2,395 all-time installs (skills.sh)
  • +7 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #217 of 4,386 Backend & APIs skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

building-sf-integrations capabilities & compatibility

Capabilities
integration pattern selection sync vs async vs e · named and external credential metadata templates · external service openapi registration guidance · platform events and cdc architecture patterns · operational safety for timeout retry and logging
Works with
salesforce
Use cases
api development · orchestration
From the docs

What building-sf-integrations says it does

never hardcode credentials
SKILL.md
do not do synchronous callouts from triggers
SKILL.md
prefer External Credentials architecture for new development when supported
SKILL.md
npx skills add https://github.com/forcedotcom/sf-skills --skill building-sf-integrations

Add your badge

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

Listed on Skillselion
Installs2.4k
repo stars763
Security audit2 / 3 scanners passed
Last updatedJuly 24, 2026
Repositoryforcedotcom/sf-skills

How do I set up secure Salesforce outbound API callouts and event-driven integrations?

Design Salesforce integration plumbing with Named Credentials, External Services, Platform Events, and CDC patterns.

Who is it for?

Salesforce architects wiring authenticated callouts, External Services, or CDC subscribers.

Skip if: Skip for Connected App OAuth setup, pure SOQL, data import, or CDC channel membership metadata alone.

When should I use this skill?

User sets up Named Credentials, External Services, REST callouts, Platform Events, or CDC in Salesforce.

What you get

Integration pattern choice, credential metadata templates, async callout design, and operational safety checklist.

  • Apex Callout retry handler class
  • Retryable error classification logic

By the numbers

  • Handles three failure classes: network timeouts, 5xx server errors, and 429 rate limiting

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

Forks & variants (1)

Building Sf Integrations has 1 known copy in the catalog totaling 523 installs. They canonicalize to this original listing.

How it compares

Use building-sf-integrations when you need Apex-native retry and Queueable backoff rather than middleware-side retry outside Salesforce.

FAQ

Can I make synchronous callouts from Apex triggers?

No. Use async callout patterns for trigger-originated outbound work.

How should secrets be stored?

Never hardcode credentials; use Named Credentials and External Credentials for runtime-managed auth.

When use External Services vs hand-written callouts?

External Services for OpenAPI spec-driven clients; Named Credential callouts for custom Apex or Flow HTTP.

Is Building Sf Integrations safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Backend & APIsintegrationsbackend

This week in AI coding

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

unsubscribe anytime.