Integrations
Crontinel fires alerts through your existing channels. Configure Slack, PagerDuty, email, and webhooks in your .env with no dashboard required, or add Discord, Microsoft Teams, and Telegram from the cloud dashboard.
Email (Laravel Mail)
AvailableInstall Crontinel in a Laravel application. Configure the OSS package, publish migrations, set alert channels, and connect to the cloud dashboard in under 10 minutes.
Microsoft Teams
AvailableSend Crontinel Laravel monitoring alerts to Microsoft Teams using an Incoming Webhook connector on your team channel.
PagerDuty
AvailableCreate and auto-resolve PagerDuty incidents from Crontinel. Use Events API v2 with dedup keys to get one incident per failure, not a flood of alerts.
Slack
AvailableSend Crontinel alerts to Slack. Configure an incoming webhook, choose a channel, and get notified immediately when a Laravel cron job fails or Horizon supervisor pauses.
Discord
AvailableRoute Crontinel Laravel alerts to Discord with a webhook URL. Get notified when scheduled tasks fail, queues back up, or Horizon supervisors pause.
Webhook
AvailableSend Crontinel alerts to any HTTPS endpoint via webhook. Build custom alert routing, connect to Opsgenie, or handle alerts in your own infrastructure.
Telegram
AvailableDeliver Crontinel Laravel alerts to Telegram via bot API or webhook relay. Good for solo founders and small teams who live in Telegram.
Coming soon
Opsgenie
SoonRoute alerts to Opsgenie teams. Full incident lifecycle support with auto-resolve on recovery.
Alert config reference
CRONTINEL_ALERT_CHANNEL slack | mail | webhook | null CRONTINEL_SLACK_WEBHOOK Your Slack incoming webhook URL CRONTINEL_ALERT_EMAIL Email address to notify CRONTINEL_WEBHOOK_URL HTTPS endpoint for alert POSTs CRONTINEL_PAGERDUTY_ROUTING_KEY PagerDuty Events API v2 routing key