Introducing the PulsAPI Integrations Hub: Slack, Discord, MS Teams & PagerDuty

Until now, connecting PulsAPI to your team's communication tools meant configuring a webhook URL on each individual service subscription. If your team monitors 40 services and uses Slack for alerting, that was 40 separate webhook fields to manage. Not anymore.

Today we're launching the PulsAPI Integrations Hub — a centralized settings page where you connect your alerting tools once, at the account level, and they apply everywhere. Slack, Discord, Microsoft Teams, and PagerDuty are all supported from day one.

The Integrations Hub is available on Pro plans and above. PagerDuty on-call integration is available on Business plans and above.

Slack integration connects to any channel via an Incoming Webhook. When PulsAPI detects a status change on any of your monitored services, it posts a rich alert message with the service name, new status, severity, and a direct link to the incident timeline.

Discord integration works the same way — paste a webhook URL from your Discord server settings and PulsAPI will post formatted alerts to your ops channel. It takes under 30 seconds to set up.

Microsoft Teams integration uses the Incoming Webhook connector built into Teams channels. Alerts arrive as Adaptive Cards with service name, status, severity badge, and timestamp — designed to fit naturally into your team's workflow.

PagerDuty integration is our deepest channel yet. Using a PagerDuty Events API v2 routing key, PulsAPI triggers incidents in your on-call system whenever a critical status change is detected. This means your on-call engineer gets paged automatically — no manual escalation needed.

Setting up an integration takes less than a minute. Go to Settings → Integrations, click Connect on the integration you want, and paste in your webhook URL or API key. Every integration includes a Test button that sends a sample payload so you can verify the connection before any real alerts fire.

Once connected, the integration applies globally. When PulsAPI's alert routing engine processes a status change event, it checks your active integrations and dispatches to all of them automatically. You don't need to update individual service subscriptions.

Your existing per-subscription Slack webhooks continue to work. If you have a global Slack integration connected, PulsAPI will prefer it for global routes. Per-subscription webhooks still work as a fallback — ensuring no disruption to existing alert configurations.

If you're on a Pro or higher plan, head to Settings → Integrations to connect your first integration. Business plan users can also set up PagerDuty for automated on-call escalation.

Full setup guides for each integration are available in our documentation: Slack, Discord, MS Teams, and PagerDuty. Each guide covers webhook setup, test verification, and tips for organizing alerts by team or environment.

We'll be adding more integrations — including Opsgenie, Datadog Events, and Jira — in the coming months. If there's a tool your team relies on that you'd like to see, let us know at hello@pulsapi.com.