Resources · n8n integration

AWS Rekognition n8n integrationAutomate AWS Rekognition with n8n.

Can a workflow read what is inside a picture? The AWS Rekognition n8n integration exposes 1 operation on a single Image resource, with 5 analysis types and 6 optional fields. No trigger node ships with it, so a Schedule or Webhook step opens the run. Built for teams drowning in visual files.

Try the AWS Rekognition integration on n8nSee the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the AWS Rekognition n8n integration actually give you?

The AWS Rekognition n8n integration wires Amazon's image analysis service into the rest of your automation. The node carries 1 resource, Image, and 1 operation on it: hand over a picture, get back what Rekognition saw in it. Five kinds of analysis sit behind one Type field, and 6 optional fields shape the answer before it reaches the next step.

Start with the gesture, not the field list. Drop one Analyze step between whatever brings an image into the workflow and whatever stores the verdict. A moderation queue is the clearest version of it: a user uploads a photo, the node runs detectModerationLabels, and the result decides whether the picture publishes or lands in a Slack channel where a human takes one look and moves on.

Catalog work is the second pattern. A shop sitting on thousands of product shots loops them through detectLabels, caps the answer with Max Labels, pushes Min Confidence up so only solid guesses survive, and appends one row per image to Google Sheets. Tagging nobody volunteers for gets done while the office is empty.

Third: text trapped inside pictures. Support screenshots, a photo of a shelf label, a scanned form someone sent as a JPEG. detectText pulls the strings out and the workflow writes them to Postgres, where they finally become searchable. detectFaces and recognizeCelebrity round out the five types on the same Type dropdown.

The node covers that single Image operation from the catalogue. Whatever else you want from the Rekognition API is work for the HTTP Request node, which calls any endpoint of the service and reuses the same AWS credential through predefined authentication. One extra step in the canvas, no second credential to manage.

Plan for one thing before you build: AWS Rekognition has no trigger node in n8n. A workflow that uses it starts elsewhere, with a Schedule Trigger firing at a fixed interval, an n8n Webhook (a URL another service calls when something happens on its side), or the trigger of an app you already automate. Picking between those three is the real design decision, and the n8n training spends time on it.

Connect

How do you connect AWS Rekognition to n8n?

  1. 01

    Create an AWS access key

    Log in to the IAM console, open your user name in the upper right and select Security credentials, then Create access key. Pick a use case on the best practices page, or Other when none of them fits. Set a description tag such as n8n integration so the key is recognizable in six months, then reveal the Access Key ID and the Secret Access Key.

  2. 02

    Add the AWS (IAM) credential in n8n

    Open the Credentials menu in n8n and create an AWS (IAM) credential. Select your Region first, then paste the Access Key ID and the Secret Access Key. Working with short-lived keys? Turn on Temporary security credential and add the Session token. A credential is created once and offered in the dropdown of every AWS node you add later.

  3. 03

    Or assume a role instead

    The second credential type, AWS (Assume Role), authenticates by assuming an IAM role through AWS STS. The keys used for the AssumeRole call are either entered by hand or read automatically from the environment n8n runs in. That second path is the one to take when you self-host n8n on EKS, ECS or EC2 and would rather not keep static keys sitting in the interface.

Actions

What the AWS Rekognition node does

The AWS Rekognition node exposes 1 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceAnalyze
Image✓

Image

1 operation
01

Analyze

image.analyze

What you see in n8n

Notes & use cases

The Image resource holds one operation: n8n sends a picture to Rekognition and returns what it found.

Key parameters

  • Binary File: on, the image comes from the binary field of the current item; off, from an S3 object.
  • Input Binary Field: the name of the input binary field holding the file.
  • Bucket and Name: the S3 bucket and the object key name.
  • Type: which of the 5 analyses runs, from detectLabels to recognizeCelebrity.
  • Min Confidence: no label below that confidence level comes back.
Use cases
a nightly run reads new uploads through Bucket and Name, runs detectLabels, and tags each photo.
Need help

Need help automating AWS Rekognition with n8n?

A person reads every message.

FAQ

AWS Rekognition and n8n: common questions

01Is the AWS Rekognition n8n integration free?
Yes on the n8n side. The AWS Rekognition node ships with n8n, so there is nothing to install and no add-on to buy. It behaves the same on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance under the Community Edition and its Sustainable Use licence. The workflow you draw is identical in both places: same node, same single Image operation, same fields. The AWS credential you create sits in the Credentials menu and is reused by every other AWS node you add later, without a second setup.
02What credentials does the AWS Rekognition node need?
Two types work. AWS (IAM) authenticates with an access key, so you supply the Region, the Access Key ID and the Secret Access Key. When the keys are short-lived, switch on Temporary security credential and add the Session token. AWS (Assume Role) is the other route: n8n assumes an IAM role through AWS STS, and the keys used for that AssumeRole call are either entered manually or read automatically from the environment n8n runs in. That second option fits a self-hosted instance on EKS, ECS or EC2, where keeping static keys inside n8n is precisely what you want to avoid.
03What are the limits of the AWS Rekognition node in n8n?
The catalogue gives the node 1 resource, Image, and 1 operation on it. That operation covers five kinds of analysis through the Type field, and 6 optional fields shape the result: Regions of Interest, Version, Word Filter, Max Labels, Min Confidence and Attributes. Anything in the Rekognition API that sits outside that operation goes through the HTTP Request node, which calls any endpoint of the service and reuses the same AWS credential through predefined authentication. In practice you keep the dedicated node for the analysis and add one HTTP Request step when a workflow needs something else.
04Does AWS Rekognition trigger an n8n workflow in real time?
No, because AWS Rekognition has no trigger node in n8n. A workflow that uses it starts somewhere else, and there are three usual openings. A Schedule Trigger fires at a fixed interval and works through a batch. An n8n Webhook, which is a URL another service calls when something happens on its side, starts the run as soon as that service reports an upload. Or the trigger of another app already wired into your automation does the job. Schedule Trigger suits overnight tagging; Webhook suits an image that should be checked as soon as it arrives.
05n8n or Make for AWS Rekognition?
It depends on where the workflow should live. Make is a hosted automation platform with no self-hosting option, billed per operation, so the bill follows volume and image batches grow fast. n8n runs on Cloud or on a server you own, which matters when the pictures are customer data you would rather keep inside your own infrastructure. Both give you a visual canvas and both get the job done. The honest split: choose Make if you never want to maintain a server, choose n8n if you want control over hosting, data and the cost model, or if you expect to reach for HTTP Request on the rest of the API.
Same platform

Other docs you might need on this stack.

Browse all integrations