# Connect it in five minutes, or send it yourself

Stripe, Polar, Lemon Squeezy and Paddle are detected automatically. Everything else works through one API call.

Canonical URL: https://whyleft.com/features/integrations

## Benefits

### Four providers, zero code

Connect the account and cancellations start flowing. Access is read-only and narrow — WhyLeft never touches card data and never modifies anything.

### Any other stack, one endpoint

POST a cancellation from wherever your own cancel logic lives. Everything downstream behaves identically to a detected one.

### Alerts where you already are

Slack notifications for the things worth interrupting you for: a reply landing, a high-MRR account leaving, a pattern emerging.

## The API is included

There's no add-on and no enterprise tier for it. Send cancellations in, receive events out through webhooks, and export everything you've collected whenever you want it.

The billing-provider integrations are a convenience, not a requirement. Plenty of businesses run entirely through the API because their cancel flow lives somewhere a webhook can't see.

## Automation without a native app

WhyLeft doesn't ship a native Zapier app today. Outbound webhooks cover the same ground — point one at Zapier, n8n, Make, or your own endpoint and react to WhyLeft events wherever you like.

We'd rather say that plainly than list a logo we haven't built.

## In practice: The homegrown billing stack

Your subscriptions live in your own database because of an old decision nobody wants to revisit. That's fine — one POST from the function that already handles cancellation, and the rest of WhyLeft works exactly as advertised.

## Related

- https://whyleft.com/features/exit-interviews
- https://whyleft.com/features/cancellation-capture
- https://whyleft.com/features/payment-recovery