Alerts & Integrations
Alerts and integrations
Connect account-level destinations and review delivery history.
Integrations send selected PingAgain events to tools your team already uses. Destinations belong to the active account and can cover all monitors or a selected set.
Account-level destinations
Open Integrations and choose:
- Slack — a Slack Incoming Webhook for a channel.
- Microsoft Teams — a supported Teams Workflows webhook.
- Google Chat — an Incoming Webhook for a Workspace space.
- Generic Webhook — a signed HTTPS request to your own endpoint.
Enter a clear connection name, choose the incident events and monitor scope, then save the destination. Provider webhook URLs are secrets; do not paste them into tickets, screenshots, or monitor names.
Delivery lifecycle
A new or replaced destination must pass a test before it can be enabled. Delivery history shows attempts and safe error messages without revealing the full provider URL.
Disable a destination to stop new messages without deleting its history. If PingAgain suspends it after delivery failures, follow the displayed recovery instructions. An endpoint blocked by destination policy must be replaced with an allowed provider URL before testing.
Workspace permissions and availability come from Slack, Microsoft, or Google. Use the recorded test and Delivery history result to confirm what happened to a message.
Next: configure Slack, Microsoft Teams, Google Chat, or a Generic Webhook.