LIVEAI Bootcamps · May 2026 · 🇫🇷 CET
Home/Resources/Integrations/Aws Comprehend
Resources · Integrations · n8n FREE · 2026Logo de AWS Comprehend

AWS COMPREHEND n8n INTEGRATION: AUTOMATE AWS COMPREHEND WITH N8N

AWS COMPREHEND N8N INTEGRATION: AUTOMATE AWS COMPREHEND WITH N8N

Need help

Need help automating Aws Comprehend with n8n?

Our team will get back to you in minutes.

Reply within 1 business hour
Why automate

Why automate Aws Comprehend with n8n?

The AWS Comprehend n8n integration gives you access to 3 powerful text analysis actions that transform how you handle unstructured data. Instead of manually reviewing text content or building custom NLP pipelines, you can deploy production-ready text analysis in minutes. Each action leverages Amazon's machine learning models, trained on vast datasets, to deliver accurate results across multiple languages.

The benefits of automating AWS Comprehend are substantial. Significant time savings: no more manual reading and categorization of text content—set up smart rules that automatically process incoming data and route it based on analysis results. Improved responsiveness: trigger instant actions as soon as sentiment drops below a threshold or specific entities are detected. Consistent analysis: machine learning models apply the same criteria to every piece of text, eliminating human inconsistency. Seamless integration: connect AWS Comprehend to over 400+ applications in n8n workflows, from CRMs to databases to messaging platforms.

Concrete workflow examples include: automatically tagging support tickets based on detected entities and routing them to the appropriate team, analyzing social media mentions to track brand sentiment in real-time, detecting the language of incoming emails to route them to the correct regional support queue, and processing customer reviews to extract product mentions and associated sentiment scores. Teams using this integration typically save 10-15 hours per week on manual text classification tasks.

Credentials

How to connect Aws Comprehend to n8n?

  1. !
    1 step

    How to connect Aws Comprehend to n8n?

    1. 01

      Add the node

      AWS Comprehend uses IAM (Identity and Access Management) credentials for authentication. You'll need an AWS account with Comprehend service access and an IAM user with the appropriate permissions.Basic configuration:Create an IAM User: In the AWS Console, navigate to IAM → Users → Add User. Create a user with programmatic access enabled.Attach Comprehend Permissions: Add the ComprehendFullAccess policy to your IAM user, or create a custom policy with only the specific Comprehend actions you need (DetectEntities, DetectDominantLanguage, DetectSentiment).Generate Access Keys: In the IAM user's Security Credentials tab, create an Access Key. Save both the Access Key ID and Secret Access Key—you won't be able to see the secret again.Configure n8n Credentials: In n8n, go to Credentials → New → AWS. Enter your Access Key ID, Secret Access Key, and select your AWS Region (must match where you want to run Comprehend).Test the Connection: Add an AWS Comprehend node to a workflow and select your new credentials. Run a test with sample text to verify everything works.

    Aws Comprehend credentials
    TIP
    💡 TIP: Create a dedicated IAM user specifically for n8n integrations rather than using your root account credentials. This follows the principle of least privilege and makes it easier to audit and revoke access if needed. Also, consider using IAM roles with temporary credentials for production environments.
Need help

Need help automating Aws Comprehend with n8n?

Our team will get back to you in minutes.

Reply within 1 business hour
Actions

