The flow
Starts it 1Logic 5Service 6
The steps in the order they run, from what starts it.
- 1Daily Subscription CheckSchedule triggerStarts it
- 2Get Current DateDate TimeLogic
- 3Check Expiring SubscriptionsSupabaseService
- 4Check Subscription ActiveIfLogic
- 5Check Expiring Within 3 DaysIfLogic
- 6Send Renewal ReminderGmailService
- 7Send Payment Info to APIHttp RequestService
- 8Add hasId FlagCodeLogic
- 9Check Payment StatusIfLogic
- 10Update Subscription ActiveSupabaseService
- 11Send Payment Failure EmailGmailService
- 12Send Confirmation EmailGmailService
How it's built
- Starts on
- A clock
- Steps
- 12, with 3 branches
- Size
- Medium: a working afternoon
- Connects to
- Gmail, Supabase
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Gmail and Supabase accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
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?
Plan an afternoon. 12 steps is enough that you should read each one before running it.
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 12 steps before you point it at anything that matters.