Webhook Subscription Limits

What this means

Every CRM platform caps how many webhook subscriptions can be registered — sometimes per user, per app, or per plan tier. Playwise HQ registers one subscription for each record type you sync, and those subscriptions count against your CRM’s cap alongside any other apps you’ve connected there.

A subscription limit reached warning means Playwise tried to register a subscription but your CRM refused because the cap is full. It can affect all record types, or just one — for example, accounts and deals register fine but contacts fail because that last slot was taken.

Why it happens

• Other integrations or tools in your CRM are already using most of the available webhook slots.
• Old, unused webhooks left behind by apps you no longer use are still counting against the cap.
• Your CRM plan tier has a lower webhook allowance.

How to fix it

1. Open your CRM’s webhook or integration settings and look for webhooks you no longer need — especially ones pointing at tools you’ve stopped using. Remove them to free up slots.
2. In Playwise, open the integration’s Webhooks tab and use Manage Subscriptions to see which of your record types registered successfully and re-register any that failed.
3. If every existing webhook is genuinely needed, check whether a higher CRM plan tier raises the limit.

Record types that couldn’t register won’t sync in real time until a slot frees up — but nothing is lost. Once registered, new changes flow normally, and a backfill catches up anything from the gap.

Still stuck?

If you’ve freed slots and registration still fails, contact support and mention which record types are affected.