Forgeworks docs
Console ↗

Connect Salesforce#

Difficulty: simple (OAuth). Salesforce is the platform's first-class system — real-time change capture, managed loads, Deal Desk, and Assay all run on it.

Auth at a glance#

MethodOAuth 2.0 (web server flow)
What you createNothing — you authorize Forge's connected app
Where Forge helpsForge runs the entire OAuth dance; you click Allow

What you'll need#

  • A Salesforce login with permission to authorize a connected app.
  • For change capture: the org on a Salesforce edition that includes Change Data Capture, with the objects you care about enabled (Forge guides this).

Steps#

  1. In Connections, choose Salesforce → Connect.
  2. You're sent to Salesforce's login + consent screen. Sign in to the right org.
  3. Click Allow to grant Forge access.
  4. You're returned to Anvil with a live, verified connection.

What you get#

  • Stream captures inserts/updates/deletes in real time via Change Data Capture, deduplicated exactly once.
  • Load writes back through the managed-load path — snapshot, verify, and one-click rollback, with a selectable API (Bulk, REST, or Tooling).
  • Deal Desk can watch an Opportunity stage and start a Slack approval.

Gotchas#

  • Sandbox vs production. Authorize the org you actually mean — a sandbox and its production org look similar on the login screen. Check the username domain.
  • Change Data Capture must be enabled for the objects you want to stream. Forge surfaces what's available; enabling an object is a one-time org setting.
Note: Per-org Salesforce credentials (so one tenant can connect several orgs) ride on the same encrypted credential store as every other connector.