Monitors Supabase subscriptions, fetches expiring rows, notifies via Telegram, and logs updates—triggered by webhook or schedule.
This AI agent monitors a Supabase subscriptions table for expirations and identifies items approaching renewal. It sends personalized renewal reminders to customers via Telegram based on a configurable reminder window. It flags notified subscriptions to prevent duplicates and returns a concise summary for auditing.
Connects data to messaging to deliver timely renewals.
Fetch subscriptions expiring on or before the target date from Supabase.
Filter for rows where notified is false.
Compose a personalized renewal message per customer.
Send the message via Telegram to the customer's chat_id.
Update the subscription row setting notified = true to prevent duplicates.
Respond to the webhook with a short summary of actions taken.
This AI agent automates the end-to-end renewal reminder workflow, reducing manual effort and human error. It connects your data in Supabase with Telegram to deliver timely renewals and maintain logs.
A simple three-step flow that non-technical users can follow.
An HTTP webhook or schedule triggers the AI agent and calculates targetDate = today + REMINDER_DAYS.
Query Supabase for subscriptions expiring on or before targetDate and where notified is false.
Send Telegram messages to each customer and update the notified flag to prevent duplicates.
One realistic scenario.
Scenario: 25 subscriptions expire in 3 days. A webhook triggers at 08:00 UTC, the AI agent queries Supabase, sends 25 personalized renewal reminders via Telegram, and updates all rows to notified = true. The webhook response returns counts of sent messages and a brief status snapshot for logging.
One supporting sentence.
Automates renewal reminders, reducing manual follow-ups.
Proactively reach customers before expiry to maximize renewals.
Provides a centralized, auditable reminder workflow.
Reduces time spent on chasing renewals.
Identifies at-risk accounts earlier to tailor engagement.
Easily integrates with Supabase data and Telegram bot credentials.
One supporting sentence with short explanation.
Reads subscriptions data, applies the notifiable filter, and updates the notified flag.
Sends personalized renewal reminders to each customer's chat via the Telegram bot.
One supporting sentence with short explanation.
One supporting sentence with short explanation.
If a Telegram API error occurs, the agent logs the failure and continues with other reminders. It can retry on a schedule or escalate to an admin if configured. The summary response always reflects which messages were delivered successfully and which failed. This ensures visibility without halting the entire batch execution.
Yes. Message templates can be customized via environment variables or a template store in Supabase. The AI agent fills in personalized fields like customer name and expiry date before sending. Changes apply without redeploying the core workflow, keeping communications consistent across customers.
The agent is triggered by an HTTP webhook or a scheduled cron-like event. This makes it easy to align reminders with your product cadence or external schedules. It also supports manual triggers for exceptional renewals. The trigger simply initiates the three-step flow described in the How it Works section.
Credentials are stored in secure, access-controlled AI agent credentials stores. The Supabase service role key is kept privately and accessed by the agent through authenticated calls. Telegram bot tokens are also stored securely and never exposed in logs. Always rotate keys and use environment-based configuration for different environments.
Each subscription has a notified flag that is set only after a successful dispatch. The agent processes each row once per run, and the flag prevents re-sending in subsequent cycles. If a run fails midway, retries are designed to skip already notified records and process only non-notified ones on the next run.
Yes. The setup supports multiple subscription sources and can be extended to different products or tenants by parameterizing the data source and message templates. You can reuse the same Telegram bot and Supabase structure, adjusting the target tables and environment variables as needed. This keeps management centralized while allowing product-specific customizations.
The webhook response includes counts of processed subscriptions and messages sent. Logs are generated at each step for auditing and debugging, with errors surfaced in the summary. You can also route the webhook response to downstream systems (e.g., a logging or alerting service) for centralized monitoring.
Monitors Supabase subscriptions, fetches expiring rows, notifies via Telegram, and logs updates—triggered by webhook or schedule.
