# EventSend > EventSend tracks your app's events in a searchable feed with analytics, then routes them to Slack, Discord, Telegram, push and webhooks from one HTTP POST. Docs: https://eventsend.io/docs ## Get started - [EventSend Documentation](https://eventsend.io/docs): Track an event with one HTTP request: EventSend records it for search and analytics, then routes it to Slack, Discord, Telegram, push or a webhook. - [Quickstart](https://eventsend.io/docs/quickstart): Track your first event in 60 seconds with one HTTP POST — copy-paste snippets for curl, JavaScript, Python, Elixir, and Go. - [Concepts](https://eventsend.io/docs/concepts): How routes, sources, topics, destinations and connections fit together, what EventSend records for every event, and how routing rules decide delivery. ## API - [Events API](https://eventsend.io/docs/api): Reference for POST /api/events — fields, limits, levels, idempotency, rate limits, and every response code. - [Webhook signatures](https://eventsend.io/docs/webhook-signatures): Verify that a webhook delivery really came from EventSend using HMAC-SHA256, with snippets for Node.js, Python, and Elixir. - [Delivery and retries](https://eventsend.io/docs/delivery): What EventSend promises about delivering an event: the retry schedule, the 24-hour freshness ceiling, which failures are retried, duplicates, and replays. - [MCP server](https://eventsend.io/docs/mcp): Connect Claude, Cursor or ChatGPT to your EventSend events — endpoint, authentication, client setup, and the tool reference. ## Sources - [Stripe source](https://eventsend.io/docs/sources/stripe): Turn Stripe webhooks into EventSend events with no code — setup steps, the default event mapping, and how to test it. - [GitHub source](https://eventsend.io/docs/sources/github): Turn GitHub webhooks into EventSend events with no code — setup steps, the default event mapping, and how to test it. - [Vercel source](https://eventsend.io/docs/sources/vercel): Turn Vercel deployment webhooks into EventSend events with no code — setup steps, the event mapping, and why two of them ship switched off. ## Recipes - [Stripe revenue alerts in 2 minutes](https://eventsend.io/docs/recipes/stripe-revenue-alerts): Get a cha-ching in Slack the next time someone pays you — connect Stripe to EventSend with no code. - [Deploy notifications](https://eventsend.io/docs/recipes/deploy-notifications): Tell your team when CI ships — one curl in your pipeline, routed to chat, with commit SHAs as idempotency keys. - [Error alerts to Telegram](https://eventsend.io/docs/recipes/telegram-error-alerts): Send application errors to your phone via Telegram, filtered so only the things that matter interrupt you. ## Alerting - [Threshold alerts](https://eventsend.io/docs/alerting/threshold-alerts): Fire one critical alert when matching events spike on a route — so a burst of 200 errors wakes you once, not 200 times. - [Rollups](https://eventsend.io/docs/alerting/rollups): Collapse a burst of repeated events into one summary message, so a broken payment provider costs you one notification instead of two hundred. - [Quiet hours](https://eventsend.io/docs/alerting/quiet-hours): Hold everything except critical events during a nightly window, in your organization's time zone, so only real emergencies wake you at 3am. - [Email digests](https://eventsend.io/docs/alerting/digests): A daily or weekly summary of your busiest events, delivery failures, and everything quiet hours or rollups held back. ## For AI assistants - [MCP server](https://eventsend.io/docs/mcp): a read-only MCP server at https://eventsend.io/mcp. Connect Claude, ChatGPT or Cursor and ask what happened in the product, in plain language: events, deliveries, daily counts and quota. ## AI coding tools - [EventSend for Cursor](https://eventsend.io/for/cursor): Paste one prompt into Cursor's Agent chat to add Slack, Discord, Telegram and push alerts for signups, payments and failures. Token in .env, never in code. - [EventSend for Claude Code](https://eventsend.io/for/claude-code): Run one prompt in Claude Code to add Slack, Discord, Telegram and push alerts for signups, payments and failures, with a CLAUDE.md note so it is wired once. - [EventSend for Codex](https://eventsend.io/for/codex): Hand Codex one prompt to add Slack, Discord, Telegram and push alerts for signups, payments and failures, with an AGENTS.md note so future tasks reuse it. - [EventSend for Devin Desktop](https://eventsend.io/for/devin): Paste one prompt into Devin Desktop's Cascade to add Slack, Discord, Telegram and push alerts for signups, payments and failures. Server-side, token in .env. - [EventSend for GitHub Copilot](https://eventsend.io/for/github-copilot): Paste one prompt into Copilot Chat in agent mode to add Slack, Discord, Telegram and push alerts for signups, payments and failures. No code to write yourself. - [EventSend for Lovable](https://eventsend.io/for/lovable): Paste one prompt into Lovable to add Slack, Discord, Telegram and push alerts for signups, payments and failures. Token kept as a backend secret, not in React. - [EventSend for Bolt](https://eventsend.io/for/bolt): Paste one prompt into Bolt to add Slack, Discord, Telegram and push alerts for signups, payments and failures, in server code and out of the browser bundle. - [EventSend for v0](https://eventsend.io/for/v0): Paste one prompt into v0 to add Slack, Discord, Telegram and push alerts for signups, payments and failures from Route Handlers and Server Actions only. - [EventSend for Replit](https://eventsend.io/for/replit): Paste one prompt into Replit Agent to add Slack, Discord, Telegram and push alerts for signups, payments and failures. Token in Replit Secrets, not in a file. ## Comparisons - [LogSnag alternative](https://eventsend.io/alternatives/logsnag): EventSend vs LogSnag: the same free tier, lower prices at every paid tier, a searchable event feed, and alerts in Slack, Discord, Telegram or on your phone. - [Zapier alternative](https://eventsend.io/alternatives/zapier): Zapier bills a task for every alert to every channel. EventSend counts each event once, with alerts in Slack, Discord, Telegram and on your phone. - [PagerDuty alternative](https://eventsend.io/alternatives/pagerduty): Need alerts, not on-call rotations? EventSend sends critical events to Slack, Telegram or your phone, on flat plans instead of per-user pricing. ## Tools - [Webhook signature checker](https://eventsend.io/tools/webhook-signature-checker): Check a Stripe, GitHub, Vercel, Slack or EventSend webhook signature and see why it fails. It runs in your browser, so nothing you paste is sent. ## Blog - [Ask your AI what happened: EventSend's MCP server](https://eventsend.io/blog/ask-your-ai-what-happened): Connect Claude, Cursor or ChatGPT to EventSend's read-only MCP server and ask what failed, how many, and what a customer did, from the assistant you use. - [Vibe-coded app monitoring: who tells you it broke?](https://eventsend.io/blog/vibe-coded-app-monitoring): Cursor, Lovable and Bolt build the app but never tell you a webhook stopped verifying. Instrument failure paths with one prompt and route them to your phone. - [Slack webhook failed at 2am? Nothing retried it](https://eventsend.io/blog/slack-webhook-failed-at-2am): A pasted Slack incoming webhook has no retries, no history, no filters and no fan-out. What that costs at 2am, and what one POST to a router gives you instead. ## Optional - [Privacy Policy](https://eventsend.io/privacy): What EventSend collects, why, how long it is kept, and the choices you have. - [Terms of Service](https://eventsend.io/terms): The agreement between you and EventSend: your account, your content, fees, and the limits of what we promise.