Integration Guides

Step-by-step guides for connecting CronBeats to your favorite tools

Plan requirements at a glance

Integration Plan Setup Format
Email Free+ None Text + HTML
Telegram Starter+ Medium Text
Slack Pro+ Easy Rich messages
Discord Pro+ Easy Embedded messages
Custom Webhooks Pro+ Medium JSON
Zapier / Make Pro+ Medium Flexible
📧

Email Integration Free+

Receive DOWN and RECOVERY alerts via email

How to Setup

  1. In CronBeats dashboard: Go to Integrations → Email
  2. Enter address: Type the email address where alerts should be sent
  3. Choose alert rules: Enable DOWN alerts, RECOVERY alerts, or both
  4. Save — alerts will send automatically, no test button needed

What you'll receive:

  • ✓ DOWN alert when a job fails or misses its schedule
  • ✓ RECOVERY alert when a job comes back up
  • ✓ Email includes job name, timestamp, and a direct dashboard link
  • ✓ Works with any email address — no extra service required
💬

Slack Integration Pro+

Get rich, formatted alerts in your Slack channels

How to Setup

  1. In Slack: Create an Incoming Webhook URL at api.slack.com/apps
  2. In CronBeats: Go to Integrations → Slack and paste your webhook URL
  3. Test it: Click "Send Test Message" to verify it works
  4. Enable: Check the "Enable Slack notifications" checkbox

What you'll receive:

  • ✓ Job state changes (healthy → late → down → recovered)
  • ✓ Real-time job progress updates
  • ✓ Beautifully formatted messages with job details
  • ✓ Customizable notification frequency
🎮

Discord Integration Pro+

Send formatted alerts to Discord servers and channels

How to Setup

  1. In Discord: Right-click your server → Server Settings → Integrations → Webhooks
  2. Create Webhook: Click "New Webhook" and choose your target channel
  3. Copy URL: Copy the webhook URL
  4. In CronBeats: Go to Integrations → Discord and paste the webhook URL
  5. Test it: Click "Send Test Message"

What you'll receive:

  • ✓ Embedded, color-coded alert messages
  • ✓ Job name, workspace, and state information
  • ✓ Timestamps for every alert
  • ✓ Customizable notification triggers
📱

Telegram Integration Starter+

Get mobile notifications via Telegram

How to Setup

  1. Create Bot: Talk to @BotFather on Telegram and create a new bot
  2. Copy Token: Copy the bot token (e.g., 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11)
  3. Get Your User ID (Easy Way):
    • Talk to @userinfobot on Telegram
    • It will immediately reply with your User ID
    • OR (harder): Send a message to your bot, then visit https://api.telegram.org/bot[YOUR_TOKEN]/getUpdates
  4. In CronBeats: Paste both the Bot Token and Chat ID (your User ID)
  5. Test it: Click "Send Test Message"

What you'll receive:

  • ✓ Instant mobile push notifications
  • ✓ Job alerts with full details
  • ✓ Works on iOS, Android, and desktop
  • ✓ Perfect for on-call monitoring
🔗

Custom Webhooks Pro+

Send alerts to any custom HTTP endpoint

What It Does

Send a JSON POST request to any HTTP endpoint when jobs trigger alerts. Perfect for:

  • Custom internal systems
  • Logging platforms (Splunk, ELK, Datadog)
  • Incident management (PagerDuty, Opsgenie)
  • Automation workflows via Zapier/Make
  • Ticketing systems (Jira, Linear, etc.)

Webhook Payload Examples

CronBeats sends a small integration.test payload for connection tests and a richer payload for real alert events.

Connectivity test payload

{
  "event": "integration.test",
  "source": "cronbeats",
  "channel": "webhook",
  "message": "Webhook integration test from CronBeats",
  "workspace_id": 123,
  "sent_at": "2026-02-24 12:06:54 UTC"
}

Production alert payload

{
  "schema_version": "1.1",
  "event": "job.down" | "job.recovery",
  "notification_type": "down" | "recovery",
  "job": {
    "id": 42,
    "name": "Database Backup",
    "schedule_value": "3600",
    "expected_interval_seconds": 3600
  },
  "workspace": {
    "id": 7,
    "name": "Production"
  },
  "timestamp": "2026-02-24T12:06:54+00:00",
  "message": "Job 'Database Backup' is DOWN",
  "dashboard_url": "https://cronbeats.com/jobs/42"
}

