Today, we’re excited to announce the release of Sync Sequence Triggers. This new kind of trigger allows you to run a sync based on the successful run of another sync.
But why?
This is useful for anyone trying to sync data across a graph of objects with nested dependencies, like in a CRM when you have a relationship that looks like this 👇
Previously, you would just run syncs in parallel and the data in these objects would eventually be consistent. But that meant your data could be in a weird state where a Contact “is attempting to be associated with an Account", but is rejected because the Account sync hadn’t been completed yet.
This race condition rears its head related to lookups/reference records, which would need the next sync to properly handle the association. Then, finally, the next contact sync would then associate the existing contact with the newly created account. 🤪
With Sync Sequence, you can now pick the order you want to create or update these objects. If we take our previous example, you can now create this Sync flow.
This guarantees that all the associations will be correct as they are being created and updated in the right order. No more orphan contacts waiting for 2 (or even 3) syncs before being associated with their accounts and their workspace objects!
But that’s not all. With Sync Sequence Triggers, you can also explore new use cases such as:
Scheduling your payment sync to run only after the associated contact is created and updated in Stripe
Create Events in your Product Analytics tools like Mixpanel only after the users are created
What’s next?
Does this mean that Census is doing orchestration? No. But we are big believers that you shouldn’t just sync fields on a single object but rather the whole representation of your business objects in all of your tools. Having dependencies between syncs is the first step toward that dream.
