CRM and Data Sync Connections
Salesforce, HubSpot, monday.com, and Confluence use the App Connections area to authorize an account and configure synchronization. The connection-specific UI walkthroughs live in the App Connections user guide. This page summarizes the developer-facing sync contract and where each provider fits.
Supported mappings
| Provider | Gravity Rail target | Match options | Inbound target options | Conflict choices |
|---|---|---|---|---|
| Salesforce | Members | Email, phone, or existing link | Member property, managed field, or Member label | Local wins, remote wins, skip |
| HubSpot | Members | Email, phone, or existing link | Member property or managed field | Local wins, remote wins, skip |
| monday.com | Members or Form records | Email, phone, external ID, existing link, or custom | Member property, managed field, or Form field | Local wins, remote wins, skip |
| Confluence | Files | Existing link | No Member or Form target | Remote wins |
Match and target options are connector-specific. A mapping must use an option supported by that connection. For API-driven Member creation or Form imports, see Creating Members and Importing Data.
Salesforce
Salesforce synchronization targets Members. Match an incoming record by email, phone, or an existing record link; inbound rules can update supported Member properties, connection-managed fields, or labels. The connection also exposes task and activity logging operations. For Salesforce-side API and OAuth concepts, see Salesforce REST API authorization.
HubSpot
HubSpot synchronization targets Members and supports the same email, phone, and existing-link matching choices as Salesforce. Inbound rules can update supported Member properties or connection-managed fields. HubSpot also supports logging chat notes and CRM activity. For app authentication and object APIs, see HubSpot developer documentation.
monday.com
monday.com supports both Member and Form-record mappings. Use a Member target for one item per person, or a Form target when an item represents a record associated with a Member. Matching can use email, phone, external ID, an existing link, or a custom rule. For board and column data structures, see the monday.com API reference.
Confluence
Confluence synchronizes files. It uses existing links to match content and applies remote-wins conflict handling. It does not create or update Members or Form records. See the Confluence Cloud REST API for provider content resources and OAuth 2.0 (3LO) for Atlassian authorization concepts.
Member identity and data ownership
Use a stable external record link when the connector has already matched or linked a record; an email or phone match is a matching rule, not a permanent external identity. When syncing inbound fields, choose the specific writable Member property or managed field exposed by the connector. To review the shared Member schema and import/export contracts, use the Members API, Data Records API, and Exporting Data.
Related
- App Connections — authorize providers and configure sync mappings.
- Creating Members — create and identify Members.
- Importing Data — reconcile incoming records.
- Exporting Data — export workspace data.