Connect an integration
Stripe, Plaid, Gusto, Addigy, Pax8 and Jira, each connected once for the Org. What each one is for, and what Pippin does with it.
Before you start
Integrations are connected once for the Org, not per person and not per Client. What varies per Client is the Link that says which account over there is theirs.
| Integration | What it does |
|---|---|
| Stripe | Issues every Invoice, takes every card, and holds your Customers. Pippin’s books mirror it. |
| Plaid | Reads bank transactions. Read-only — it can never move money. |
| Gusto | Payroll. |
| Addigy | Reports device counts you bill from. |
| Pax8 | Reports license and seat counts you bill from, and can supply its own invoices. |
| Jira | Brings work across. |
Stripe is not optional. Pippin does not author Invoices; Stripe does, and the ledger records what Stripe did. Everything else on this list is.
Steps
- Open Settings › Integrations.
- Choose the integration and connect it. Each shows Connected or Not connected, so there is no guessing.
- For Addigy and Pax8, connecting is only half the job — each Client still needs a Link saying which policy or company is theirs. See Link a Client to Addigy or Pax8.
- Where an integration supports webhooks, turn them on. A vendor event makes Pippin re-read the counts straight away instead of waiting for the hourly sweep.
Good to know
Connecting an integration needs a Role holding the integrations permission. It is grouped with Administration rather than with day-to-day work, because a connection made wrong bills every Client wrong.
The hourly sweep keeps running even where webhooks are connected. Push is the fast path; the sweep is how you know the fast path was right.
An AI assistant is configured separately, under Settings › Assistant — Claude, ChatGPT and MCP tokens. It reads your books; it is not a vendor integration.