forcedotcom/sf-skills / plugins/builder/integration/skills/platform-salesforce-connect-adapter-generate
platform-salesforce-connect-adapter-generate
VerifiedCustom Apex adapter generation for Salesforce Connect — connects any external REST API to Salesforce as live, queryable External Objects without ETL or copying. TRIGGER when: connecting a non-standard external API, writing a DataSource.Provider/Connection or a `.cls`/`.cls-meta.xml` custom adapter class, adding a `.namedCredential-meta.xml` for the adapter's callout, surfacing external data as records, "custom adapter", "ExternalId field", "DataSource namespace", or whether custom Apex fits. DO NOT TRIGGER when: a standard adapter is already configured (OData, Snowflake), for copy/bulk-sync (use platform-data-manage), or for Apex callouts outside Connect (use platform-apex-generate or integration-connectivity-generate).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 19.4 KB |
| references/official-examples.md | markdown | 3.6 KB |
| references/scenarios.md | markdown | 7.8 KB |
references/official-examples.md
View on GitHub# Official Salesforce Connect Adapter Examples
Study these before generating code for a user. Each example demonstrates distinct patterns — don't generate from memory alone.
## GitHub Issues adapter — read this one first
The most complete example, built by the Salesforce Connect team as the definitive reference. It is the only official example with:
- Full DML: create, update, delete (`upsertRows` + `deleteRows`)
- Date fields and picklist / multi-picklist fields
- Two related external object tables (Issues + Comments) with cross-table relationships
- `DataSource.Column.externalLookup()` and `DataSource.Column.indirectLookup()`
- `DataSource.QueryUtils.process(context, rows)` — handles ORDER BY and LIMIT automatically; use this instead of manual sorting
Read it: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_connector_example_github_issues.htm
Key patterns to bring forward:
```apex
// Let QueryUtils handle sorting and limiting — don't do it manually
return DataSource.TableResult.get(context,
DataSource.QueryUtils.process(context, rows));
// Cross-object relationship to another external object
DataSource.Column.externalLookup('issue_number', 'GithubIssues__x')
// Indirect lookup — link external object to a standard Salesforce object
DataSource.Column.indirectLookup('repository_url', 'Product2', 'Repository__c')
// Picklist column
DataSource.Column.picklist('State', new List<String>{'Open', 'Closed'})
```
## Other official examples — each demonstrates one specific feature
| Example | The one thing it's best for | Unique pattern |
|---------|----------------------------|----------------|
| **GitHub (users)** | Indirect lookup to a standard object | `DataSource.Column.indirectLookup('login', 'Contact', 'github_username__c')` — links external records to Contact via a custom external ID field |
| **Google Drive** | OAuth per-user auth + test mock pattern | `System.Test.isRunningTest()` returns static `mockResponse` to avoid real callouts in tests; `'Authorization', 'Bearer '+ connectionInfo.oauthToken` for OAuth |
| **Google Books** | Pagination against an API with a hard page-size cap | Explicit loop accumulating batches: `data.addAll(getData(url + startIndex))` incrementing offset by 40; `column.sortable = false` for non-sortable fields |
| **StackOverflow** | Multiple tables with external lookup between them | `DataSource.Column.externalLookup('owner_id', 'stackoverflowUser__x')` linking child posts to parent user external object |
| **Loopback** | Filter translation from `DataSource.Filter` to SOQL | `getSoqlFilter()` recursively maps all `FilterType` values (EQUALS, LESS_THAN, STARTS_WITH, AND_, OR_, NOT_ etc.) to SOQL operators — use this when the user's API supports server-side filtering |
| **GitHub Issues** | Full DML + picklist + date + two related tables | See primary reference above |
Base URL: `https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/`
## Test mock pattern (from Google Drive)
Use this in all generated adapters to make them testable:
```apex
if (System.Test.isRunningTest()) {
return mockResponse; // return static test data
}
Http http = new Http();
// ... real callout
```
## Filter translation pattern (from Loopback)
Use this when pushing WHERE clause conditions to the external API:
```apex
// Access filter from query context
DataSource.Filter filter = context.tableSelection.filter;
// filter.type is one of: EQUALS, NOT_EQUALS, LESS_THAN, GREATER_THAN,
// LESS_THAN_OR_EQUAL_TO, GREATER_THAN_OR_EQUAL_TO, STARTS_WITH, ENDS_WITH,
// LIKE_, AND_, OR_, NOT_
// filter.columnName, filter.columnValue, filter.subfilters (for compound)
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |