Auto Generate Descriptive Node Names with AI for Workflow Readability
⚡Auto Rename n8n Workflow Nodes with AI✨ This workflow uses AI to automatically generate clear and descriptive names for every node in your n8n workflows. It analyzes each node's type, parameters, and connections to create meaningful names, making your workflows instantly readable. Who is it for? This workflow is for n8n users who manage complex workflows with dozens of nodes. If you've ever: Built workflows full of generic names like HTTP Request 2 or Edit Fields 1 Struggled to understand your own work after a few weeks Copied workflows from others with unclear node names Spent hours manually renaming nodes one by one ...then this workflow will save you significant time and effort. Requirements n8n API Credentials: Must be configured to allow listing and updating workflows AI Provider Credentials: An API key for your preferred AI provider (OpenRouter is used currently) How it works Trigger: Launch via form (select from dropdown) or manual trigger (quick testing with pre-selected workflow) Fetch: Retrieve the target workflow's JSON and extract nodes and connections Generate: Send the workflow JSON to the AI, which creates a unique, descriptive name for every node Validate: Verify the AI mapping covers all original node names Apply: If valid, update all node names, parameter references, and connections throughout the workflow Save: Save/Update the workflow with renamed nodes and provide links to both new and previous versions If validation fails (e.g., AI missed nodes), the workflow stops with an error. You can modify the error handling to retry or loop back to the AI node. Setup Connect n8n API credentials Open any n8n node in the workflow and make sure your n8n API credentials is connected Configure AI provider credentials Open the "OpenRouter" node (or replace with your preferred AI) Add your API credentials Adjust the model if needed (current: openai/gpt-5.1-codex-mini) Test the workflow Use Manual Trigger for quick testing with a pre-selected workflow Use Form Trigger for a user-friendly interface with workflow selection Important notice If you're renaming a currently opened workflow, you must reload the page after execution to see the latest version, n8n doesn't automatically refresh the canvas when workflow versions are updated via API. Need help? If you're facing any issues using this workflow, join the community discussion on the n8n forum.
By AnanGenerate biblical character vlogs with GPT-4o and Veo3 AI video generator
🧠 How It Works This intelligent workflow turns ancient stories and legendary characters into modern-style vlog ideas — then automatically builds cinematic prompts ready to generate short videos using Veo3. Think: “What if biblical figures had GoPros?” — funny, emotional, and visually stunning AI-made videos. --- 🔄 Workflow Steps ✨ 1. Concept Generator (AI Node 1) The first AI agent creates a video concept inspired by a biblical or mythological theme. It structures output as JSON with: 🎬 caption – Short, emotional or humorous line with emojis & hashtags 💭 concept – A short summary of the story or moment captured on camera 🌄 setting – Visual and mood details (lighting, style, colors) 📋 status – Stage label like “draft” or “to produce” Example Output: json { "caption": "POV: Moses trying to record a vlog mid–Red Sea split 🌊📹 faithvibes holyshorts", "concept": "Moses looks straight into the camera, trying to act calm while walls of water rise dramatically beside him.", "setting": "Vast sea corridor glowing in blue light, reflections dancing on wet sand, robes fluttering in the wind.", "status": "to produce" } --- 🎬 2. Cinematic Prompt Builder (AI Node 2) This agent converts the concept and setting into a Veo3-ready cinematic prompt that guides realistic video generation. Each output includes: Scene layout & description 🌅 Character framing & expression 🎭 Camera movement (pan, orbit, dolly-in, etc.) 🎥 Lighting style & atmosphere 💡 Textural realism (dust, wind, shadows, fabrics) Example Output: > A robed man stands between two towering walls of water, facing the camera as waves shimmer in the light. The handheld camera slowly pushes forward, capturing ripples and wind-blown fabric. His tone is confident yet tense. The atmosphere feels surreal — reflections glisten and mist drifts through golden rays. --- ☁️ 3. Send to Veo3 API The cinematic description is sent directly to the Veo3 video generation API to create the visual clip. POST Request https://queue.fal.run/fal-ai/veo3 Header → Authorization: Key YOURAPIKEY Body → { "prompt": "{{ $json.output }}" } The API responds with a request_id to track progress. --- ⏳ 4. Track Video Progress Monitor generation status and retrieve your final clip details. GET Request https://queue.fal.run/fal-ai/veo3/requests/{{ $json.request_id }} Header → Authorization: Key YOURAPIKEY When complete, the Veo3 model delivers your AI-generated short film. --- ⚙️ Setup Guide Connect APIs • Create a Veo3 (fal.run) account • Copy your API key → Add it under Header Auth: Authorization: Key YOUR_API_KEY Customize Prompts • Change the core question in Node 1 to explore other themes — e.g., “Greek myths,” “ancient warriors,” or “historic leaders.” • Refine the camera and lighting tone in Node 2 for different cinematic vibes (gritty, vintage, surreal). Run & Validate • Trigger manually to test flow • Check JSON output → must include caption, concept, setting, status • Ensure Veo3 receives your cinematic prompt correctly Automate & Expand • Add a Scheduler to generate new ideas daily or weekly • Send results to Google Sheets, Notion, or Discord for creative collaboration --- 🚀 Ideal For • 🎬 Creators & Filmmakers → Quickly generate cinematic ideas & AI-shot scripts • 🙏 Faith-Based Artists → Reimagine ancient lessons with modern storytelling • 💡 Creative Studios → Automate short video ideation for campaigns • 🧠 Educators & Animators → Visualize history or mythology through creative AI prompts ---
By NiteshAutomate JotForm submissions via HTTP without API keys
This guide explains how to send form data from n8n to a JotForm form submission endpoint using the HTTP Request node. It avoids the need for API keys and works with standard multipart/form-data. --- 📌 Overview With this workflow, you can automatically submit data from any source (Google Sheets, databases, webhooks, etc.) directly into JotForm. ✅ Useful for: Pushing information into a form without manual entry. Avoiding API authentication. Syncing external data into JotForm. --- 🛠 Requirements A JotForm account. An existing JotForm form. Access to the form’s direct link. Basic understanding of JotForm’s field naming convention. --- ⚙️ Setup Instructions Get the JotForm Submission URL Open your form in JotForm. Go to Publish → Quick Share → Copy Link. Example form URL: sample form Convert it into a submission endpoint by replacing form with submit: Example: submit url --- Identify Field Names Each JotForm field has a unique identifier like q3name[first] or q4email. Steps to find them: Right-click a field in your published form → choose Inspect. Locate the name attribute in the <input> tag. Copy those values into the HTTP Request node in n8n. Example mappings: First Name → q3_name[first] Last Name → q3_name[last] Email → q4_email --- Configure HTTP Request Node in n8n Method: POST URL: Your JotForm submission URL (from Step 1). Content Type: multipart/form-data Body Parameters: Add field names and values. Example Body Parameters: json { "q3_name[first]": "John", "q3_name[last]": "Doe", "q4_email": "john.doe@example.com" } --- Test the Workflow Trigger the workflow (manually or with a trigger node). Submit test data. Check JotForm → Submissions to confirm the entry appears. --- 🚀 Use Cases Automating lead capture from CRMs or websites into JotForm. Syncing data from Google Sheets, Airtable, or databases. Eliminating manual data entry when collecting responses. --- 🎛 Customization Tips Replace placeholder values (John, Doe, john.doe@example.com) with dynamic values. Add more fields by following the same naming convention. Use n8n expressions ({{$json.fieldName}}) to pass values dynamically.
By moosa