Restore approved Supabase row updates with Rewind APIs

by Kanishq Sharma · 0 views · created 2026-10-05 · Document Extraction

What this workflow does

This workflow has 12 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). It uses only n8n's built-in nodes.

How it runs

Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).

1. Configure endpoints (Edit Fields (Set)): sets 3 fields: rewindBaseUrl, supabaseBaseUrl, connection
2. Validate endpoints (Code): runs custom JavaScript code
3. Claim approved job (HTTP Request): calls an HTTP API (POST)
4. Validate job (Code): runs custom JavaScript code
5. Read current resource (HTTP Request): calls an HTTP API (POST)
6. Check current version (Code): runs custom JavaScript code
7. Version still matches (If): checks a condition and branches into true / false
8. Conditional restore (HTTP Request): calls an HTTP API (POST)
9. Report outcome (HTTP Request): calls an HTTP API (POST)
10. Classify write result (Code): runs custom JavaScript code

Before you upgrade to n8n 3.0

Nodes used (6)

• Manual Triggern8n-nodes-base.manualTrigger
• Schedule Triggern8n-nodes-base.scheduleTrigger
• Edit Fields (Set)n8n-nodes-base.set
• HTTP Requestn8n-nodes-base.httpRequest
• Coden8n-nodes-base.code
• Ifn8n-nodes-base.if

From the author

Quick overview Run an approved recovery job for a Supabase row update captured with Rewind. Check for later edits, conditionally restore the saved fields, and report the outcome. Capture and human approval happen separately; verify the restored row directly…

View the original on n8n.io → Check your own copy