evonx
Guide

How to integrate Salesforce

Follow these steps in Evonx to connect Salesforce objects to your application with secure API access. Use this when enterprise CRM data must stay synchronized with product workflows.

Step-by-step

Pick objects and ownership

Document Account, Contact, Opportunity, or custom objects and which system wins conflicts.

Configure Connected App

Create a Salesforce Connected App with OAuth scopes matching your integration needs.

Authenticate with JWT or OAuth

Prefer server-to-server JWT for backends; store certificates and secrets outside the repo.

Query and upsert via REST/Bulk

Use REST for interactive flows and Bulk API for large syncs with external ID matching.

Subscribe to change events

Use platform events or Change Data Capture where near-real-time updates matter.

Preview against a sandbox

Validate mappings in a Salesforce sandbox via Evonx preview before production merge.

Outcome

Salesforce-integrated application code with OAuth/JWT auth, upserts, and change handling you can ship.

FAQ

REST vs Bulk API—when?

REST for low-volume interactive sync. Bulk for nightly or large backfills to respect governor limits.

How do I map custom fields?

Maintain an explicit field dictionary in code or config and fail loudly when required fields are missing.

Can multiple Salesforce orgs connect?

Yes in multi-tenant products—store org credentials per tenant and never share connections across customers.

Build production software with Evonx

Start from a template or connect an existing repository. Evonx helps you ship real applications with preview, evolution threads, and pull-request delivery—not disposable demos.