Block 1 - Schedule Trigger
- Type / Role
- n8n-nodes-base.scheduleTrigger - scheduleTrigger
- Config choices
- Version 1.3
Supabase Free Plan Keep Alive Prevents Supabase from pausing an inactive project by writing randomised pings to a database table on a recurring schedule. Overview The workflow runs every 4 days and...
n8n-nodes-base.scheduletrigger, n8n-nodes-base.supabase, n8n-nodes-base.manualtrigger, n8n-nodes-base.code, n8n-nodes-base.splitinbatches, n8n-nodes-base.wait, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by LukaszB.
Original n8n.io sourcePrevents Supabase from pausing an inactive project by writing randomised pings to a database table on a recurring schedule.
The workflow runs every 4 days and performs 25 sequential database writes to the ping table in Supabase. Each write is separated by a random delay between 20 and 60 seconds to simulate organic activity rather than a mechanical burst.
Schedule Trigger Fires every 4 days automatically. A manual trigger is also included for testing.
Code – Generate Items Creates an array of 25 identical items to drive the loop.
Loop Over Items Processes one item per iteration until all 25 are complete.
Code – Random Wait Assigns a random integer between 20 and 60 seconds to each item before the wait step.
Wait Pauses execution for the duration assigned in the previous step.
Create a Row
Inserts a row into the ping table in Supabase with the current timestamp as created_at.
ping table in your Supabase project with a created_at column (timestamptz).This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Keep Supabase free plan projects alive with scheduled database pings |
|---|---|
| Complexity | intermediate |
| Nodes | 11 |
| Categories | DevOps |
| Author | LukaszB |
| Published | 05 Apr 2026 |
Use the JSON export at /data/workflows/14745/14745.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Supabase Free Plan Keep Alive Prevents Supabase from pausing an inactive project by writing randomised pings to a database table on a recurring schedule. Overview The workflow runs every 4 days and...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps use case.