Aws Comprehend actions available in n8n

  1. 01
    Action 01

    DetectEntities text

    The DetectEntities text action is your go-to tool for extracting structured information from unstructured text. It identifies and categorizes entities such as people, organizations, locations, dates, quantities, and more—transforming free-form text into actionable data points that can drive your automation logic.

    Key parameters:

    • Credential to connect with: Select the AWS IAM account that provides access to AWS Comprehend. This dropdown shows all configured AWS credentials in your n8n instance. Required.
    • Language Code: Specify the language of your input text using a dropdown selection. English is commonly used, but Comprehend supports multiple languages including Spanish, French, German, Italian, and Portuguese. Required.
    • Text: The main input field where you provide the text to analyze. Accepts free-form text input—you can use expressions to pull text from previous nodes. Required.
    • Additional Fields: An optional section for adding extra configuration options based on specific requirements.

    Use cases:

    • Extract customer names and company mentions from incoming emails to auto-populate HubSpot CRM fields
    • Identify location references in support tickets to route issues to regional teams
    • Parse contract documents to extract dates, monetary values, and party names
    • Build a knowledge base by extracting key entities from articles and documentation
    DetectEntities text
  2. 02
    Action 02

    Detect Dominant Language

    The Detect Dominant Language action automatically identifies which language a piece of text is written in. This is essential for building multilingual workflows that need to route, translate, or process content differently based on language—all without requiring human review.

    Key parameters:

    • Credential to connect with: Select your configured AWS IAM credentials from the dropdown. Required.
    • Resource: Specifies the resource type, set to 'Text' for this action. Required.
    • Text: The content you want to analyze for language detection. Paste text directly or use expressions to pull content from previous workflow nodes. Required.
    • Simplify: A toggle switch that simplifies the output when enabled. When turned on, returns a cleaner response with just the dominant language; when off, returns full confidence scores for all detected languages. Optional.

    Use cases:

    • Route incoming customer messages to language-specific support queues automatically
    • Trigger translation workflows with Google Translate only when content isn't in your primary business language
    • Tag and categorize user-generated content by language for analytics
    • Filter and sort multilingual content before processing with language-specific models
    Detect Dominant Language
  3. 03
    Action 03

    DetectSentiment text

    The DetectSentiment text action analyzes text to determine its emotional tone—positive, negative, neutral, or mixed. It returns both the dominant sentiment and confidence scores, enabling you to build workflows that respond intelligently to the emotional content of text data.

    Key parameters:

    • Credential to connect with: Choose your AWS IAM account from the dropdown list of configured credentials. Required.
    • Resource: Set to 'Text' to indicate you're analyzing text content. Required.
    • Language Code: Specify the language of your input text. Sentiment analysis accuracy depends on correct language selection, with English being a common default. Required.
    • Text: Enter the text you want to analyze for sentiment. This field accepts free-form input and supports n8n expressions for dynamic content. Required.

    Use cases:

    • Prioritize negative customer feedback for immediate human review
    • Track brand sentiment across social media mentions in real-time dashboards
    • Trigger escalation workflows when support ticket sentiment indicates frustration
    • Score and rank product reviews to highlight both praise and criticism
    DetectSentiment text
You've seen the integration

Build your first workflow with our team

Drop your email and we'll send you the catalog of automations you can ship today.

  • Free n8n & Make scenarios to import
  • Step-by-step setup docs
  • Live cohort + community support

Frequently asked questions

  • Is the AWS Comprehend n8n integration free?
    The n8n integration itself is free to use, but AWS Comprehend is a paid service with usage-based pricing. Amazon charges per unit of text analyzed—for example, sentiment detection costs $0.0001 per unit (100 characters) as of current pricing. New AWS accounts receive a free tier that includes 50,000 units per month for the first 12 months, which is generous for testing and small-scale production. n8n (self-hosted) is open-source and free; n8n Cloud has its own pricing tiers. Always check the current AWS Comprehend pricing page for accurate costs based on your expected volume.
  • What languages does AWS Comprehend support in n8n?
    AWS Comprehend supports multiple languages across its different actions, though coverage varies. For entity detection and sentiment analysis, supported languages include English, Spanish, French, German, Italian, Portuguese, Japanese, Korean, Hindi, Arabic, and Chinese (simplified and traditional). The Detect Dominant Language action can identify over 100 languages. When configuring actions in n8n, you'll select the appropriate language code from a dropdown. For best results, ensure your Language Code parameter matches the actual language of your input text—mismatches can significantly reduce accuracy.
  • How long does it take to set up the AWS Comprehend n8n integration?
    Most users can complete the setup in 15-30 minutes. The bulk of time is spent on the AWS side: creating an IAM user (5 minutes), configuring permissions (5 minutes), and generating access keys (2 minutes). Adding credentials to n8n takes under a minute. Building your first working workflow with a Comprehend action typically takes another 10-15 minutes, depending on complexity. If you already have AWS credentials with Comprehend permissions, you can be running your first text analysis in under 5 minutes. The hardest part is usually planning what to do with the analysis results—the technical integration is straightforward.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.