Integrations

Pinion is the system of record for configuration, pricing, quotes, and contracts. It is not a billing engine, an ERP, or a signature tool. Integrations are how Pinion connects to those systems: an AI assistant drives Pinion, and external systems read the terms Pinion commits and react when they change.

The pattern throughout is bring your own system. Pinion exposes clean surfaces; your assistant, your billing platform, or your integration middleware consumes them. Data stays in Salesforce.

The surfaces

There are three ways in and out of Pinion, and every integration uses one of them.

  • AI assistants, over MCP. Any MCP-capable assistant (Claude, ChatGPT, Agentforce) calls Pinion’s tools against your org — your team asks plain-English questions and takes tightly scoped actions that run as the signed-in user. This is the inbound surface: an assistant driving Pinion. You compose which tools each server exposes — see AI Assistant Access.
  • Platform events, outbound. Pinion publishes Salesforce Platform Events for key lifecycle transitions (a subscription created or changed, an approval submitted or decided, a quote document generated). External systems subscribe and react without polling. See Platform Events & Webhooks.
  • Queryable records. The configuration, line items, subscriptions, and contract terms Pinion persists are standard Salesforce records, readable through the platform’s REST / SOQL / GraphQL APIs (with field-level security). This is how a downstream system reads what a deal committed to. The usage-billing contract is a worked example.

What integrates today, and what’s a pattern

  • AI assistants (MCP) — shipped. A first-class capability; you compose and gate the servers. See the three MCP pages in this section.
  • Billing / rating for usage-based products — a documented data contract. Pinion commits the rate card; your biller (Salesforce Revenue Cloud, Stripe, Metronome, Orb, Zuora, or homegrown) meters and invoices. See Billing Integration for Usage-Based Products.
  • Downstream systems (ERP / quote-to-cash, e-signature, tax, analytics) — the same pattern: subscribe to the relevant platform event, then read the committed records. Pinion provides the surface; the specific connector is built by your team or an integration partner.