Supabase Subscription Renewal Automation (Gmail + Payment API) for n8n

Automate Supabase subscription renewals—daily reminders + payment API updates via n8n

This n8n workflow checks your Supabase subscriptions every day, sends renewal reminder and confirmation (or failure) emails through Gmail, and posts payment identifiers to an external HTTP API to update renewal status automatically.

What this workflow does

• Runs daily at 09:00 using an n8n schedule trigger.
• Retrieves the current date/time and fetches all records from your Supabase subscriptions table.
• Filters to subscriptions where status = active and end_date falls between now and the next three days.
• Sends a renewal reminder email to each subscription owner using Gmail.
• Posts subscription and payment identifiers to an external HTTP endpoint (payment processing step) and treats the response as successful when an id is present.
• On success: updates the Supabase subscription record with active status, a new start_date/end_date, and last_payment_date, then emails a renewal confirmation via Gmail.
• On failure: emails the customer a payment failure notice via Gmail.

Use cases

• SaaS operators who want hands-off subscription renewal communication for expiring plans.
• Automation engineers needing a reliable Supabase + Gmail + payment API renewal pipeline inside n8n.
• Teams managing renewal windows and wanting both reminders and payment outcome emails sent automatically.

Technical details

• Supabase integration to read/update the subscriptions table.
• Gmail node for renewal reminder, confirmation, and payment failure emails.
• HTTP Request to send identifiers to an external payment processing endpoint and evaluate success by presence of an id.
• Date/Time logic to compute the renewal window (next three days).
• Control flow using if and code (plus a sticky note for workflow context).