claude-memory/graph/configurations/sf-ca-getter-salesforce-oauth2-auth-pattern-differs-from-poo-463065.md

id	type	title	tags	importance	confidence	created	updated	relations
46306580-2561-45f5-b479-d62fce505a04	configuration	SF-CA getter: Salesforce OAuth2 auth pattern differs from Poolbrain API key	esb-monorepo sf-ca salesforce authentication oauth2 configuration	0.65	0.8	2026-02-26T18:57:46.631773+00:00	2026-02-26T18:58:15.151987+00:00	target type direction strength edge_id 83e29321-7215-47a1-813e-a73187bda39f RELATED_TO incoming 0.75 777a44d6-96ba-4552-a743-f12dc3a31e1a

SF-CA Getter: Salesforce Authentication

Auth Mechanism

OAuth2 (token refresh required) — unlike Poolbrain's simple API key header.

Secret Manager Format (TBD)

JSON blob with OAuth2 credentials. Fields TBD based on chosen auth flow, likely:

• client_id
• client_secret
• username
• password
• security_token
• instance_url

Key Differences from Poolbrain

• Must handle token expiry and refresh within getter lifecycle
• Uses Salesforce REST API with SOQL queries (not a REST collection endpoint)
• Pagination via nextRecordsUrl in response (vs. offset-based or cursor)
• Queries TWO object types: Account and Contact (vs. Poolbrain's single Customer type)
• Salesforce has daily API call limits — query efficiency matters

API Pattern

GET /services/data/vXX.X/query?q=SELECT+...+FROM+Account+WHERE+LastModifiedDate+>+{timestamp}

Response includes totalSize, done, nextRecordsUrl (if paginated), records[].