How to Setup

  1. Prepare endpoint: Create an HTTP endpoint that accepts POST requests
  2. Optional secret: Generate a secret for signature verification (HMAC-SHA256)
  3. In CronBeats: Go to Integrations → Webhooks and enter your URL
  4. Test connectivity: Click "Send Test Webhook" and verify the integration.test payload arrives
  5. Verify production shape: Trigger a real DOWN/RECOVERY and confirm the production payload above
  6. Verify signature: Check the X-CronBeats-Signature header for security

How To Use Secret Key

CronBeats never sends your raw secret to the endpoint. Instead it signs each request and sends only X-CronBeats-Signature.

  1. Keep one shared secret in both CronBeats and your receiving service.
  2. Read the raw body on your endpoint.
  3. Compute HMAC-SHA256 using that raw body + secret.
  4. Compare your result with the X-CronBeats-Signature header using a timing-safe compare.

If someone sends fake DOWN/RECOVERY webhooks to your URL, verification fails unless they know your secret. Test signature verification on both integration.test and production alert events.

Pro Tip: Use Zapier or Make with webhooks to connect to 8000+ services without custom code.

What you'll receive:

  • ✓ JSON POST to your endpoint on every DOWN or RECOVERY event
  • ✓ Optional HMAC-SHA256 signature in the X-CronBeats-Signature header
  • ✓ Test payload available on demand to verify connectivity before going live

Zapier / Make Integration Pro+

Connect CronBeats to 8000+ apps via webhooks

With Zapier or Make as the action layer, CronBeats alerts can create tickets in Jira or Linear, trigger PagerDuty incidents, send SMS via Twilio, post to Google Chat, or run any automation across 8,000+ supported services — without writing any custom code.

How to Setup (Zapier)

  1. Create Zap: Go to zapier.com and create a new Zap
  2. Trigger: Choose "Webhooks by Zapier" as your trigger
  3. Get Webhook URL: Zapier will give you a unique webhook URL
  4. In CronBeats: Add that URL as a custom webhook in Integrations → Zapier
  5. Choose Action: Set up your action (create ticket, send alert, etc.)
  6. Test & Publish: Test your Zap and turn it on

How to Setup (Make)

  1. Create Scenario: Go to make.com and create a new Scenario
  2. Add Trigger: Click the plus icon and search for "Webhooks" module
  3. Choose Trigger: Select "Custom webhook"
  4. Get Webhook URL: Make will generate a unique webhook URL — copy this URL
  5. In CronBeats: Paste the webhook URL in Integrations → Zapier
  6. Add Action: Click the plus icon to add what happens next (send to Jira, Slack, etc.)
  7. Map Fields: Connect CronBeats data to your action fields
  8. Test & Activate: Test your scenario, then turn it on

Webhook URL format examples

Zapier: https://hooks.zapier.com/hooks/catch/123456/abcdefg

Make: https://hook.make.com/v1/abc123def456ghi789jkl

Example: PagerDuty incidents via Zapier

Set "Webhooks by Zapier" as trigger → "PagerDuty: Create Incident" as action. Map the CronBeats job.name, event, and message fields to the incident severity, summary, and description. When a job goes DOWN, a P1 incident is automatically created in PagerDuty.

What you'll receive (in Zapier/Make):

  • ✓ The same JSON payload as a custom webhook — all fields available to map
  • ✓ Triggered on every DOWN or RECOVERY event
  • ✓ Use any Zapier/Make action: create ticket, send SMS, trigger incident, log to spreadsheet

Frequently Asked Questions

Can I use multiple integrations at the same time?

Yes. Enable as many integrations as you want. Alerts will be sent to all configured channels simultaneously.

Are webhooks secure?

Yes. When CronBeats sends webhook notifications to your server, we include an optional HMAC-SHA256 signature in the X-CronBeats-Signature header.

You provide a secret key in CronBeats. We use it to sign every webhook. Your server verifies the signature to confirm the request actually came from CronBeats and not a third party.

What if an integration fails?

CronBeats retries failed notifications automatically with exponential backoff. Check your integration settings if alerts stop arriving.

Can I filter which alerts go to which channel?

Currently all integrations receive the same alerts. For granular filtering, use Zapier or Make to create custom workflows based on job name, state, or workspace.

Ready to set up integrations?

Go to your integrations page and start connecting your favorite tools

Go to Integrations →