Post Connection Data Scope Filtering

Establish a data-scope filtering strategy (pre-storage or post-storage) before syncing data from Merge. Customers rarely want every record their connected system has — they want a scoped subset (active employees in HRIS, candidates in a specific stage in ATS, accounts of a certain type in CRM, tickets from a specific project in Ticketing, etc.). Use as Step 6 of post-connection implementation when customers need control over which records are synced. Triggers on: "filter synced data", "selective sync", "sync scope", "employee filtering", "candidate filtering", "account filtering", "ticket filtering", "include/exclude records", "scope of sync".

merge-api Updated 1 repo stars

File contents

merge-api/merge-unified-skills commit d66bcc41da

Frequently asked questions

npx get-skill add merge-api/post-connection-data-scope-filtering