Skip to content
The Social Tools The Social Tools Docs

Webhooks by plan, and the downgrade grace

Outgoing webhooks are a plan-gated feature, and the endpoint card on the Delivery page is careful to distinguish your switch from the plan’s. This page explains which plans include webhooks, what happens to endpoints when a plan stops covering them, and why an endpoint is never deleted by a billing change.

Which plans include webhooks

Section titled “Which plans include webhooks”
PlanOutgoing webhooks
BaseNot included
ProIncluded
PremiumIncluded, plus custom webhook retry

On Base, creating or enabling a webhook endpoint is refused as a plan-gated feature — the refusal names the plan that includes it.

Two switches on one endpoint

Section titled “Two switches on one endpoint”

Every endpoint carries two independent switches, and the card never merges them:

  • Enabled / Disabled is the owner’s switch — the toggle on the card. You turned it off; you can turn it back on.
  • The plan gate is the system’s. The payer moved to a plan without webhooks and delivery stopped. No toggle on the card clears it — upgrading does.

This distinction is why the card will never tell you that you disabled an endpoint you never touched: a plan-gated endpoint shows its own badge and notice beside the Enabled/Disabled chip, not instead of it.

The 30-day grace, then the pause

Section titled “The 30-day grace, then the pause”

An account that ends up on a plan without webhook entitlement is not cut off at that moment. Its endpoints enter a 30-day grace period, and the endpoint card walks through the states in the order they occur:

StateBadgeWhat the card says
Entitled (the normal case)—No plan notice at all
In grace, still deliveringPlan grace (amber)“Your plan does not include webhooks — delivery stops on <date> (in N days). Upgrade to keep it.”
Grace expired, sweep pendingPlan grace (amber)The same deadline, worded as “any moment now” — the pause sweep runs daily, so an endpoint can sit past its deadline for up to a day before delivery actually stops
PausedPaused by plan (red)“Webhooks are paused — your plan does not include them. Upgrade to resume delivery.”
An endpoint card on the Delivery page showing the amber Plan grace badge and the delivery-stops-on date
In grace: still delivering, with the date delivery stops and the way to keep it.
An endpoint card showing the red Paused by plan badge with the upgrade-to-resume notice
Paused by plan: the system's switch, cleared by upgrading — not by the Enable toggle.

Upgrading restores everything in one step, without waiting for the daily sweep: paused endpoints resume, grace countdowns clear.

Downgrading to Base is blocked while endpoints are enabled

Section titled “Downgrading to Base is blocked while endpoints are enabled”

Because Base includes no webhooks at all, a move to Base is refused while any webhook endpoint is enabled — the refusal names the count: “Base cannot carry what this account is using: 2 webhook endpoints are enabled (Base does not include webhooks). Remove them first, then switch to Base.” (The same pre-flight blocks the move while extra team seats are in use.)

Disable or delete the endpoints yourself, then downgrade. The grace period above is for entitlement that lapses on its own — a deliberate move to Base asks you to choose first rather than silently starting a 30-day countdown.

Section titled “Related”