> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.pivotal.app/llms.txt.
> For full documentation content, see https://docs.pivotal.app/llms-full.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.pivotal.app/_mcp/server.

# Integrations

Pivotal sits in the middle of your customer-success stack. Your CRM owns the sales pipeline, Stripe owns billing, Slack owns conversations, and your data warehouse owns reporting. Pivotal pulls from each, joins the records on a single customer, and pushes events back out when something changes.

There are five kinds of integrations to think about:

* **CRM sync** mirrors your HubSpot companies and contacts into Pivotal customers and contacts. One-way, HubSpot to Pivotal.
* **Billing sync** brings Stripe subscriptions, MRR, and payment status onto each customer record.
* **Slack** posts notifications to channels you pick and gives your team `@Pivotal` mentions and slash commands.
* **Outbound webhooks** let your own systems react to Pivotal events. Backed by Svix, with signed payloads and replay.
* **Email templates and data export** cover customer comms and warehouse-scale takeout.

If you are wiring Pivotal up for the first time, do them in this order: HubSpot, then Stripe, then Slack. CRM gives you the customer list to work with. Stripe gives every customer a plan and MRR. Slack closes the loop so your team sees changes without opening Pivotal. Webhooks and data export come last, once you know what you want to fan out.

OAuth, field mapping, sync direction.

Pull subscriptions, MRR, payment status.

Bot, channel routing, notifications.

Map CRM properties to Pivotal fields.

Slack, email, and in-app routing.

Welcome, kickoff, digest, at-risk.

Outbound events to your systems.

Diagnose missing or stale records.

CSV, full takeout, warehouse path.

Email **[help@pivotal.app](mailto:help@pivotal.app)** with a screenshot of where you got stuck and the customer or onboarding id from the URL.