Understand what happens at the limit.

Incoming alert capacity and paid notification spending have separate safeguards. Configure both around the sources you connect and the channels your team needs.

Contain fresh triggers without preventing recovery.

Each integration key has a plan ceiling for new trigger events. Set a lower per-key ceiling to contain a noisy source. Acknowledge and resolve events do not consume fresh-trigger capacity; recognized idempotent retries do not consume it twice.

When a source exceeds its limit

New triggers receive a rate-limit response. Respect the returned retry delay. A separate active-incident ceiling also limits new incidents for a service.

Review capacity before connecting

Trial supports 60 fresh triggers per minute per key, Team 300, Business 1,000, and Enterprise 5,000.

Review the response path before relying on it.

Verify responder contact methods, current schedule coverage, matching policy steps, channel choices, and available credits. Use a labeled end-to-end test to confirm the configured path.

Read the product guide

Build a response people can follow.

Start a workspace, connect a service, and make the next signal reach its owner.

Start free