Integrations
Wire Drumbeats into your stack. One HTTP request per job — no SDK required. Pick your language or platform below.
Drumbeats integrates with any stack that can send an HTTP request. There is no SDK to install and no authentication on ping endpoints — one curl or fetch per job is enough. The pages below cover the recommended pattern for each language and platform.
Choose your stack
| Stack | Guide | When to pick this |
|---|---|---|
| Node.js / TypeScript | Node.js integration | Express / Fastify / Nest / NextAuth jobs, Lambda handlers, Bun / Deno scripts. |
| Python | Python integration | Django / Celery / Airflow tasks, FastAPI background jobs, plain scripts. |
| Go | Go integration | Long-running workers, gRPC services, CLI cron jobs. |
| PHP | PHP integration | Laravel scheduled tasks, Symfony Messenger consumers, WordPress crons. |
| Shell / Bash | Shell integration | System cron, container entrypoints, glue scripts, one-off make targets. |
| GitHub Actions | GitHub Actions integration | Workflow jobs and scheduled CI runs. |
| Kubernetes | Kubernetes integration | CronJob and Job resources. |
| AI agent | AI agent integration | Manage monitors from Claude, Cursor, or VS Code via the Drumbeats MCP server. |
Once you have picked
Every guide follows the same shape so you can jump between them without re-learning the model:
- Quick example — minimal
start/success/failureping inline in a job. - Centralized setup — one config module that stores monitor IDs and exposes
wrap(monitorId, fn). - Error handling — catch / except / defer patterns that always send the right event.
- Production patterns — retries on the ping side, payload size limits, observability hooks.
Read the Node.js guide once to see the shape — every other language guide mirrors it.
Cross-cutting reference
These pages apply regardless of language:
- Ping API — the HTTP surface every integration is calling.
- Monitor types — Cron, Heartbeat, Event-driven, Uptime. Pick the one that matches the workload before wiring pings.
- Production hardening — retries, timeouts, observability patterns to harden any integration.
- Alternatives — how Drumbeats compares to Cronitor / Healthchecks.io / Dead Man's Snitch when you are evaluating stacks side-by-side.