Back to Catalog

Transform your selfies into 3D figurines with Nano Banana AI

panyanyanypanyanyany
732 views
2/3/2026
Official Page

Transform Your Selfies into 3D Figurines with Nano Banana AI

Overview

This workflow utilizes the Defapi API with Google's Nano Banana AI model to transform your selfies into stunning 3D figurines, action figures, and collectible merchandise designs. Simply upload a selfie photo, provide a creative prompt describing your desired 3D figurine or action figure design, and watch as AI generates professional-quality product visualizations.

Input: Your selfie photo + creative prompt + API key
Output: AI-generated 3D figurine and action figure designs perfect for collectibles, merchandise, and product visualization

Users can interact through a simple form, providing a text prompt describing the desired creative scene, a product image URL, and their API key. The system automatically submits the request to the Defapi API, monitors the generation status in real time, and retrieves the final creative image output. This solution is ideal for marketers, product designers, e-commerce businesses, and content creators who want to quickly generate compelling product advertisements and creative visuals with minimal setup. Perfect for creating 3D figurines and collectible merchandise designs.

Prerequisites

  • A Defapi account and API key: Sign up at Defapi.org to obtain your API key.

  • An active n8n instance (cloud or self-hosted) with HTTP Request and form submission capabilities.

  • Basic knowledge of AI prompts for product creative generation to achieve optimal results, especially for 3D figurines and collectible designs.

    • Example prompt: Create a 1/7 scale commercialized 3D figurine of the characters in the picture, in a realistic style, in a real environment. The figurine is placed on a computer desk. The figurine has a round transparent acrylic base, with no text on the base. The content on the computer screen is the Zbrush modeling process of this figurine. Next to the computer screen is a packaging box with rounded corner design and a transparent front window, the figure inside is clearly visible.
  • A product image for creative generation.

  • Important Note: Avoid using dark photos as input, as the generated 3D figurine will also appear dark.

Setup Instructions

  1. Obtain API Key: Register at Defapi.org and generate your API key. Store it securely—do not share it publicly.
  2. Configure the Form: In the "Upload Image" form trigger node, ensure the following fields are set up: Image (file upload), API Key (text field), and Prompt (text field).
  3. Test the Workflow:
    • Click "Execute Workflow" in n8n.
    • Access the generated form URL, upload your product image, enter your prompt, and provide your API key.
    • The workflow will process the image through the "Convert to JSON" node, then send the request to the Defapi API.
    • The system will wait 10 seconds and then poll the API status until the image generation is complete.
  4. Handle Outputs: The final "Format and Display Image Results" node formats and displays the generated creative image URL for download or embedding.

Workflow Structure

The workflow consists of the following nodes:

  1. Upload Image (Form Trigger) - Collects user input: image file, API key, and prompt
  2. Convert to JSON (Code Node) - Converts uploaded image to base64 and formats data
  3. Send Image Generation Request to Defapi.org API (HTTP Request) - Submits generation request
  4. Wait for Image Processing Completion (Wait Node) - Waits 10 seconds before checking status
  5. Obtain the generated status (HTTP Request) - Polls API for completion status
  6. Check if Image Generation is Complete (IF Node) - Checks if status equals 'success'
  7. Format and Display Image Results (Set Node) - Formats final image URL output

Technical Details

  • API Endpoint: https://api.defapi.org/api/image/gen (POST request)
  • Model Used: google/nano-banana (Nano Banana AI)
  • Status Check Endpoint: https://api.defapi.org/api/task/query (GET request)
  • Wait Time: 10 seconds between status checks
  • Image Processing: Uploaded images are converted to base64 format for API submission
  • Authentication: Bearer token authentication using the provided API key
  • Specialized For: 3D figurines, collectible merchandise, and product visualization

Customization Tips

  • Enhance Prompts: Include specifics like scene setting, lighting, style (e.g., realistic, artistic, cinematic), product placement, and visual elements to improve AI creative image quality. For 3D figurines, specify scale, materials, and display context.
  • Form Fields: The form accepts image files (image/*), API key (text), and prompt (text) as required fields.
  • Error Handling: The workflow includes conditional logic to check for successful completion before displaying results.
  • Best Practices for Nano Banana AI: Use detailed descriptions for figurine designs, specify lighting conditions, and include environmental context for realistic 3D figurine generation.
  • Photo Quality Tips: Use well-lit photos for best results. Avoid dark images as they will make the generated 3D figurine appear dark too.

8571-transform-your-selfies-into-3d-figurines-with-nano-banana-ai

This n8n workflow is designed to process form submissions, allowing for conditional logic and data manipulation. While the directory name suggests a specific use case related to AI and 3D figurines, the provided JSON defines a generic workflow for handling form data, applying conditional logic, and performing data transformations.

Description

This workflow automates the process of receiving data via an n8n form, applying a conditional check, and then either processing the data further or waiting based on the condition. It includes steps for modifying the incoming data and executing custom JavaScript code.

What it does

  1. Listens for Form Submissions: The workflow is triggered whenever a user submits data through an n8n form.
  2. Edits Fields (Set): Immediately after submission, the incoming data is passed to a "Set" node, which is configured to edit or add fields to the data.
  3. Applies Conditional Logic (If): The modified data then goes through an "If" node, which evaluates a condition. The workflow branches based on whether this condition is true or false.
  4. Executes Custom Code (Code): If the condition in the "If" node evaluates to true, the data is passed to a "Code" node, allowing for custom JavaScript logic to be applied.
  5. Performs HTTP Request: If the condition in the "If" node evaluates to true, the workflow also makes an HTTP request.
  6. Introduces a Delay (Wait): If the condition in the "If" node evaluates to false, the workflow pauses for a specified duration using a "Wait" node.

Prerequisites/Requirements

  • n8n Instance: A running instance of n8n to import and execute the workflow.
  • n8n Form: The workflow relies on an n8n Form Trigger, which will need to be configured with the specific fields you expect to receive.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure the n8n Form Trigger:
    • Open the "On form submission" node.
    • Define the form fields that users will submit.
    • Save the form. n8n will provide a URL for your form.
  3. Configure the "Edit Fields (Set)" Node:
    • Open the "Edit Fields" node.
    • Adjust the fields to be set or modified based on your requirements.
  4. Configure the "If" Node:
    • Open the "If" node.
    • Define the condition(s) that will determine the flow of your data.
  5. Configure the "Code" Node (if used):
    • Open the "Code" node.
    • Write your custom JavaScript logic to process the data when the "If" condition is true.
  6. Configure the "HTTP Request" Node (if used):
    • Open the "HTTP Request" node.
    • Set up the URL, method, headers, and body for the API call you want to make when the "If" condition is true.
  7. Configure the "Wait" Node (if used):
    • Open the "Wait" node.
    • Specify the duration for which the workflow should pause when the "If" condition is false.
  8. Activate the Workflow: Once configured, activate the workflow. It will then be ready to process form submissions.
  9. Submit Data: Use the URL provided by the "On form submission" node to submit data and test the workflow.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942