Integrations
Connect your CRM, email, calendar, product usage, and conversation data so Cust can build a complete picture of every customer.
Cust is only as useful as the data it can see. Integrations bring your customer data into one place, so health scores, signals, and recommendations reflect what is actually happening across every account.
Supported integrations
Availability depends on your workspace and region. Slack, Zoom, Single sign-on, and Assistant connectors require the corresponding workspace feature. Jira is currently listed for US workspaces. Contact support@cust.co if a guide's connection is missing from your settings.
Identity and access
Owners and admins configure these connections in Settings → Single sign-on.
Okta single sign-on
Connect sign-in, verify email domains, and manage access through Okta.
Okta provisioning
Create and deactivate members, update profiles, and manage roles through SCIM.
Microsoft Entra ID single sign-on
Connect Microsoft work identities with OIDC and verified-domain sign-in policies.
Microsoft Entra ID provisioning
Map users and roles, then verify onboarding, access changes, and offboarding.
CRM
Support and messaging
Calls and meetings
Email and calendar
Product usage and data warehouse
Issue tracking
What Cust syncs
Depending on the source, an integration can sync:
- Companies and contacts: your accounts and the people on them.
- Deals and transactions: contract and revenue data, used for managed revenue and lifecycle.
- Calls and meetings: meeting details, summaries or transcripts, and links to source recordings where the provider supplies them. Cust uses the imported text for sentiment, topics, and account context.
- Support conversations: tickets and issues from your support tool, synced message by message onto the account timeline. For Pylon you can also exclude issues by tag, so internal or automated noise stays out.
- Tasks: open work tied to an account.
- Product usage and metrics: events and usage levels that drive adoption signals and user statuses.
Connecting an integration
Admins manage customer-data integrations in Settings under Integrations.
Choose a provider and authorize it
Pick the integration and connect it with OAuth where supported, or with an API key.
Select what to sync
Review the resources and filters available for that provider. Some connections offer self-service field and object selection; others use a configured sync scope.
Let the initial sync run
Cust imports your data, then keeps it up to date. Each connection shows whether it is connected, disconnected, or needs re-authentication.
Review what a connection can access and sync
Open a provider in Settings → Integrations and review its details. The panels answer three separate questions:
| Panel | What to check |
|---|---|
| Connection | Authentication method, connected user and date, provider account, and credential refresh date where available. Confirm this is the account you intended to connect. |
| Access granted | The scopes reported by the provider, or an explanation of where permissions are managed. For BigQuery, inspect the service account's IAM roles in Google Cloud. For an API key, inspect the key's permissions at the provider. |
| Data synced | Each configured resource, its schedule or filters where available, and its Last sync. Review resources individually. |
Syncing means importing is enabled for that resource. It does not indicate that a job is running at that moment. Not syncing means importing is disabled. Never means no sync time has been recorded for that resource.
For example, a BigQuery connection can be authorized while its metric query still shows Last sync: Never. Check that the query is configured and enabled, then check its next scheduled run. Once a sync time appears, compare a known query row with the company's metric.
An absent scope list is not a statement that the connection has no access. Some providers do not return scopes with their credentials. Use the explanation in Access granted, then narrow access in the provider and review the data selection in Cust. See Data handling.
Keeping connections healthy
Check each connection's current state and latest sync. Some providers, including Snowflake, show an authorization expiry and a reconnect reminder. Reconnect when prompted, and inspect failed syncs or missing data even if the connection still appears authorized.
Mapping fields
Salesforce and HubSpot managed connections let you select fields, configure key fields and record filters, and review changes before applying them. Removing a managed field deletes its stored values in Cust. Use the sync toggle to pause updates while retaining data. See the CRM integration guide.
For setup and troubleshooting, use the email and calendar, calls and meeting notes, and product data guides. Assistant connectors provide tools for chat, and the Partner API supports custom integrations.
Start with your CRM
Your CRM defines who your customers are, so connect it first. See Data handling for exactly what Cust syncs and how to limit scope.