sf-integration_skill

This skill helps you design and implement secure Salesforce integrations with Named Credentials, External Services, and event-driven patterns.
  • Python

67

GitHub Stars

3

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill jaganpro/sf-skills --skill sf-integration

  • CREDITS.md3.9 KB
  • README.md3.6 KB
  • SKILL.md22.9 KB

Overview

This skill creates end-to-end Salesforce integrations and rates them with a 120-point validation score. It generates Named Credentials or External Credentials, registers External Services from OpenAPI specs, and scaffolds REST/SOAP callouts, Platform Events, and Change Data Capture subscribers. It is focused on secure, scalable, and deployable integration patterns for new development or migration.

How this skill works

The skill inspects the org API level to decide between legacy Named Credentials and API 61+ External Credentials, then generates metadata templates (credentials, externalServiceRegistration, Apex classes, events, triggers). It produces synchronous and asynchronous callout patterns, WSDL2Apex guidance, event publishers/subscribers, and an automated 120-point scoring audit across security, error handling, bulkification, architecture, best practices, and documentation. It also outputs a recommended deployment order and test/verification steps.

When to use it

  • Setting up new server-to-server or per-user integrations (OAuth, JWT, certificate)
  • Registering External Services from OpenAPI/Swagger specs
  • Implementing REST or SOAP callouts from triggers or services
  • Designing event-driven flows with Platform Events or Change Data Capture
  • Migrating legacy Named Credentials to External Credentials for API 61+

Best practices

  • Always use Named Credentials or External Credentials — never hardcode secrets
  • Check org API version and prefer External Credentials for new work (API 61+)
  • Use async patterns (Queueable, @future, Platform Events) for any trigger-based callouts
  • Implement retry handlers with exponential backoff and idempotency for 5xx failures
  • Validate callouts with Test.setMock and include Named Credential connection tests

Example use cases

  • Create a JWT Bearer Named Credential and deploy an Apex service for a CI/CD server-to-server integration
  • Register an external payment API via OpenAPI spec and call generated Apex methods to create customers
  • Build a trigger that publishes Platform Events and a subscriber that performs asynchronous REST callouts
  • Enable CDC on Account and generate a subscriber that synchronizes changes to an external data warehouse
  • Migrate legacy Named Credentials to External Credentials and update External Service registrations

FAQ

Check org API version: use legacy if API < 61 or maintaining compatibility; use External Credentials for new development and modern OAuth flows (API 61+).

Can I run callouts from triggers?

Never perform synchronous callouts in triggers; use async patterns like Queueable, Platform Events, or @future to comply with platform rules.

What does the 120-point score evaluate?

It scores Security, Error Handling, Bulkification, Architecture, Best Practices, and Documentation to give a holistic integration quality rating.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational