Data Sources
Data Sources represent collections of Data Records on the external apps. Integrations can read from them, write to them, and react to changes in them.

Managing Collections

Each data source has name, key, and optional Unified Data Model associated with it. You can select a UDM if you want the data source to contain records of a certain type (Contacts, Companies, etc), or you can leave it empty so that user could associate the Data Source with any data in the third-party application.

Data Collection Instances

Each Connection will have its own instance of a Data Source. If your user created two different connections, integrations that use the same Data Source will work with different data.
Additionally, when configuring flows, you can choose whether to share a Data Source with other integrations. If you chose "don't share", each Flow Instance will have its own independent Data Source Instance. If you chose "share" (default), all flows and nodes that use the same Data Source within the same Connection will point to the same data. This is useful when you want to have multiple flow or nodes working with the same data and don't want your users to configure each one individually.

User Interface

When you let your user customize integrations that use a Data Source, and there are multiple possibilities of where the Data Source can point to within a given Connection, your users will be able to choose the path to the data source:
​
​
If you associated an Universal Data Model with the data source, only locations that support this data model will be available to select (except Connections that don't support this UDM - in which case the behavior will be as if UDM was not associated with the Data Source).
​
Copy link
Outline
Managing Collections
Data Collection Instances
User Interface