npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

n8n-nodes-fluentc

v2.0.2

Published

N8N nodes for FluentC AI Translation API

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

fluentcfluentc

Keywords

n8n-community-node-packagetranslationaifluentc

Readme

FluentC N8N Plugin

This N8N community plugin provides integration with the FluentC AI Translation API, enabling you to translate text and HTML content and detect languages within your N8N workflows.

Features

  • Translation: Support for both real-time and batch translation modes
  • Language Detection: Detect the language of input content
  • Language Retrieval: Fetch lists of supported and source languages
  • Dynamic Language Selection: Dropdown menus populated with your API key's enabled languages
  • Format Support: Handle text, HTML, and JSON content
  • Automatic Polling: Batch jobs are automatically polled until completion
  • Comprehensive Output: Returns all metadata including token counts, detected languages, and model information
  • Error Handling: Graceful error handling with continue-on-fail support
  • Language Management: Direct link to manage enabled languages on your account

Installation

The installation method depends on your n8n setup. Choose the appropriate method below:

Method 1: n8n GUI Installation (Recommended for self-hosted n8n)

This is the easiest method for self-hosted n8n instances:

  1. Open n8n Settings: In your n8n instance, go to Settings > Community Nodes
  2. Install Node: Click Install
  3. Enter Package Name: Enter n8n-nodes-fluentc in the "Enter npm package name" field
  4. Accept Risk: Check "I understand the risks of installing unverified code from a public source"
  5. Install: Click Install
  6. Restart: The nodes will be available immediately after installation

Method 2: Verified Community Nodes (for n8n Cloud and recent versions)

If this package gets verified by n8n (future goal):

  1. Open Nodes Panel: Go to the Canvas and open the nodes panel (click '+' or press Tab)
  2. Search: Search for "FluentC"
  3. Install from Community: Look for the "More from the community" section
  4. Install: Click on the FluentC node and select Install

Method 3: Manual Installation (for Docker/advanced setups)

For Docker containers, queue mode, or when GUI installation isn't available:

