Viewing the Sync Criteria/Rules for a Workato Data Sync

Unifyr Support
Unifyr Support
  • Updated

Criteria/rules for a Workato data sync define the conditions that must be satisfied for a data object to be picked up for the sync.

You can find the criteria/rules that are configured for a sync in Unifyr Admin - they are listed in the Parent asset/recipe for the sync.

Notes

It is also required, but will not be described in the sync criteria, that for a lead or deal to sync from Unifyr to your CRM, the Unifyr partner account registering the lead or deal must contain your CRM's external ID in the SSO Company ID field on the Partner profile in Partner Explorer.

When syncing leads or deals from your CRM to Unifyr, the account in your CRM must contain the Unifyr Partner ID.

If these IDs are not present or the record does not meet the required sync criteria, the record will not be picked up for a sync. No job will be recorded under the project.

To find the sync conditions:

  1. Navigate to   > Settings > Integrations > iPaaS.  
  2. In the Projects tab, go to the list of projects. Click on a project to open the syncs it contains. These relate to the types of object being synced in this direction.

  3. Choose an object type, then find and click on the Parent asset/recipe that is syncing the data. For example, to view the conditions for Leads syncing from Salesforce to Unifyr, select Salesforce to Unifyr | Leads | Parent (note that the list of available assets and names varies by supplier - your list might look different).

    admin_integrations_workato_choose_parent_asset.png 

  4. Go to the Recipe tab for the sync.
  5. Select the Trigger for the recipe.

  6. In the popup panel, scroll down to SOQL WHERE clause, where the conditions for the trigger are defined.

    admin_integrations_workato_recipe_soql_where_clause.png 

    This example includes these conditions - they're separated by an AND operator which means that all three must be satisfied:

    • Zift_Lead_Partner__r.Zift_Partner_ID__c <> - the Unifyr Partner ID must be present in on the account record in the CRM
    • (Zift_Distributed_Lead__c = true or Zift_Registered_Lead__c = true) - one of these values must be checked/true on the lead in the CRM
    • LastModifiedById not in (select UsersId from AuthSession where IsCurrent = true) - the record was not modified by the integration account. This condition stops looping updates.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.