Integration Type: OAuth 2.0, Organization-Level
Setup Time: 5–10 minutes
Required Role: Salesforce System Administrator or equivalent
Setup Time: 5–10 minutes
Required Role: Salesforce System Administrator or equivalent
Prerequisites
- Active Salesforce account (Sales Cloud, Service Cloud, or similar)
- System Administrator or API Enabled permissions in Salesforce
- Organization administrator access in Cora.ai
- You do not need to create a Connected App in Salesforce — the Cora integration is fully managed on our side
Required Permissions
Cora.ai will request the following Salesforce permissions:- API Access (
api) — Access Salesforce APIs - Perform requests at any time (
refresh_token,offline_access) — Maintain persistent connection
- Granular control over accessible data
- Clear audit trail (all API activity attributed to the integration user)
- Easy permission management without affecting other users
Setup Steps
1
Approve the Cora Connected App in Salesforce
Salesforce requires your org to explicitly approve third-party Connected Apps before they can be authorized. You’ll need to create a temporary permission set to allow this.
- In Salesforce, go to Setup → Permission Sets
- Click New and name it something like “Cora Integration Access”
- In the new permission set, click System Permissions → Edit
- Check the box for “Approve Uninstalled Connected Apps” and click Save
- Click Manage Assignments → Add Assignments
- Select the user who will connect Salesforce to Cora and click Assign
2
Initiate Connection in Cora
- Log into Cora.ai as an organization administrator
- Navigate to Settings → Organization Settings → Integrations
- Locate the Salesforce integration card
- Click the Connect button
3
Salesforce Authentication
- You will be redirected to the Salesforce login page
- Enter your Salesforce credentials
- Select the appropriate Salesforce instance (Production or Sandbox)
4
Grant Permissions
- Review the permissions that Cora.ai is requesting
- Verify the requested scopes align with your security policies
- Click Allow to grant access
5
Confirm Connection
- You will be redirected back to Cora.ai
- The Salesforce integration card will show Connected status
- Connection details will display:
- Connected by: [Admin Name]
- Connected on: [Date]
- Instance: [Production/Sandbox]
6
Clean Up (Optional)
Once the connection is confirmed, you can remove the temporary permission set created in Step 1. Go to Setup → Permission Sets in Salesforce, select “Cora Integration Access”, and delete it.
7
Enable Lifecycle Events
Track events across your customer lifecycle — from onboarding and renewals to upsells, expansion, and churn risk — so your team never misses a key moment.
- Click the connected Salesforce integration card to open the settings panel
- Under Lifecycle Events, toggle the switch on
- Click Save
What Cora.ai Accesses
Reads: Cora.ai syncs Accounts, Contacts, Opportunities, Cases, and other configured objects via scheduled API polling. All data stays on Cora’s infrastructure and is used to surface insights and track lifecycle events. Writes (if configured): When agents are configured for Salesforce actions, Cora can update record fields, post to Chatter, and attach files to records. Writes only happen through explicitly configured agent workflows — never automatically or without visibility. If write-back is enabled for your organization, your Cora.ai contact will walk through the specifics and provide observability for any changes made.Importing Accounts and Ownership Sync
Once Salesforce is connected, you can import accounts, set up ownership sync, and filter by ownership on the Accounts page. See Managing Your Accounts for setup instructions.How the Sync Works
Cora uses scheduled API polling to keep your Salesforce data in sync. Here’s what that means for your org:- Standard REST API — Cora periodically queries Salesforce’s standard API to pull the latest data. No CDC, Platform Events, or Apex triggers are involved.
- Nothing installed in your org — No packages, triggers, or custom objects are created in your Salesforce instance. All processing happens on Cora’s infrastructure.
- Change detection on our side — Cora compares current field values against a previous snapshot stored on our infrastructure. All comparison and change detection logic runs on Cora’s side.
- API usage — Only standard Salesforce API calls are made, counting toward your org’s daily API request limit. If API limits ever become a concern, we can adjust the polling frequency.