Reminders

Reminders are configured in App settings → Reminders. They are off by default. Turn on Send through Telegram to enable them.

BotFather, chat ID, test-message, and deployment details are covered in Telegram setup below.

Reminder events

Each event can be enabled independently. A reminder is enqueued only when its event is enabled for the current user.

Manual and review publishing

The Ready to post Telegram message contains Yes, I posted it for slideshow and generated-video outputs. Selecting it:

1. identifies the exact reminder job and its owning user;
2. marks that generation Published and records manuallyPublishedAt;
3. removes the action button so its state is clear;
4. leaves the account, TikTok URL, provider-native ID, and provider publication time empty until real evidence is available.

The action is idempotent, so a repeated callback does not duplicate anything. You can later open the generation and use Link published post to attach its TikTok URL. The link workflow records the actual provider evidence and corrects the publication timestamp if necessary. See Manual publication and linking.

Automatic publishing

Automatic PostFast publishing never waits for a Telegram response. Its Scheduled to post reminder is notification-only, and provider state remains the source of truth for scheduled and published timestamps. No confirmation button is shown.

Telegram setup

1. Create a Telegram bot with BotFather.
2. Enter its bot token and destination chat/channel ID in App settings.
3. Set BASE_URL to the public HTTPS origin of the LumenClip app.
4. Set a strong TELEGRAM_WEBHOOK_SECRET on the app.
5. Turn on Telegram, choose the events, save, and send a test reminder.

Deployment-level TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID values remain fallbacks for existing installations. A saved workspace token is never returned to the browser after storage.

Completed slideshow messages include two signed public delivery links: Preview generation opens a login-free preview where the recipient can copy the title or combined description and hashtags, while Download slides (.zip) points directly to a downloadable archive of every rendered slide. Both links are scoped to one output, expire after one year, and use SLIDESHOW_SHARE_SECRET (falling back to the Railway server key if a dedicated share secret is not configured).

Saving Telegram settings registers <BASE_URL>/api/telegram/webhook with Telegram when the public URL and webhook secret are available. A localhost URL can send messages, but Telegram cannot deliver button callbacks to it unless a public HTTPS tunnel is used.

The webhook route is public only at the session layer. Every callback must contain Telegram's configured secret header, and the referenced job must be an actionable Ready to post reminder before any generation can be changed.

Implementation reference

• Settings UI: components/realfarm/user-settings-modal.tsx
• Settings and Telegram client: lib/reminder-settings.ts
• Reminder queueing: lib/reminders.ts
• Worker delivery: railway/functions/job-worker/src/main.js
• Confirmation callback: app/api/telegram/webhook/route.ts
• Posted-state update: lib/reminder-actions.ts