Connect your CRM
HubSpot, Salesforce, or Stripe. Pick the one that owns your customer list and connect that.
Pivotal supports three CRM connectors: HubSpot, Salesforce, and Stripe. Pick the system where new customers land first. That system becomes the source of truth for customer names, domains, and primary contacts. Pivotal writes back state changes (active, at-risk, churned) but does not create or rename customers in the CRM.
Connect from Admin > Integrations. Per-connector setup detail lives under Integrations.
The supported pattern is one connector per workspace. Connecting HubSpot and Stripe at the same time creates duplicate customer records when a domain matches across both. If you need to reconcile two systems, leave one off and use data export plus the API to push the second source’s signal into Pivotal as field updates on the existing customer.
The exception: Stripe as a billing-signal source alongside HubSpot or Salesforce as the customer source. Connect HubSpot first, then connect Stripe with the Billing signal only toggle in the Stripe setup flow. Pivotal then attaches Stripe MRR to existing customers via domain match and does not create new ones.
HubSpot and Stripe push via webhook; expect new customers in Pivotal inside a minute. Salesforce polls every 15 minutes. The nightly reconcile (3am workspace time) catches anything the webhook missed, plus syncs field changes that don’t fire webhooks (e.g. contact title updates in HubSpot).
Pivotal’s customer.name maps to HubSpot’s company name, Salesforce’s account Name, and Stripe’s customer name field. If your CRM stores legal entity names (“Acme Corporation, Inc.”) and your team uses display names (“Acme”), set the display name explicitly under Admin > Integrations > [provider] > Field mapping before the first sync. Renaming after the fact is fine but each rename writes back to the CRM unless you flip the writeback toggle off.
Email help@pivotal.app with a screenshot of where you got stuck and the customer or onboarding id from the URL.