--- title: Integrations description: Where to find the Integrations page for a community and for a digital product, which connections each one offers, and what the Inactive and Active badges really mean. --- An integration connects one community or one digital product to something outside Insy — the account that takes the money, the Telegram or Discord server you gate, the service that issues an invoice, the analytics tools that count the visit. Each connection is stored against that single community or that single product, so a second community or a second product means walking through the same cards again from its own page. This section covers the integrations you set up yourself. Getting paid and connecting your Telegram group are covered in their own sections, linked at the bottom. ## Where to find it There are three screens called **Integrations**, and they are not the same page. This section covers the two that belong to something you sell: - **For a community** — open the community you manage and pick **Integrations** in its menu: `/managed//integrations`. - **For a digital product** — open the product and pick **Integrations** in its menu: `/products//integrations`. The third, under **Account → Integrations**, is a different thing entirely: it links *your own* Telegram and Discord accounts to Insy, and holds none of the cards below. ## What is on each page | Card | Community | Digital product | | --- | --- | --- | | Stripe | Yes | Yes | | Payment method | Yes | Yes | | Cryptocurrency fee / CoinPayments | Yes | — | | Telegram | Yes | — | | Discord | Yes | — | | Chat (experimental) | Yes | — | | Fakturownia | Yes | Yes | | inFakt | Yes | Yes | | Google Analytics | Yes | Yes | | Meta Pixel | Yes | Yes | | Custom Domain | — | Yes | Money, invoicing and analytics are on both pages. Telegram, Discord, the experimental chat and the crypto card exist only for a community; **Custom Domain** only for a digital product. The crypto card is titled **Cryptocurrency fee** until you finish the fee setup and **CoinPayments** after that, and the **Payment method** card appears at all only once Stripe is connected. ## What Inactive and Active mean Every card carries a badge. **Inactive** means Insy has nothing stored for this community or product yet. **Active** means it has something stored — it is a record of what you saved, not a health check of whether the other side is working. - **Stripe** — Active once a Stripe account is connected to this community or product. - **Payment method** — always Active. The badge carries no information; the card only renders when Stripe is already connected. - **Telegram** — Active only while a group is linked *and* the bot is still in it. If the bot is removed or kicked from the group, the card drops back to Inactive. - **Fakturownia** and **inFakt** — Active means an API key is stored. The key is never tested when you save it, so a wrong key stays green until a sale fails to produce an invoice. - **Google Analytics** and **Meta Pixel** — the only two that are verified before they are stored. Your credentials are sent to Google or Meta on save and rejected on the spot if they don't work. - **Custom Domain** — Active from the moment you add a domain, before any DNS is in place. Whether the domain actually serves your page — Pending, SSL Pending, Active or Error — is a second badge inside the card, behind **Manage Domain**. - **Chat (experimental)** — the card never reads its state back. After a page reload it shows Inactive and offers **Activate** again, whether or not you already switched it on. > **The red badge says Payment error, but no payment failed** > > When Fakturownia or inFakt rejects an invoice, the card turns red and the badge reads **Payment > error** — the same label Insy uses for failed payments elsewhere. Nothing is wrong with the sale or > the money. The invoicing provider refused the request, usually because the API key or subdomain is > wrong. See [Automatic invoices](/integrations/invoicing). > **Four integrations cannot be disconnected** > > Fakturownia, inFakt, Google Analytics and Meta Pixel have no disconnect button and no way to clear > what you saved — you can only overwrite the stored credentials with new ones. The ones that can be > undone are Telegram and Discord, which each carry a **Disconnect** button on the community page, and > Custom Domain, which has **Remove Domain** inside **Manage Domain**. ## Next Connect Fakturownia or inFakt, what lands on the invoice, and when no invoice is created at all. Send page views, checkouts and purchases to your own GA4 property or Meta pixel. Serve a digital product page from your own hostname — the DNS records, the certificate, the statuses. Covered with communities: the bot, the group, and how paying members are added and removed. The Stripe account behind the Stripe card, and the rail behind the crypto one.