{"slug": "show-hn-eventkiwi-scheduled-reports-for-your-app-s-events", "title": "Show HN: Eventkiwi – Scheduled reports for your app's events", "summary": "Eventkiwi launched as a hosted event-reporting service that ingests events through a single HTTP GET or POST request, aggregates counts per event and tag, and delivers scheduled reports by email or Telegram, each opening with an AI-generated summary built on the counted figures. The service requires no SDK or hosting, supports hourly, daily, weekly or monthly schedules in the user's timezone, and claims each schedule before sending so overlapping runs cannot deliver the same report twice; failed deliveries carry the period's events into the next report. Eventkiwi offers a free 100-event trial and plans of 10,000 events per month (about 330 a day) and 50,000 events per month (about 1,650 a day), with every feature included on all plans.", "body_md": "Send events from any service through one API. Eventkiwi aggregates them, compares each period with the ones before and delivers a scheduled report by email or Telegram, opening with an AI summary built on exact numbers.\n\nNo credit card. Every feature included.\n\nIf your code can make an HTTP request, it can use Eventkiwi. There is no SDK to install and nothing to host.\n\nStep 1\n\nOne GET or POST from your backend, app or no-code tool. Extra parameters become tags, like the plan someone bought.\n\n```\ncurl \"https://app.eventkiwi.com/api/event\\\n?_id=AGGREGATOR_ID&_apikey=API_KEY\\\n&name=order_paid&plan-pro\"\n```\n\nStep 2\n\nEach aggregator collects one project’s events and keeps a running count per event and tag, with a dashboard and event log if you want to look.\n\nMy shop\n\nDaily at 08:00 · Europe/Berlin\n\nStep 3\n\nHourly, daily, weekly or monthly, in your timezone. By email, to a Telegram chat, or both. No dashboard to remember to open. [See what a report looks like](#reports).\n\nThe report is the product. It is written to be read in thirty seconds, not explored.\n\nDaily report · My shop\n\nOrders up 12% on Monday, two thirds of them on the Pro plan. Signups are flat. Failed payments halved, down to 9.\n\n| Event | Count | Change | \n|---|---|---|\n| order_paid  | 184 | +20 (+12%) | \n| user_signup  | 212 | +3 (+1%) | \n| payment_failed | 9 | −10 (−53%) | \n| refund_requested | 8 | +1 (+14%) | \n\nTotal: 413 events\n\nDaily report — My shop\n\nIllustration with sample data.\n\nEvery report opens with a sentence or two on what moved and what didn’t, so you can read it on your phone and move on.\n\nA quiet Sunday or a public holiday is called what it is, and compared with the same weekday a week earlier rather than with Friday.\n\nEach event shows its count, the change since the last report, and a small trend line. Telegram gets a grid of trend charts.\n\nAdd tags like plan-pro or source-google to an event and the report splits the count by them.\n\nHourly, daily, weekly or monthly, sent at the local time you pick.\n\nSend each report to one or several channels, and test-send to check a channel before relying on it.\n\nNot page views or stack traces: those belong in your analytics and error tracker. Send the handful of business events you care about and let the report tell you when they move.\n\n`order_paid`` cart_abandoned``refund_requested`\n“Orders down 9% on last Saturday, all of it on mobile checkout. Refunds unchanged.”\n\n`user_signup`` trial_converted``subscription_cancelled`\n“Signups up 18% after the launch post; trial conversions steady at 31. Two cancellations, both on the Starter plan.”\n\n`lead_form_sent`` booking_made`\n“Client sites sent 42 leads this week, 11 of them from the new landing page.”\n\n`import_finished`` sync_failed``invoice_sent`\n“Nightly import finished as usual. Sync failures jumped to 14, all from the same supplier feed.”\n\nEvery plan includes every feature. Only the number of events differs. Try it with 100 events, on the house.\n\n100 events, one time\n\nEnough to see your first real reports\n\nEnough to wire up an aggregator and see a real report land in your inbox.\n\n10,000 events / month\n\nAbout 330 events a day\n\nFor a product in production that you actually watch.\n\n50,000 events / month\n\nAbout 1,650 events a day\n\nFor teams running several services at once.\n\nIf you stop opening dashboards, the report has to show up, on time, with the right numbers.\n\nA schedule is claimed before it is sent, so overlapping runs cannot send you the same report twice.\n\nIf a delivery fails, the period’s events are kept for the next report instead of being dropped.\n\nYou get one email when your event allowance is used up, rather than finding a gap in your reports later.\n\nSend a sample report to an inbox or chat to check it arrives before you depend on it.\n\nCreate an aggregator, send one request, pick a schedule. Short on time? We’ll wire it up for you.", "url": "https://wpnews.pro/news/show-hn-eventkiwi-scheduled-reports-for-your-app-s-events", "canonical_source": "https://eventkiwi.com/", "published_at": "2026-11-18 21:11:49+00:00", "updated_at": "2026-11-18 21:15:19.189081+00:00", "lang": "en", "topics": ["ai-products", "ai-tools", "developer-tools", "artificial-intelligence"], "entities": ["Eventkiwi"], "also_reported_by": [], "takeaway": "Eventkiwi accepts events via a single HTTP GET or POST with an aggregator ID and API key, where extra parameters become tags, and sends hourly-to-monthly reports by email or Telegram with an AI summary of the counted changes.", "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/show-hn-eventkiwi-scheduled-reports-for-your-app-s-events", "markdown": "https://wpnews.pro/news/show-hn-eventkiwi-scheduled-reports-for-your-app-s-events.md", "text": "https://wpnews.pro/news/show-hn-eventkiwi-scheduled-reports-for-your-app-s-events.txt", "jsonld": "https://wpnews.pro/news/show-hn-eventkiwi-scheduled-reports-for-your-app-s-events.jsonld"}}