Integrations

12 items

Revenue, usage, feedback, and action — in one loop.

Keep reads revenue from Stripe, AbacatePay, or Asaas, usage from PostHog or its activity API, and context from HubSpot and Intercom. It alerts in Slack or email, turns risk into Linear issues, and asks your users with its own survey widget.

Revenue

Who pays and how much. Keep reads it and never writes to your billing.

  • Stripe Connect

    Stripe

    Subscriptions, customers, cancellations, downgrades, and failed payments. No keys stored; nothing written.

  • Read-only API key

    AbacatePay

    Card and Pix subscriptions added to your MRR, with an optional webhook for cancellations as they happen.

  • API key

    Asaas

    Subscriptions and customers from Asaas, with an optional webhook for overdue payments. Production or sandbox, detected.

Usage

Who still uses the product — the signal billing cannot see.

  • OAuth, read-only

    PostHog

    Per-person usage matched to paying customers and summed per company, to flag accounts that dropped or went silent.

  • HTTP API

    Keep Activity API

    Send activity from your backend, keyed by Stripe customer id or email, with optional feature names. Batches of up to 500.

CRM and support

Who owns the account and whether anyone is already talking to them.

  • OAuth, read-only

    HubSpot

    Account owner, lifecycle stage, and last contact on every account, matched by company domain.

  • OAuth

    Intercom

    Open conversations beside every account, and an internal note on the contact when it becomes at risk.

Communication

Where the team hears about it.

  • Incoming webhook

    Slack

    Alerts in the channel you pick. Keep can post there and cannot read messages. Risk alerts have buttons: Already talked to them, Not a risk, Remind me in 7 days.

  • Built in

    Email

    The same alerts by email, and the fallback when Slack is not connected or a delivery fails.

Action

Turning risk into work someone owns.

  • OAuth, two-way sync

    Linear

    At-risk accounts open issues with the reason and the MRR at stake. Status, assignee, and comments sync both ways; issues settle when the account recovers.

  • OAuth, one-way sync

    Notion

    Paying customers in a Notion database — MRR, status, risk, renewal, NPS, owner — kept up to date. No duplicates; pages are never deleted.

Feedback

What customers say, next to what they pay.

  • Keep SDK

    Survey widget

    NPS, CSAT, CES, and custom surveys inside your product, each answer tied to the account's MRR and risk.

Start with your billing. Add the rest when you need it.

Revenue alone gives you MRR and churn alerts. Usage, context, and feedback make them sharper.