Salesforce Real Time Sync
What it is
The Mixmax Real Time Sync (MX-RTS) from Salesforce package is built to get all your necessary updates into Mixmax in real time. This means that the package only is handling traffic from Salesforce to Mixmax and not the other way around.
Customers utilizing MX-RTS to sync data from Salesforce to Mixmax will also require a Salesforce Sync User in order for Mixmax to ensure it’s connected to the correct Salesforce deployment for the Mixmax org. MX-RTS benefits customers as it does not utilize API quota for its applicable portion of the bi-directional sync. API quota will only be used by individual users syncing their changes from Mixmax to Salesforce (i.e. updating records).
Let’s dive in and see how MX-RTS works.
How it works
MX-RTS is purely Salesforce Apex based and consists of minimal Apex code to ensure that there is negligible contribution your Salesforce Apex code limit. The lion’s share of the package is Apex triggers with a smattering of a few Apex classes which receive the data from the triggers to send to Mixmax.
Apex triggers on updates
MX-RTS uses the triggers to identify whenever a change has been made to an Account, Contact, Event, Lead, Opportunity, Task or User. These triggers fire after the resource has been updated.
Sending information to Mixmax
Each trigger sends the update to one of the few MX-RTS Apex classes to then send that information on to Mixmax.
What does this mean for my API quota
The MX-RTS package uses zero of your Salesforce API quota for its applicable portion of the bi-directional sync, sending information from Salesforce to Mixmax. API quota will only be used by individual users syncing their changes in the other direction, from Mixmax to Salesforce (i.e. updating records).
Example: Updating a lead in Salesforce triggering a rule in Mixmax
Let’s look at an example of how updating a lead in Salesforce would trigger a rule in Mixmax that would add that lead to a Sequence.