Cross-Category Sync Health Check
A 4-step recipe with Merge. We can help you get access.
Recipe · 4 steps
Cross-Category Sync Health Check
with Merge
Read sync status and open issues for an HRIS and a CRM linked account.
- Read the sync status for the HRIS linked account.
- List the currently ongoing issues for the HRIS linked account.
- Read the sync status for the CRM linked account.
- List the currently ongoing issues for the CRM linked account.
What you'll need to have ready
- authorization: Production access token with the required "Bearer " prefix.
- hrisAccountToken: The account token identifying the linked HRIS end user.
- crmAccountToken: The account token identifying the linked CRM end user.
For your developer
Arazzo workflow merge:cross-category-sync-health-check, 4 operations: {$sourceDescriptions.subpackageSyncstatusApi.url}#/paths/~1hris~1v1~1sync-status/get → {$sourceDescriptions.subpackageIssuesApi.url}#/paths/~1hris~1v1~1issues/get → {$sourceDescriptions.subpackageSyncstatusApi.url}#/paths/~1crm~1v1~1sync-status/get → {$sourceDescriptions.subpackageIssuesApi.url}#/paths/~1crm~1v1~1issues/get. Specs on APIs.io.