Skip to content

forcedotcom/sf-skills / plugins/builder/integration/skills/integration-connectivity-generate

integration-connectivity-generate

Verified

Salesforce 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).

FileKindSize
README.mdmarkdown3.5 KB
SKILL.mdskill md8.8 KB
assets/callouts/callout-retry-handler.clsother6.0 KB
assets/callouts/http-response-handler.clsother8.5 KB
assets/callouts/rest-queueable-callout.clsother8.8 KB
assets/callouts/rest-sync-callout.clsother7.4 KB
assets/cdc/cdc-handler.clsother8.4 KB
assets/cdc/cdc-subscriber-trigger.triggerother5.3 KB
assets/endpoint-security/example.cspTrustedSite-meta.xmlconfig1.8 KB
assets/endpoint-security/example.remoteSite-meta.xmlconfig1.3 KB
assets/external-credentials/jwt-external-credential.externalCredential-meta.xmlconfig3.2 KB
assets/external-credentials/oauth-external-credential.externalCredential-meta.xmlconfig3.0 KB
assets/external-services/external-service-operations.mdmarkdown5.5 KB
assets/external-services/openapi-registration.externalServiceRegistration-meta.xmlconfig4.8 KB
assets/named-credentials/certificate-auth.namedCredential-meta.xmlconfig2.2 KB
assets/named-credentials/custom-auth.namedCredential-meta.xmlconfig2.2 KB
assets/named-credentials/oauth-client-credentials.namedCredential-meta.xmlconfig1.8 KB
assets/named-credentials/oauth-jwt-bearer.namedCredential-meta.xmlconfig2.2 KB
assets/platform-events/event-publisher.clsother6.4 KB
assets/platform-events/event-subscriber-action.clsother9.5 KB
assets/platform-events/event-subscriber-trigger.triggerother3.9 KB
assets/platform-events/platform-event-definition.object-meta.xmlconfig3.7 KB
assets/soap/soap-callout-service.clsother6.4 KB
assets/soap/wsdl2apex-guide.mdmarkdown6.2 KB
references/callout-patterns.mdmarkdown21.8 KB
references/cdc-guide.mdmarkdown8.2 KB
references/cli-reference.mdmarkdown2.9 KB
references/event-driven-architecture-guide.mdmarkdown10.1 KB
references/event-patterns.mdmarkdown27.2 KB
references/external-services-guide.mdmarkdown8.4 KB
references/messaging-api-v2.mdmarkdown17.9 KB
references/named-credentials-automation.mdmarkdown6.2 KB
references/named-credentials-guide.mdmarkdown7.1 KB
references/platform-events-guide.mdmarkdown6.6 KB
references/rest-callout-patterns.mdmarkdown8.8 KB
references/scoring-rubric.mdmarkdown2.4 KB
references/security-best-practices.mdmarkdown5.9 KB
scripts/README.mdmarkdown2.9 KB
scripts/configure-named-credential.shexecutablescript9.2 KB
scripts/set-api-credential.shexecutablescript4.9 KB
scripts/suggest_credential_setup.pyscript9.3 KB
scripts/templates/setup-credentials-with-csp.shexecutablescript5.9 KB
scripts/validate_integration.pyscript13.4 KB

assets/platform-events/platform-event-definition.object-meta.xml

View on GitHub
<?xml version="1.0" encoding="UTF-8"?>
<!--
    Platform Event Definition Template

    Use Case: Asynchronous, event-driven communication
    - Real-time notifications
    - Decoupled system integrations
    - High-volume data streaming
    - Trigger external processes

    Event Types:
    - StandardVolume: ~2,000 events/hour, standard delivery
    - HighVolume: Millions/day, at-least-once delivery, 24-hour retention

    Publish Behaviors:
    - PublishAfterCommit: Event published after transaction commits (default)
    - PublishImmediately: Event published immediately (use for rollback scenarios)

    Setup Steps:
    1. Replace all {{placeholder}} values
    2. Add fields as needed
    3. Deploy to org
    4. Create publisher (Apex, Flow, Process Builder)
    5. Create subscriber (Trigger, Flow, External via CometD)

    File Location: force-app/main/default/objects/{{EventName}}__e/{{EventName}}__e.object-meta.xml
-->
<CustomObject xmlns="http://soap.sforce.com/2006/04/metadata">
    <!-- Deployment status -->
    <deploymentStatus>Deployed</deploymentStatus>

    <!--
    Event Type:
    - StandardVolume: Up to 2,000 events per hour (included in licenses)
    - HighVolume: Up to millions per day (may require additional entitlement)

    Use HighVolume for:
    - Large-scale integrations
    - IoT data streaming
    - High-throughput scenarios
    -->
    <eventType>HighVolume</eventType>

    <!-- Display labels -->
    <label>{{EventLabel}}</label>
    <pluralLabel>{{EventPluralLabel}}</pluralLabel>

    <!--
    Publish Behavior:
    - PublishAfterCommit: Publish when transaction commits (RECOMMENDED)
      Ensures event only fires if data save succeeds
    - PublishImmediately: Publish right away
      Use when you need event even if transaction rolls back
    -->
    <publishBehavior>PublishAfterCommit</publishBehavior>

    <!-- Event Fields -->

    <!-- Record ID field - link to triggering record -->
    <fields>
        <fullName>Record_Id__c</fullName>
        <label>Record ID</label>
        <description>ID of the Salesforce record that triggered this event</description>
        <type>Text</type>
        <length>18</length>
        <externalId>false</externalId>
    </fields>

    <!-- Operation type field -->
    <fields>
        <fullName>Operation__c</fullName>
        <label>Operation</label>
        <description>The operation that occurred: CREATE, UPDATE, DELETE</description>
        <type>Text</type>
        <length>20</length>
        <externalId>false</externalId>
    </fields>

    <!-- Payload field - JSON data -->
    <fields>
        <fullName>Payload__c</fullName>
        <label>Payload</label>
        <description>JSON payload containing event data</description>
        <type>LongTextArea</type>
        <length>131072</length>
        <visibleLines>5</visibleLines>
    </fields>

    <!-- Correlation ID for tracking -->
    <fields>
        <fullName>Correlation_Id__c</fullName>
        <label>Correlation ID</label>
        <description>Unique ID for tracking related events across systems</description>
        <type>Text</type>
        <length>50</length>
        <externalId>true</externalId>
    </fields>

    <!-- Timestamp field -->
    <fields>
        <fullName>Event_Timestamp__c</fullName>
        <label>Event Timestamp</label>
        <description>When the event occurred</description>
        <type>DateTime</type>
    </fields>

    <!--
    Add more fields as needed for your use case.

    Field Types Supported:
    - Text (up to 255 chars)
    - LongTextArea (up to 131,072 chars)
    - Number
    - Checkbox
    - DateTime
    - Date

    NOT Supported:
    - Lookup/Master-Detail (no relationships)
    - Formula
    - Roll-up Summary
    - Picklist (use Text instead)
    -->
</CustomObject>
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall