Before connecting Salesforce to Enginy, make sure your organization meets the following requirements. This article covers what you need on the Salesforce side — for step-by-step connection instructions, see How to Configure Your Salesforce Integration.
Salesforce Edition
⚠️ Important: Salesforce requires an edition with API access enabled. This excludes some entry-level editions — check with your Salesforce admin if unsure. This is a requirement from Salesforce itself, not from Enginy.
User Permissions
The Salesforce user connecting the integration needs:
API Enabled permission on their profile
Read/write access to the objects you want to sync (Contacts, Leads, Accounts)
⚠️ Important: Enginy does not validate these permissions at connection time. The OAuth connection completes successfully even if "API Enabled" is missing, because exchanging the authorization code doesn't require real API access. The failure shows up later, on the first sync, as a generic, non-actionable message ("There was a problem exporting the data to the CRM. Please check CRM Export Reports page and contact support if you still have questions.") — the real Salesforce error (e.g. "API is not enabled for this User") is only logged internally and never shown to you.
That's why it's critical to verify this permission before connecting — if it's missing, you won't get a clear warning; exports will simply fail without a useful explanation.
Authentication
Enginy connects via OAuth 2.0. When you authorize the integration, you'll be asked to grant these scopes:
api— access to Salesforce data via APIrefresh_token/offline_access— allows Enginy to stay connected without you re-authenticating
Sandbox Testing
Not supported.
Security
Tokens are refreshed automatically; you don't need to re-authenticate manually.
To revoke Enginy's access at any time, do so from Salesforce Setup → Connected Apps → OAuth Usage.