EventSend is an event tracking and routing service for product teams. Its core idea is "track once, deliver everywhere": an application only needs to send one HTTP request, and EventSend logs the event for search and analysis while distributing it to the communication channels the team uses every day, with no need to build your own bot or maintain infrastructure.
Purpose
EventSend is used to track key events in an application (such as sign-ups, payment failures, deployments, etc.) and route them in real time to Slack, Discord, Telegram, mobile push, or any Webhook. It is suitable for product teams and developers who need timely awareness of product activity without wanting to repeatedly build a notification system.
Main capabilities
- Event tracking and search: Log events to a searchable feed, providing analytics, usage statistics, and complete delivery history.
- Multi-channel routing: Distribute events to Slack, Discord, Telegram, Pushover, browser push, and custom Webhooks from a single HTTP POST.
- Source integrations: With no code required, paste a URL to connect Webhook events from third-party tools such as Stripe, GitHub, and Vercel into the pipeline, with automatic handling of signature verification, deduplication, and retries.
- Reliability guarantees: Signed Webhook delivery, automatic retries (with intelligent backoff), idempotent ingestion (preventing duplicates via unique_key), circuit breakers, distributed rate limiting, endpoint failure detection, and more.
- Signal management: Threshold alerts, event aggregation (merging identical events), quiet hours, and daily/weekly digests to reduce noise.
- AI assistant queries: Connect Claude or ChatGPT via MCP (Model Context Protocol) to query event history in natural language, for example "what errors happened last night", without digging through logs.
- Debug mode: Enable debugging per route to inspect events without logging or delivering them, making testing easier.
- Team collaboration: Support organizations and teams, invite members and assign owner, admin, and member roles, and share routes, channels, and history.
How to use
- Sign up and create a route, then copy its es_ token.
- From a backend, scheduled job, or CI script, send an HTTP POST containing a JSON payload to the endpoint (adding uni is recommendedque_key to achieve idempotency).
- Events are recorded and delivered to the destination channel you configure.
- If using a source integration, select Stripe, GitHub, or Vercel, copy the generated private Webhook URL, paste it into the corresponding service's backend, and enter the signing secret.
- When querying via the AI assistant, you can log in from claude.ai or ChatGPT, or paste the API key in Claude Code or Cursor.
Use Cases
- Product teams need to monitor key events such as sign-ups, payments, and deployments in real time.
- Developers want to quickly push events to chat tools without having to write and maintain notification infrastructure.
- Those using tools such as Stripe, GitHub, and Vercel want to unify the routing and formatting of their Webhook events.
- Need to use an AI assistant to quickly investigate event history, analyze reasons for user churn, etc.
Limitations
- The official text does not state whether all programming languages are supported, but notes that any stack capable of sending HTTP requests can be used, with no SDK required.
- The retention period for raw event data depends on the plan (7 days for free, 30/60/90 days for other plans, etc.), and daily counts are retained for 12 months.
- Pricing information (free tier 2,500 events/month, paid tiers starting at 50,000 events/month, with overages billed at $0.0005/event) comes from the official page; specific prices may change, so please refer to the official website.
- Some features (such as heartbeat monitoring and one-click resending of failed deliveries) are marked as "coming soon" and may not currently be available.
- The AI assistant has read-only permissions and will not change any data.
