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/event-subscriber-trigger.trigger

View on GitHub
/**
 * @description Platform Event Subscriber Trigger for {{EventName}}__e
 *
 * Use Case: React to published Platform Events
 * - Process incoming events from other systems
 * - Sync data based on events
 * - Trigger downstream processes
 *
 * Key Concepts:
 * - Platform Event triggers run in their own execution context
 * - Events are processed in batches (up to 2000 for High Volume)
 * - ReplayId enables resuming from failures
 * - SetResumeCheckpoint ensures durability
 *
 * IMPORTANT:
 * - Triggers on Platform Events only fire on AFTER INSERT
 * - Events are immutable (cannot be updated or deleted)
 * - Triggers run as Automated Process user
 *
 * @author {{Author}}
 * @date {{Date}}
 */
trigger {{EventName}}Subscriber on {{EventName}}__e (after insert) {

    // Track last processed replay ID for durability
    String lastReplayId = '';

    // Process each event
    for ({{EventName}}__e event : Trigger.new) {
        // Store replay ID for checkpoint
        lastReplayId = event.ReplayId;

        try {
            // Log event receipt
            System.debug(LoggingLevel.DEBUG,
                'Processing event: ' + event.Correlation_Id__c +
                ' Operation: ' + event.Operation__c +
                ' ReplayId: ' + event.ReplayId);

            // Route to handler based on operation
            switch on event.Operation__c {
                when 'CREATE' {
                    {{EventName}}Handler.handleCreate(event);
                }
                when 'UPDATE' {
                    {{EventName}}Handler.handleUpdate(event);
                }
                when 'DELETE' {
                    {{EventName}}Handler.handleDelete(event);
                }
                when else {
                    // Unknown operation - log and continue
                    System.debug(LoggingLevel.WARN,
                        'Unknown operation: ' + event.Operation__c +
                        ' for event: ' + event.Correlation_Id__c);
                }
            }

        } catch (Exception e) {
            // Log error but continue processing other events
            // Don't throw - that would cause retry of ALL events in batch
            System.debug(LoggingLevel.ERROR,
                'Error processing event ' + event.Correlation_Id__c + ': ' + e.getMessage());
            System.debug(LoggingLevel.ERROR, 'Stack: ' + e.getStackTraceString());

            // Consider: Create error log record for monitoring
            // {{EventName}}ErrorLogger.logError(event, e);
        }
    }

    // Set resume checkpoint for durability
    // If trigger fails after this point, processing resumes from this ReplayId
    if (String.isNotBlank(lastReplayId)) {
        EventBus.TriggerContext.currentContext().setResumeCheckpoint(lastReplayId);
    }
}

/*
 * ============================================================================
 * PLATFORM EVENT TRIGGER BEST PRACTICES
 * ============================================================================
 *
 * 1. ALWAYS set resume checkpoint
 *    - Call setResumeCheckpoint() with the last processed ReplayId
 *    - Ensures events aren't lost if trigger fails mid-batch
 *
 * 2. DON'T throw exceptions
 *    - Unhandled exceptions cause entire batch to retry
 *    - Catch errors per-event and log them
 *    - Continue processing remaining events
 *
 * 3. Keep processing lightweight
 *    - Avoid SOQL/DML in loops
 *    - Collect data, then do bulk DML outside loop
 *    - Consider queueing heavy work via Queueable
 *
 * 4. Handle duplicates
 *    - At-least-once delivery means duplicates possible
 *    - Use Correlation_Id__c to detect/dedupe
 *    - Design handlers to be idempotent
 *
 * 5. Monitor failures
 *    - Log errors to custom object for visibility
 *    - Set up alerts for processing failures
 *    - Review Event Delivery Failures in Setup
 *
 * ============================================================================
 */
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: 471kUpdated 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