The flow
Starts it 3Logic 9Service 10
The steps in the order they run, from what starts it.
- 1Stripe TriggerStripe triggerStarts it
- 2Recon ScheduleSchedule triggerStarts it
- 3Telegram TriggerTelegram triggerStarts it
- 4Paywall SettingsSetLogic
- 5Recon SettingsSetLogic
- 6Normalize Telegram MessageSetLogic
- 7Skip If Already ProcessedData TableService
- 8Read All EntitlementsData TableService
- 9Bot SettingsSetLogic
- 10Record Event As ProcessedData TableService
- 11Fetch Live Subscription StatusHttp RequestService
- 12Look Up EntitlementData TableService
- 13Map Event To EntitlementCodeLogic
- 14Detect DriftCodeLogic
- 15Is Entitled?IfLogic
- 16Upsert EntitlementData TableService
- 17Only Drifted RowsFilterLogic
- 18Send Protected ContentTelegramService
- 19Send Subscribe PromptTelegramService
- 20Apply CorrectionData TableService
- 21Summarize CorrectionsCodeLogic
- 22Report Drift To SlackSlackService
How it's built
- Starts on
- An incoming Telegram message
- Steps
- 22, with 1 branch
- Size
- Large: read it before trusting it with anything live
- Connects to
- Slack, Telegram, n8n data table
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Slack and Telegram accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an incoming Telegram message.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Take your time. At 22 steps it is large: read it before trusting it with anything live.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 22 steps before you point it at anything that matters.