Terminal
Terminal/Skill
Skill for using Paragon's Managed Sync for ingesting and syncing 3rd-party data like Google Drive files or CRM records
By Paragon
Works with
npx skills add useparagon/paragon-ai-skills --skill paragon-managed-sync-skillUse this Skill to help the user implement Managed Sync with the Sync API and the Permissions API, using the references in the Table of Contents.
Managed Sync is a set of APIs for developers to spin up data pipelines that pull their users' 3rd-party integration data (like Salesforce CRM data, Google Drive file data, and ServiceNow tickets) and keep that data up-to-date. These data pipelines live in Paragon's infrastructure and are completely managed by Paragon. Developers can easily start syncs, pause syncs, and pull synced data.
When integration data is synced, that data is also normalized across that integration's category. For example, the data schema from Google Drive, Dropbox, Box, and Sharepoint are all normalized so that code/logic can be used across that category.
For file storage integration data, the Permissions API is an API to check permissions of any synced file. Paragon manages a graph database behind the scenes, so developers can get and check up-to-date permissions without managing that data.
When helping with RAG or search implementations, guide the user toward the right Permissions API pattern:
List Objects is usually enoughStreamed List ObjectsStreamed List Objects (All Syncs)Batch Check Access is usually the right post-filtering stepManaged Sync is built on top of Paragon's managed authentication and monitoring. When using any Sync APIs or Permissions APIs, a JWT with a unique end-user ID is required so that Paragon knows which end-users data to sync.
Managed Sync also requires the aud claim on the Paragon User Token to match the Paragon hostname and project ID.
Before helping the user implement Managed Sync, it's best to have the Paragon SDK and Connect Portal setup.
Check the user's project for "@useparagon/connect" in their package.json or references of paragon.authenticate in their frontend codebase
If a user does not have the Paragon SDK and Connect Portal for authorization set up: Direct them to use the paragon-setup-skill
If the user does have the Paragon SDK and authorization set up: Proceed with using the resources in the "Table of Contents" to help implement Managed Sync