Release identity
SHA-256 of the pack file bytes: fcd8bb7b1e73b3c9ac0800f427d2003eb6d6c9b10d5a7ea806cafa3bcd167e4e
Not in the distributable release manifest. The binary carries a digest-bound manifest of the distributable library; a pack whose bytes differ from its manifest entry — endpoint, tier, allowlist, or credential edited, with provider, version, and review block preserved — fails the digest check, loses distributability, and renders MODIFIED rather than as the shipped reviewed artifact. Review state and artifact status are different facts: the first is a documentation-review declaration, the second is the identity of the exact bytes.
Capabilities (4)
salesforce.account.read v1.0.0R0
- Action
- read
- Endpoint
GET https://your-instance.my.salesforce.com/services/data/v62.0/query- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-salesforce-oauth- Data class
- pii
Query Account records through the SOQL query resource (the SELECT statement is the request's q parameter). Account data identifies individuals and is registered at the pii class.
salesforce.lead.create v1.0.0R2
- Action
- create
- Endpoint
POST https://your-instance.my.salesforce.com/services/data/v62.0/sobjects/Lead- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-salesforce-oauth- Data class
- pii
Create a Lead record.
salesforce.opportunity.update v1.0.0R2
- Action
- update
- Endpoint
PATCH https://your-instance.my.salesforce.com/services/data/v62.0/sobjects/Opportunity/OPPORTUNITY_ID- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-salesforce-oauth- Data class
- financial
Update one Opportunity record, including amount and stage; OPPORTUNITY_ID in the path is a placeholder for the record this capability is bound to.
salesforce.account.delete v1.0.0R3
- Action
- delete
- Endpoint
DELETE https://your-instance.my.salesforce.com/services/data/v62.0/sobjects/Account/ACCOUNT_ID- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-salesforce-oauth- Data class
- pii
Delete one Account record; ACCOUNT_ID in the path is a placeholder for the record this capability is bound to. Delete is one of the IRREVERSIBLE ACTIONS (delete, send, pay, deploy, approve, share and transfer), so it carries the R3 floor; policy can raise it further.
Credential reference
The pack names a reference, never a secret. Installing a pack registers capabilities and makes them governable; registration is not connectivity. The credential is created at the provider and held in the client's own secret manager under the reference the pack names, and deployment testing is still required to show the credential path works and cannot be bypassed.
- Reference
secret-ref-salesforce-oauth- Custody
- customer_vault
- Injection
- header (Authorization)
A Salesforce access token (minted by an external client app or a connected app) held in the client's own secret manager. The stored material must be the complete Authorization header value (scheme included). A per-decision token obtained by identity federation is the stronger option where the org supports it; this pack registers the client-vault model as the default.
Resources
salesforce-org(api, financial):https://your-instance.my.salesforce.com
Pack notes and exclusions
The endpoint host 'your-instance.my.salesforce.com' is a placeholder: replace it with the org's My Domain before enabling, in the endpoint and in the egress allowlist. OPPORTUNITY_ID and ACCOUNT_ID in the endpoint paths are placeholders too: Salesforce's sObject Rows resource targets one record as /sobjects/{Object}/{Id}, so update and delete must name the record they are bound to, and record retrieval goes through the query resource (SOQL SELECT as the q parameter). Replace the ids before enabling. As of Spring '26 Salesforce restricts new connected-app creation and recommends external client apps for new integrations; the org's admin creates the app, and this pack does not. The pack pins API version v62.0 deliberately: Salesforce keeps serving pinned versions, and a version bump is a reviewed migration, not a silent edit. The review state is draft, not library, for a concrete reason: this pack's custody model — a long-lived OAuth access token held in the customer's vault and refreshed client-side — has not yet been reviewed against the properties the capability-library plan (docs/gtm/CAPABILITY-LIBRARY-PLAN.md §4) gates any authentication mode on: issuance authority and delegation, scope, audience, TTL, refresh ownership, revocation, executor access and bypass paths. That review is unfinished; identity_federation (a per-decision token where the org supports it) is one candidate stronger model, not an automatic pass.
Review record
Draft review record dated 2026-09-21 · Reviewer: aaes-eng (an opaque id that resolves internally to the responsible reviewer)
- https://developer.salesforce.com/docs/platform/api-rest/guide/intro-oauth-and-connected-apps.html (retrieved 2026-09-20)
- https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/ (retrieved 2026-09-20)
- https://developer.salesforce.com/docs/platform/api-rest/guide/resources-list.html (retrieved 2026-09-21)
A pack review is not a vendor or examiner attestation. A retrieval date says when a source page was read; it does not by itself establish what the page said then. No pack is vendor-endorsed, and none has been connectivity-tested against a live vendor tenant.