For Docker Containers:

  1. Access Docker Shell:

    docker exec -it [your-n8n-container-name] sh

  2. Create nodes directory (if it doesn't exist):

    mkdir -p ~/.n8n/nodes
cd ~/.n8n/nodes

  3. Install the package:

    npm install n8n-nodes-fluentc

  4. Restart n8n container

For npm-based installations:

  1. Navigate to n8n nodes directory:

    cd ~/.n8n/nodes

    (Create the directory if it doesn't exist: mkdir -p ~/.n8n/nodes)

  2. Install the package:

    npm install n8n-nodes-fluentc

  3. Restart n8n

Method 4: Custom Docker Build

For permanent installation in a custom Docker image:

FROM n8nio/n8n:latest
RUN cd ~/.n8n/ && mkdir -p nodes && cd nodes && npm install n8n-nodes-fluentc

Verification

After installation, verify the node is available:

  1. Create a new workflow
  2. Click the '+' button to add a node
  3. Search for "FluentC" in the node search
  4. You should see the FluentC node (with package icon)

Setup

1. Create FluentC API Credentials

  1. In N8N, go to Credentials > New
  2. Search for "FluentC API" and select it
  3. Enter your FluentC API key (obtained from the FluentC sales website)
  4. Test and save the credential

2. Using the Node

The FluentC node uses a Resource and Operation pattern. Select the resource for the task you want to perform, then choose the operation.

Translation > Translate

Translate text, HTML, or JSON content with support for both real-time and batch modes.

Parameters:

  • Mode: Choose between "Real-Time" (synchronous) or "Batch" (asynchronous)
  • Input: Text, HTML, or JSON content to translate (max 100,000 bytes)
  • Input Format: Select "Text", "HTML", or "JSON"
  • Target Language: Dropdown populated with your enabled target languages
  • Source Language: Dropdown with your enabled source languages (optional, includes "Auto-Detect")
  • Max Polling Attempts: (Batch mode only) Maximum polling attempts for batch jobs (default: 60)

Language Management: The language dropdowns are dynamically populated based on your API key's enabled languages. If you need additional languages, you'll see a link to visit www.fluentc.io to manage your language access.

Output: The node returns all available data including:

  • translation: The translated content
  • token_count: Number of tokens used
  • source_language_detected: Detected source language
  • model_used: AI model used for translation
  • metadata: Additional metadata
  • mode: Translation mode used
  • input_format: Input format processed
  • target_language: Target language

Language Detection > Detect

Detect the language of input content.

Parameters:

  • Input: Text or HTML content to analyze
  • Input Format: Select "Text" or "HTML"

Output:

  • detected_language: Two-letter language code of detected language
  • confidence: Confidence score (0-1) for the detection
  • input_format: Input format processed
  • input_length: Length of analyzed content

Language > Get Many

Fetch the lists of supported and source languages from your FluentC account.

Parameters: This operation has no additional parameters. It only requires a configured FluentC API credential.

Output:

  • supported_languages: An array of objects, each with code and name of a language available for translation as a target.
  • source_languages: An array of objects, each with code and name of a language available as a source for translation.

Usage Examples

Basic Translation Workflow

  1. Add a FluentC node to your workflow
  2. Select Resource: Translation, Operation: Translate
  3. Configure it with:
    • Mode: "Real-Time"
    • Input: "Hello, how are you today?"
    • Input Format: "Text"
    • Target Language: Select "Spanish (es)" from dropdown
  4. The output will include the Spanish translation and metadata

Batch Translation for Large Content

  1. Use the FluentC node with Resource: Translation, Operation: Translate
  2. Configure with:
    • Mode: "Batch"
    • Input: Your large HTML or text content
    • Target Language: Your desired language code
  3. The node will automatically poll until the translation is complete

Language Detection Before Translation

  1. Add a FluentC node with Resource: Language Detection, Operation: Detect
  2. Connect it to another FluentC node with Resource: Translation, Operation: Translate
  3. Use the detected language as the source language parameter

Retrieving Language Lists

  1. Add a FluentC node with Resource: Language, Operation: Get Many
  2. Execute the node
  3. The output will contain two arrays: supported_languages and source_languages, which you can use in other parts of your workflow

Migration from v1.x

Version 2.0 consolidates the three separate nodes from v1.x into a single FluentC node:

| v1.x Node | v2.0 Resource | v2.0 Operation | |---|---|---| | FluentC Translate | Translation | Translate | | FluentC Check Language | Language Detection | Detect | | FluentC Languages | Language | Get Many |

Existing workflows using the old nodes must be updated manually. Parameter names within each operation remain the same, so expressions referencing fields like input, targetLanguage, or mode should continue to work after migration.

Troubleshooting

Node Not Appearing

If the node doesn't appear after installation:

  1. Check Installation Method: Ensure you used the correct method for your setup
  2. Restart n8n: Always restart n8n after manual installation
  3. Check Directory: For manual installs, verify the package is in ~/.n8n/nodes/
  4. Check Permissions: Ensure n8n has read permissions for the nodes directory
  5. Check Logs: Look at n8n logs for any error messages during startup

Permission Issues

For Docker installations, you might need to ensure proper permissions:

# Inside the container
chown -R node:node ~/.n8n/nodes

Queue Mode

If you're running n8n in queue mode, you must use manual installation (Method 3).

Error Handling

The plugin includes comprehensive error handling:

  • Content Size Validation: Prevents requests exceeding 100,000 bytes
  • Batch Timeout Protection: Limits polling attempts to prevent infinite loops
  • API Error Handling: Gracefully handles API errors and rate limits
  • Continue on Fail: Option to continue workflow execution even if translation fails

API Rate Limits

The plugin respects FluentC API rate limits and uses the recommended polling intervals returned by the batch API to avoid overwhelming the service.

Development & Publishing

This package follows n8n community node standards:

  • ✅ Package name starts with n8n-nodes-
  • ✅ Includes n8n-community-node-package keyword
  • ✅ No runtime dependencies (only devDependencies)
  • ✅ Proper n8n configuration in package.json
  • ✅ Built TypeScript with proper exports
  • ✅ Single action node with Resource/Operation pattern

Support

For issues related to this N8N plugin, please check:

  1. FluentC API Documentation: https://fluentc.ai/docs
  2. N8N Community: https://community.n8n.io
  3. Plugin Repository: https://github.com/FluentC/n8n-nodes-fluentc
  4. n8n Community Nodes Documentation: https://docs.n8n.io/integrations/community-nodes/

License

MIT License - see LICENSE file for details.

Note: You need a valid FluentC API key to use this plugin. API keys are obtained through the FluentC sales website.