integration-connectivity-generate

Generate Salesforce Named Credentials, callouts, Platform Events, and CDC integration patterns.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/padjei/SF_Build --skill integration-connectivity-generate-padjei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: integration-connectivity-generate
Source: https://github.com/padjei/SF_Build/tree/main/.claude/skills/integration-connectivity-generate
Command: npx skills add https://github.com/padjei/SF_Build --skill integration-connectivity-generate-padjei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Building Salesforce integrations requires juggling authentication metadata, callout code, event-driven patterns, and security rules, and mistakes like hardcoded secrets or synchronous trigger callouts cause production failures. This Skill generates secure, validated integration artifacts with a 120-point scoring rubric. ## Core Features & Use Cases - Credential Generation: Creates Named Credential and External Credential metadata for OAuth 2.0, JWT Bearer, Certificate, and API Key authentication, plus automation scripts that configure credentials via ConnectApi without manual UI steps. - Callout & Event Patterns: Produces REST/SOAP callout Apex classes (sync, Queueable, retry with exponential backoff), External Services from OpenAPI specs, Platform Event publishers/subscribers, and Change Data Capture handlers. - Use Case: You need to sync closed-won Opportunities to an external ERP. The skill generates an External Credential, a Queueable callout class with retry logic, and endpoint security metadata, then scores the result across Security, Error Handling, Bulkification, Architecture, Best Practices, and Documentation. ## Quick Start Ask the skill to create a Named Credential and callout class for your external API, specifying the authentication method and whether the callout is synchronous or trigger-originated.

Frequently Asked Questions about integration-connectivity-generate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Salesforce Named Credential with OAuth or API key authentication?▼

The skill generates Named Credential and External Credential XML metadata for OAuth 2.0, JWT Bearer, Certificate, and API Key auth. After deploying the metadata, run the configure-named-credential.sh script to store the secret securely via ConnectApi without using the Setup UI.

How do I make a REST callout from a Salesforce trigger?▼

Synchronous callouts fail in trigger context, so the skill generates a Queueable class implementing Database.AllowsCallouts that the trigger enqueues. The template includes batching, timeout configuration, and Named Credential-based authentication.

Platform Events vs Change Data Capture in Salesforce: which should I use?▼

Use Platform Events for custom business events with custom fields and full publishing control. Use Change Data Capture for automatic record change notifications and external data synchronization, since it requires no publishing code and fires on DML automatically.

Does the skill support retry logic for failed Salesforce callouts?▼

Yes, it provides a retry handler template with exponential backoff and a Queueable chaining pattern, since Apex has no sleep function. It retries on 5xx server errors and network failures but not on 4xx client errors, and recommends idempotency keys.

What are the limitations of Platform Events in Salesforce?▼

Platform Events allow 2,000 publishes per transaction, 1 MB message size, and retention of 72 hours for standard-volume or 24 hours for high-volume events. High-volume events use at-least-once delivery, so subscribers must be idempotent.

When should I not use this integration skill?▼

Delegate Connected App OAuth configuration to integration-connectivity-connected-app-configure, pure Apex business logic to platform-apex-generate, data import/export to platform-data-manage, and CDC channel membership metadata to integration-eventing-cdc-configure.