All records ingested by Managed Sync are normalized into standard Synced Object types supported by each category, so that you can add support for all available integrations in File Storage or CRM while implementing Sync API once. Synced Objects can be retrieved from the Sync API using Pull Synced Records.

​
File Storage

Synced Objects for File Storage integrations represent file and folder metadata. Paragon does not store the contents of the files that are synced; files are proxied from the integration directly upon download request.
  • File (files): A file or folder in a File Storage integration. Files and folders can be distinguished by mimeType.
    • For document integrations like ServiceNow or Confluence, documents will be exported as text or HTML files when downloading file content.

​
CRM

Synced Objects for CRM come with a normalized schema for each object type, but any unmapped fields are always available in the customFields property, giving you complete over visibility over the underlying contents of each record.
  • Contact (contacts): A person with contact details as represented in a CRM integration.
  • Company (companies): A company, organization, or account in a CRM integration.
  • Deal (deals): A deal or opportunity record in a CRM integration.
  • Custom Object (custom_objects): Sync any object, including user-defined custom objects, directly from a CRM with a Custom Object sync pipeline.

​
Ticketing

Ticketing sync pipelines are coming soon. If you are interested in early access, please contact us.

​
Customizing the Synced Object Model

Synced Object Model customizations and Custom Source Framework are coming soon. If you are interested in early access, please contact us.
With our Custom Source Framework, you can define your own schema for any Synced Object and add support for integrations outside of our catalog.