Platform › Connectivity
Integration
What is connected, and what is flowing.
In Platform → Connectivity · 5 screens
RecordsConnector CatalogWhat can be connected to: protocols, ERP and finance systems, CRMs, identity directories, payment engines and clinical interfaces. Microsoft Teams calls, meetings and presence are not set up here: add them under CRM › Interaction Centre › Connected Channels.OpenRecordsConnectionsA connector configured against a real system — over HTTPS, or directly over the network (a VPN or interconnect) to a database, directory or service port. Every handshake is TLS 1.2 or higher and the server is verified, against a trusted root or a CA you upload under Certificates. Credentials are encrypted on the way in and never come back out — only the last four characters are ever shown. A connection here carries data; it does not place Microsoft Teams calls or create meetings — those run through CRM › Interaction Centre › Connected Channels, and testing a Teams connection here says what that still lacks.OpenRecordsCertificatesCertificates a connection trusts or presents. A trusted CA lets a connection verify a server whose certificate your own authority issued; a client certificate is presented to the server (mutual TLS). What a certificate says about itself is read from it. A private key is sealed on the way in and never shown again.OpenRecordsData PipelinesExtract from a source, apply the field mapping, load to a destination. An incremental pipeline remembers where it finished and starts there next time.OpenViewPipeline RunsWhat each run read, staged for its destination and failed to stage, and where the cursor moved to. Whether the destination itself can be reached is shown by its connection’s health, on Connections.Open
Columns, fields and actions
| Screen | Kind | What it is | Columns | Fields | Actions |
|---|---|---|---|---|---|
| Connector Catalog | List | What can be connected to: protocols, ERP and finance systems, CRMs, identity directories, payment engines and clinical interfaces. Microsoft Teams calls, meetings and presence are not set up here: add them under CRM › Interaction Centre › Connected Channels. | 9 | 11 | 0 |
| Connections | List | A connector configured against a real system — over HTTPS, or directly over the network (a VPN or interconnect) to a database, directory or service port. Every handshake is TLS 1.2 or higher and the server is verified, against a trusted root or a CA you upload under Certificates. Credentials are encrypted on the way in and never come back out — only the last four characters are ever shown. A connection here carries data; it does not place Microsoft Teams calls or create meetings — those run through CRM › Interaction Centre › Connected Channels, and testing a Teams connection here says what that still lacks. | 17 | 18 | 3 |
| Certificates | List | Certificates a connection trusts or presents. A trusted CA lets a connection verify a server whose certificate your own authority issued; a client certificate is presented to the server (mutual TLS). What a certificate says about itself is read from it. A private key is sealed on the way in and never shown again. | 11 | 5 | 1 |
| Data Pipelines | List | Extract from a source, apply the field mapping, load to a destination. An incremental pipeline remembers where it finished and starts there next time. | 11 | 13 | 1 |
| Pipeline Runs | Read-only list | What each run read, staged for its destination and failed to stage, and where the cursor moved to. Whether the destination itself can be reached is shown by its connection’s health, on Connections. | 11 | 0 | 0 |