Jan Willem Altink

Workflows

Workflows by Jan Willem Altink

Sort by:

Upload & categorize files with Supabase Storage and secure URL generation

# Supabase Storage File Upload Workflow *works with selfhosted Supabase* ## ℹ️ How it works • Accepts file data (MIME type, filename, base64 content) from other workflows • Automatically routes files to appropriate storage buckets based on file type (images, audio, video, documents) • Uploads files to Supabase Storage using the REST API • Generates secure signed URLs for file access with 30-day expiration • Returns structured success/error responses for downstream processing ## 🏗️ Set up steps • Configure Supabase API credentials in n8n • Create storage buckets in your Supabase project (image-files, audio-files, video-files, document-files) (or choose your own structuring system) • Replace url paths with your own • Test the workflow using the included form trigger • Remove test form and integrate with your main workflows **📚 Reference:** [Supabase Storage Documentation](https://supabase.com/docs/guides/storage)

n8n workflow manager API

This workflow provides a secure API endpoint to remotely trigger other n8n workflows with custom data and to retrieve information about your existing workflows. It's perfect for users who want to integrate n8n into external systems or programmatically manage their automations. _example usage: I use this workflow in a Raycast extension i have build, to execute n8n workflows from within Raycast: [see Github](https://github.com/jwa91/n8n-manager-raycast)_ ++**How it works**++ 1. **Receives API Calls:** A webhook listens for incoming HTTP requests (e.g., POST to trigger, GET to retrieve info). 2. **Triggers Workflows:** If the request is to trigger a workflow, it dynamically identifies the target workflow ID (from query parameters) and any input data (from the request body), then executes that workflow. This means you can control any of your workflows without modifying this manager template. 3. **Retrieves Workflow Info:** Similarly, if the request is to get information, it dynamically uses query parameters (`workflowId`, `mode`, `includedWorkflows`) to fetch details about one or more n8n workflows (e.g., specific, all, active, inactive; full or summarized data). 4. **Responds:** Sends back a JSON response indicating success/failure or the requested workflow data. ++**Set it up**++ 1. **Configure Webhook Security:** Set up "Header Auth" credentials for the main Webhook node. This is the API key your external services will use. 2. **Add n8n API Credentials:** For the nodes that fetch workflow information (like "Get specific workflowid", "get all active workflows", etc.), connect your n8n API credentials. This allows the workflow to query your n8n instance. 3. **Note Your Webhook URL:** Once active, n8n provides a production URL for the webhook (path: `workflow-manager`). Use this URL to make API calls. 4. **Understand API Parameters:** * To trigger: Use `?workflowId=[ID_OF_WORKFLOW_TO_RUN]` and send JSON data in the request body. * To get info: Use parameters like `?workflowId=[ID]`, `?includedWorkflows=[all/active/inactive]`, and `?mode=[full/summary]`.