Salesforce integration is available on all paid plans. Check out our pricing page for more information.
If your Salesforce plan includes API access, you're under your API usage limit, you're connected to Salesforce, and you are still having trouble syncing data, you may need to enable the Mixmax app in Salesforce.
Depending on your permissions in Salesforce, you may not be able to do this yourself and may need to ask your Salesforce admin. Sharing this article with them may help.
Salesforce Lightning and Classic
In Salesforce Setup, go to Apps → Connected Apps → Connected Apps OAuth Usage in the left sidebar.
Locate Mixmax in the list of connected apps, and then click Install. (For full details, see the Salesforce support article on managing OAuth-connected apps.)
If you're using Lightning, follow the Lightning-UI prompts; if Classic, follow the Classic-UI prompts.
When the install pop-up appears, click Install.
Once installation completes, Salesforce is now connected to your Mixmax account.
To customize which events sync between Mixmax and Salesforce, go to the CRM & Live Feed section in the Settings on your Mixmax dashboard, or to the CRM integrations section if an admin manages it.
Salesforce Lightning Install Prompt
Salesforce Classic Install Prompt
Once you've completed these steps, the Mixmax app will be fully enabled in Salesforce!
Approving users for the Mixmax connected app
Salesforce admins can set the Mixmax connected app so that only admin-approved users can use it. With this setting enabled, each Mixmax user's Salesforce profile or permission set must be approved for the app. Until a user is approved, Salesforce blocks every request Mixmax makes for them, so their emails and meetings aren't logged to Salesforce.
When this happens, Mixmax shows a warning:
The affected user sees a Salesforce isn't syncing warning on their Integrations settings page, even though the page says they're connected.
Workspace admins see a warning icon next to the user in Admin Center > CRM Integrations > Connected Members, along with a notice that names everyone affected.
To check whether Mixmax is limited to admin-approved users and approve users:
In Salesforce Setup, enter Manage Connected Apps in the Quick Find box, then select Manage Connected Apps.
Click Mixmax.
Under OAuth Policies, check the Permitted Users setting. If it's set to Admin approved users are pre-authorized, only users you approve can use Mixmax.
To approve users by profile, scroll to Profiles and click Manage Profiles. To approve users by permission set, scroll to Permission Sets and click Manage Permission Sets.
Select the profiles or permission sets assigned to your Mixmax users, then click Save.
For full details, see the Salesforce help article on managing OAuth access policies for a connected app.
Once a user is approved, syncing resumes automatically, and they don't need to reconnect. The warning in Mixmax clears after the next daily sync, so it can take up to a day to disappear. Emails and meetings that weren't logged while the user was blocked won't be logged later.
Ask affected users not to disconnect Salesforce in Mixmax while they wait. Disconnecting removes the connection that lets syncing resume automatically, and they can't reconnect until they're approved.
FAQ
How is OAuth handled?
Mixmax uses OAuth to securely authenticate with Salesforce without storing user credentials. Salesforce issues time-limited access tokens after explicit authorization, and tokens are scoped to the permissions granted to the user.
If a user's Salesforce account is deactivated, Mixmax can no longer sync that user's activity to Salesforce.
If your workspace's Sync User is deactivated or disconnected, Mixmax stops receiving updates from Salesforce, so the Sidebar, Salesforce variables, and other features that rely on up-to-date Salesforce data might not work as expected. Each user can still log activity to Salesforce records that Mixmax already knows about through their own connection, but activity for records created in Salesforce after that point won't log until the Sync User is reconnected. That's why we recommend a dedicated integration user as your Sync User and keeping it active. See: Who should be the Sync User?