Getting started
Rules Engine Widgets
Supabase Storage
4 min
purpose to upload, download, list, or delete files from supabase storage directly within your workflow this node enables seamless integration between your automation flows and supabase’s scalable, secure file storage system problem statement managing files across apis and workflows can be complicated — especially when handling uploads, retrieval, or deletions on external storage platforms the supabase storage node simplifies this process by providing built in file operations (upload, download, list, delete) inside your automation — without the need for manual api calls requirements must have an active supabase project must include your supabase url and api key must specify a bucket name (where your files are stored) should support standard file operations ( upload , download , delete , list ) must handle variable based input for dynamic workflows use cases upload user generated files (images, pdfs, audio, etc ) to supabase fetch or download stored files for preview or further processing automatically delete files when specific conditions are met generate public urls for uploaded files use supabase storage as a backend for ai , documentation , or analytics workflows outcome uploads, retrieves, or manages files in supabase storage — returning file urls or metadata that can be used in subsequent workflow nodes how to use 1\ add the supabase storage node drag and drop the supabase storage node into your workflow canvas this node will handle all file interactions with your connected supabase project 2\ add credentials click add credentials in the node it will redirect you to the credentials page click add credentials , then click supabase and enter your supabase url and api key click save once done the saved credentials will now appear under the supabase node and can be reused in future workflows 3\ select operation choose the file action you want the node to perform upload file download file list files delete file get public url 4\ configure file details based on your selected operation, fill in the required fields such as bucket name — the target bucket where files are stored file path — the location or name of the file within the bucket file variable — a variable reference (e g , {{uploadedfile}}) for dynamic file input 5\ output variable define a variable name to store the operation result this will hold information such as file metadata, url, or confirmation messages node output output variable supabaseresult