Skip to main content
Webhook Integration

Connect BlackTide Alerts to Any System via Webhooks

Not every team uses Slack or PagerDuty — and even those that do often need alerts to trigger custom backend logic, automation workflows, or internal tooling. BlackTide webhooks deliver rich JSON payloads to any HTTP endpoint the moment a monitor status changes, giving you complete control over what happens next.

Start Free — Add a WebhookView payload schema
Any HTTP
Compatible endpoint
HMAC-SHA256
Payload signing
Custom
JSON payloads
<5s
Delivery latency

Why fixed alert integrations limit your incident workflow

  • Pre-built integrations (Slack, email) are one-size-fits-all — they cannot trigger custom internal scripts, update your CMDB, or feed your proprietary incident management system
  • No way to chain alerts into automation workflows: when a node goes down, you want to auto-scale standby nodes, update a status page, and create a JIRA ticket — none of that is possible with a static Slack message
  • Tools like Zapier and n8n can automate almost anything, but they require an incoming webhook trigger from your monitoring tool — without one, the automation never starts. Zapier webhook triggers
  • Alert payloads from most monitoring tools are generic — no chain-specific data, no block height, no smart contract address — making downstream automation logic brittle and error-prone
  • Security: unsigned webhooks can be spoofed. Without HMAC verification your backend cannot confirm that the payload actually came from your monitoring platform

How BlackTide webhooks give you full integration flexibility

  • POST a rich JSON payload to any URL when a monitor changes status — trigger Zapier automations, n8n workflows, Make scenarios, or your own backend API with a single configuration
  • Payloads include all monitor context: monitor ID, name, type, status transition, affected chain, block height at time of failure, check timestamp, and incident URL
  • HMAC-SHA256 signing: every webhook request includes an X-BlackTide-Signature header so your endpoint can verify the payload is authentic and untampered before processing
  • Configurable retry logic with exponential backoff ensures delivery even when your endpoint is temporarily unavailable — with a full delivery log per event

Capabilities

Everything you need for webhook-driven alert automation

Webhooks that carry enough context to automate your entire incident response workflow.

Rich JSON payloads

Every webhook delivery includes a structured JSON body with monitor ID, name, type (RPC, node, gas price, whale wallet, etc.), previous status, new status, affected chain, block height, check timestamp, incident ID, and a direct URL to the BlackTide incident page. Downstream automation can make decisions based on chain, monitor type, or severity without any additional API calls.

HMAC-SHA256 payload signing

Each webhook request includes an X-BlackTide-Signature header computed as HMAC-SHA256 of the raw request body using your secret key. Your endpoint can verify this signature before processing the payload, preventing spoofed requests. Secret rotation is supported without downtime via a brief dual-signature acceptance window.

Automatic retry with backoff

If your endpoint returns a non-2xx response or times out, BlackTide retries with exponential backoff — up to 5 attempts over 30 minutes. Every delivery attempt is logged with the response code and latency so you can debug delivery failures without guessing. A dead-letter notification fires if all retries are exhausted.

Connect to any automation platform

Zapier, n8n, Make (Integromat), Pipedream, and any custom HTTP server can receive BlackTide webhooks. Use them to create JIRA tickets on P1 incidents, update your internal status dashboard, trigger PagerDuty via Zapier if you prefer that routing, spin up standby infrastructure via an internal API, or post richly formatted alerts to a custom Discord bot.

Per-monitor and per-severity webhook routing

Configure different webhook URLs for different monitors or alert severities. Route all P1 production incidents to your incident management backend and P3 degradation warnings to your logging pipeline. A single BlackTide account can have unlimited webhook channels, each with its own URL, secret, and filter configuration.

Use Cases

What teams build with BlackTide webhooks

Auto-scaling standby infrastructure on node failure

When BlackTide detects a primary RPC node is down, a webhook triggers an n8n workflow that calls your cloud provider API to spin up a standby node and update your load balancer configuration — fully automated, zero human intervention.

Custom incident management system integration

Your team uses an internal incident platform instead of PagerDuty. BlackTide webhooks POST incident data to your platform's API, creating tickets with full blockchain context — chain, monitor type, block height, severity — that your system can use for routing and escalation.

Multi-platform alert fan-out via Zapier

A single BlackTide webhook triggers a Zapier automation that simultaneously posts to Slack, creates a Linear ticket, updates a Google Sheets incident log, and sends an SMS via Twilio. One integration, unlimited downstream actions — no custom code required.

Frequently asked questions

How do I add a webhook in BlackTide?
Go to Settings → Alert Channels → Add Channel → Webhook. Enter the target URL and optionally set a secret for HMAC signing. Assign the webhook to one or more monitors or alert rules. You can send a test event from the configuration page to verify delivery before going live.
What does the webhook JSON payload look like?
The payload includes: event_type (alert.triggered, alert.resolved, incident.created), monitor_id, monitor_name, monitor_type, status (up/down/degraded), previous_status, chain, check_timestamp, incident_id, incident_url, severity (p1–p3), and a metadata object with type-specific fields such as block_height for RPC monitors or gas_price_gwei for gas monitors. Full schema documentation is available at blacktide.xyz/docs/api.
How do I verify that a webhook request came from BlackTide?
BlackTide signs every request using HMAC-SHA256 with your configured secret. The signature is sent in the X-BlackTide-Signature header as sha256=<hex_digest>. In your endpoint handler, compute HMAC-SHA256 of the raw request body using your secret and compare it to the header value. Reject requests where the signatures do not match.
What happens if my endpoint is down when an alert fires?
BlackTide retries the delivery with exponential backoff: immediately, then after 1 minute, 5 minutes, 15 minutes, and 30 minutes. Each attempt is logged with the response code received. If all 5 attempts fail, BlackTide sends a notification via your other configured alert channels (email, Slack) so you know a webhook delivery failed.
Can I connect BlackTide webhooks to Zapier or n8n?
Yes. Use BlackTide's webhook URL as the source trigger in Zapier (choose "Webhooks by Zapier" → "Catch Hook") or in n8n (use the Webhook node). Paste the generated Zapier or n8n webhook URL into BlackTide as the destination. Once connected, every BlackTide alert event will trigger your automation workflow with the full JSON payload available as variables.

Ready to connect BlackTide to your stack via webhooks?

Any HTTP endpoint. HMAC-signed. Rich JSON payloads. Zero code required to get started.

Start freeSee all integrations