In plain terms: this keeps your systems in sync. It moves and updates information across Supabase, PostgreSQL on a set schedule (e.g. daily), so you never copy-paste between tools again.
16
Nodes
3
Integrations
15
Connections
Schedule, Sub-workflow
Trigger
🚀 Deploy this workflow
Deploy this automation in minutes
Log in and we'll walk you through every key step by step, then deploy it for you.
The real node graph exported from n8n — triggers (green), AI nodes (violet), services and logic — laid out as they run.
⚙️ How it works
Schedule Trigger· scheduleTrigger
When Executed by Another Workflow· executeWorkflowTrigger
Get Active Keywords· supabase
Normalize Competitor Input· set
YouTube API Search· httpRequest
Get Video Statistics· httpRequest
Split Video Items· splitOut
Calculate Viral Score· code
Normalize Keyword Input· set
Is Viral?· if
Update Keyword Timestamp· postgres
kw || comp_id· if
Store in yt_videos· postgres
Store in yt_videos comp_ID· postgres
💼 Business analysis
🎯
Business use case
A data pipeline that moves, syncs and transforms records across Supabase, HTTP / REST API, PostgreSQL — the plumbing that keeps systems of record consistent without manual exports.
📈
Market need
Disconnected tools create silos and manual re-entry. Reliable sync pipelines are foundational infrastructure every scaling company needs.
💰
Market value
Integration/ETL work bills $100–$200/hr bespoke; a reliable pipeline template saves days of engineering per deployment.