Custom JSON HTTP POST Webhook Alerts

SimpleOps custom JSON webhooks enable automated incident workflows, allowing engineering teams to route downtime events into custom backend microservices, PagerDuty, automated DNS failover controllers, or serverless functions.

Automated Incident Workflows with Custom Webhooks

Standard chat and email notifications inform human operators about downtime, but automated infrastructure requires programmatic event triggers. SimpleOps webhooks send instant HTTP POST requests to your designated server endpoints the moment an incident is detected or resolved by our global monitoring network.

By automating incident response through webhooks, engineering teams can achieve zero-touch infrastructure remediation—automatically executing failover procedures, restarting frozen application containers, or spinning up backup server instances before human operators even review an incident report.

Webhook Payload Architecture & Schema

SimpleOps dispatches clean, structured JSON payloads containing complete diagnostic context:

{
  "event": "monitor.down",
  "monitor_id": "mon_12345",
  "name": "Production E-commerce API",
  "url": "https://api.example.com/checkout",
  "status": "down",
  "status_code": 500,
  "error_message": "Internal Server Error",
  "response_time_ms": 1240,
  "timestamp": "2026-07-26T19:40:00Z",
  "check_locations": ["us-east", "eu-central", "ap-south"]
}

Event Types Dispatched by Webhooks

• monitor.down: Dispatched when an endpoint fails HTTP status checks or times out across multi-region verification probes.
• monitor.up: Dispatched when an endpoint recovers and returns consecutive successful 2xx/3xx HTTP status codes.
• ssl.warning: Dispatched when an SSL certificate reaches 30-day, 7-day, or 1-day expiration warning thresholds.
• performance.degraded: Dispatched when synthetic Lighthouse performance scores or Core Web Vitals breach defined budgets.

Common Webhook Automation Use Cases

Integrating custom webhooks allows engineering teams to construct powerful automated DevOps pipelines:

1. Automated Traffic Failover: Reroute DNS records (via Cloudflare API or AWS Route 53) or CDN edge traffic away from a failing origin server to a static maintenance page or backup cloud region.
2. Serverless Remediation: Trigger an AWS Lambda function, Google Cloud Function, or Kubernetes Webhook controller to restart a frozen container or clear an overloaded Redis/Memcached cache pool.
3. Custom Incident Logging: Store raw downtime event logs in internal TimescaleDB, Datadog, Grafana, or Elasticsearch instances for compliance auditing and post-mortem analysis.
4. Third-Party Service Desk Integration: Automatically create and update tickets in Jira Service Management, Zendesk, or ServiceNow when outages occur and resolve.

Technical Webhook Security & Verification

To protect your receiving server endpoints against spoofing, replay attacks, or unauthorized HTTP requests, SimpleOps supports industry-standard security verification mechanisms:

• Custom Secret Token Headers: Include custom HTTP headers (such as X-SimpleOps-Secret: your_secret_token) in every webhook payload.
• HMAC Digest Signatures: Verify incoming payload integrity using SHA-256 HMAC signatures computed with your shared secret key.
• Fixed IP Egress Ranges: Configure your firewall rules to permit webhook traffic exclusively from official SimpleOps monitoring probe IP addresses.

Detailed Comparison: Webhooks vs Standard Alerting Channels

Engineering Guidelines for Implementing Webhook Handlers

When building an internal endpoint handler to process incoming SimpleOps webhooks, adhere to these technical best practices:

1. Fast Response Acknowledgment: Return a 200 OK status code immediately upon receiving and validating the request, deferring heavy background processing or API calls to an asynchronous task queue.
2. Idempotency Verification: Inspect the timestamp and monitor_id fields to ensure duplicate webhooks generated during retries do not trigger duplicate failover actions.
3. Signature Validation: Always compute the HMAC-SHA256 signature using your shared secret and compare it against the incoming HTTP signature header using a constant-time comparison function to prevent timing attacks.
4. Comprehensive Error Handling: Return appropriate HTTP status codes (such as 401 Unauthorized for bad signatures or 503 Service Unavailable for temporary queue degradation) so SimpleOps backoff retries behave predictably.

Step-by-Step Setup: Adding a Custom Webhook

Setting up a custom webhook channel in SimpleOps takes less than two minutes:

1. Navigate to Alert Settings: Open SimpleOps dashboard and go to Alert Settings -> Add Channel.
2. Select Webhook: Choose Custom Webhook (HTTP POST).
3. Enter Target Endpoint URL: Input your server endpoint URL (e.g., https://api.yourcompany.com/webhooks/simpleops).
4. Configure Custom Headers: Add any required authorization or secret key headers (e.g., Authorization: Bearer your_api_token).
5. Send Test Payload: Click Send Test Payload to verify that your receiving server endpoint processes the test JSON request cleanly.
6. Save Channel: Click Save Settings to enable live webhook dispatches.

Handling Webhook Failures & Retry Policies

If your receiving server endpoint experiences temporary downtime or returns a non-2xx HTTP status code, SimpleOps automatically initiates exponential backoff retries (retrying at 1-minute, 5-minute, and 15-minute intervals) to guarantee reliable delivery of critical incident notifications.

Building automated webhooks with SimpleOps ensures zero-touch infrastructure remediation, allowing your operations team to respond to incidents instantly, streamline DevOps workflows, eliminate manual intervention, and maintain maximum application uptime across global environments. Webhooks bridge the gap between real-time monitoring and automated cloud infrastructure management.