Slack, Discord and Telegram alerts for your Lovable app. One prompt.

Add EventSend notifications to this app so I hear about what matters while it runs.

1. First, study what this app actually does. Read the codebase and list the moments
   worth knowing about in THIS product, not a generic checklist. Signups and payments
   are the baseline: a marketplace also cares about listings and orders, an AI app
   about generations and credits, a scheduler about jobs that ran or did not.
   Write that list down before you instrument anything.

2. Send events by POSTing JSON to https://eventsend.io/api/events with the header
   Authorization: Bearer <EVENTSEND_TOKEN> (read from an environment variable;
   never hardcode it, never ship it to the browser).
   Body: { "event": "<kebab-case name, 4-64 chars, e.g. user-signup>",
           "message": "<human-readable text, 4-500 chars>",
           "level": "<default | success | warning | error | critical>",
           "icon": "<one emoji>",
           "payload": { <ids, amounts, plan names; under 4 KB as JSON> },
           "unique_key": "<optional idempotency key, 4-128 chars>" }
   A 202 response means the event is queued. Anything else means it was not.

3. Create one small server-side helper (for example lib/eventsend.ts) wrapping this
   call. It must never throw, never block the response (fire-and-forget), and no-op
   when EVENTSEND_TOKEN is unset.

4. Instrument the moments from step 1, SERVER-SIDE ONLY:
   - Product moments, level "success" or "default": the app's own features being
     used, named in the product's own language ("order-placed", "export-finished").
   - Signups as "user-signup" (success). Payments and subscriptions as
     "payment-received", "subscription-created" (success) and
     "subscription-canceled", "payment-failed" (warning or error).
   - Failures, which matter most, level "error" or "critical": every catch block in
     API routes and server actions, webhook handlers that fail or fail signature
     verification, declined payments, cron jobs that throw or do not complete, and
     failed calls to external APIs.

5. Put a fitting emoji in "icon": 💰 revenue, 🎉 signup, ✅ success, ⚠️ warning, ❌ failure.

6. Put the user's email or id, amounts, plan names and object ids in "payload".
   Never log secrets, passwords, tokens or card numbers.

7. Set "unique_key" wherever the caller might retry: a webhook handler (the provider's
   event id), a CI job (the commit SHA), a queue consumer (the job id).

8. Where the app knows which customer a moment is about, set "user_id" to that
   customer's stable id (your account id, or the Stripe customer id; never the email),
   the same value from every place that reports on them. If the app knows when the
   thing actually happened, set "occurred_at" to that ISO-8601 timestamp; otherwise
   leave it out.

When done, list every file you changed and every event now tracked, with its name and
level, so I can create topics for them in EventSend.

Note: This is a Lovable project. Put the calls in the backend functions, never in React components or anything that runs in the browser, and store EVENTSEND_TOKEN as a backend secret rather than in a file.