n8n integration

Analyze images with the Luntrex community node for n8n.

Install the community node, add your Luntrex API key, and send either image URLs or binary file inputs to vision models such as gemini-2.5-flash-image. Perfect for product analysis, content tagging, and visual QA inside workflows.

Configure the Image Analyzer node

Follow these steps to install @luntrex/n8n-nodes-luntrex-image-analyzer, add credentials, and set the node parameters shown in the screenshots.

Community node ID
@luntrex/n8n-nodes-luntrex-image-analyzer
View on npm

Integration steps

Install the community node Go to Settings → Community Nodes, paste @luntrex/n8n-nodes-luntrex-image-analyzer into the node name box, and click Install.
Create credentials In credentials, set Base URL to https://luntrex.com and paste your Luntrex API key. Save and test the connection.
Add the node to a workflow Drag Analyze Image onto the canvas. Select your credential to unlock model choices.
Set parameters Operation: Analyze Image. Choose a model (e.g., gemini-2.5-flash-image). Pick an image source: Image Link or Binary File. For binary, set the Input Binary Field (default data). Add your prompt.
Execute or wire forward Click Execute step to preview the analysis output or connect the node into your workflow.
Tip: Store the API key in n8n credentials instead of the node body so you can rotate keys without editing workflows.

Parameter reference

  • Credential to connect with Choose the saved Luntrex API key credential.
  • Operation Set to Analyze Image.
  • Model Select a vision-capable model (e.g., gemini-2.5-flash-image).
  • Image Source Choose Image Link (URL) or Binary File.
  • Input Binary Field Required when Binary File is selected. Default is data; match it to the incoming binary field name.
  • Prompt Describe what to extract/understand (e.g., “Summarize this product photo with title, category, and key attributes”).

Supported image sources

  • Image Link Provide a reachable HTTPS URL to the image.
  • Binary File Pass image bytes from an upstream node and set the binary field name (default data).

Execution tips

  • Keep prompts concise but specific about the desired output (e.g., “List product title, color, material, defects”).
  • For binary input, confirm the field name matches your upstream node.
  • Use URLs that are publicly reachable; private links may fail.

Troubleshooting

  • Unauthorized Re-check the API key in credentials and ensure it’s active.
  • Model not shown Select credentials first; the node loads models after authentication.
  • Image errors For binary, ensure the field name matches. For links, confirm the URL is reachable and uses HTTPS.
Back to top