Resources · n8n integration

AWS Textract n8n integrationAutomate AWS Textract with n8n.

One node operation, and it carries the whole job. The AWS Textract n8n integration takes a receipt or invoice image already in the workflow and sends it to Amazon Textract for analysis. No trigger ships with the node, so you choose what starts the run.

Try the AWS Textract integration on n8nSee the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What can the AWS Textract n8n integration do for you?

The AWS Textract node sends a file that is already sitting in the n8n workflow to Amazon Textract, and hands the answer back as the node output. The catalog lists a single operation, default.analyzeExpense, built for receipts and invoices. You tell the node which binary field holds the image, and the rest of the workflow works on whatever Textract returns.

Start with the file. Textract wants an image, and n8n wants that image in a binary field before the node runs. A node that downloads an attachment, an HTTP Request that fetches a scan, a storage node that reads an object: each one leaves the file in a binary property. The move to remember is a one-liner. Copy the exact name of that property into Input Data Field Name, and the node runs.

First scenario, accounts payable. Supplier invoices land in a shared mailbox, Gmail pulls the attachment, Textract analyzes it, and the response is appended row by row to a ledger in Google Sheets. One execution per invoice, and a readable history at the end of the month.

Second scenario, field expenses. People post photos of receipts into a channel, the workflow picks the image up, runs the analysis, and answers in the same Slack thread so the person who posted knows the receipt went through. Leave Simplify on for that reply, and turn it off later if a downstream node needs to read deep into the raw response.

Third scenario, clearing a backlog. A Schedule Trigger fires at night, the workflow lists a folder of scans, and the files go through the node one item at a time. None of that is instant, and it does not need to be. The node has no trigger of its own, so the starting point is always a Schedule Trigger on a fixed interval, an n8n Webhook (a URL a third-party service calls to launch the workflow), or the trigger of another app you already run.

Two markers before you build. The description of the required field names PNG and JPEG as supported file types, so the step that produces the binary property should hand over one of those. And anything that falls outside this operation goes through the HTTP Request node, which calls any endpoint of the API while reusing the same AWS credential (the access you register once in n8n) through predefined authentication. For a wider look at the platform first, the n8n review and the n8n training cover the ground.

Connect

How do you connect AWS Textract to n8n?

  1. 01

    Create the AWS credential

    In n8n, open the Credentials menu and create an AWS (IAM) credential. It asks for your AWS Region, an Access Key ID and a Secret Access Key. Both keys are generated in the IAM console: pick your user name, then Security credentials, then Create access key. Set a description tag such as n8n integration so you can spot the key later.

  2. 02

    Or assume a role instead

    The second type, AWS (Assume Role), authenticates by assuming an IAM role through AWS STS. The credentials n8n uses for the AssumeRole call are either entered by hand or read automatically from the environment n8n runs in. That second path exists for teams who self-host n8n on AWS infrastructure (EKS, ECS or EC2) and would rather not store static keys inside n8n.

  3. 03

    Point the node at the binary field

    Add the AWS Textract node, pick your credential from the dropdown, and leave the operation on Analyze Receipt or Invoice. That leaves Input Data Field Name: copy the exact name of the binary property carrying the image, the one the previous node produced. Run the node once on its own and read the output before wiring anything behind it.

Actions

What the AWS Textract node handles

The AWS Textract node exposes one operation. For each one: the node as you configure it in n8n, the required fields, and our field notes.

01

Analyze Receipt or Invoice

analyzeExpense

What you see in n8n

Notes & use cases

This operation sends the image carried by the workflow to Amazon Textract for receipt and invoice analysis, and hands the answer back as the node output.

Key parameters

  • Input Data Field Name: the name of the input field containing the binary file data to be uploaded. Copy it from the node that produced the file. Supported file types are PNG and JPEG.
  • Simplify: on, the node returns a simplified version of the response; off, it returns the raw data, which is what a later node needs when it reads deep into the payload.
Use cases
a restaurant receipt photographed by a colleague, read once and filed into the month's expense sheet instead of being typed in by hand.
Need help

Need help automating AWS Textract with n8n?

A person reads every message.

FAQ

AWS Textract and n8n, the questions that come next

01Is the AWS Textract n8n integration free to use?
Yes on the n8n side. The node ships with n8n, so there is nothing to install and nothing extra to pay for the node itself, whether you run n8n Cloud or a self-hosted instance under the Community Edition and its Sustainable Use licence. A workflow behaves the same way in both places, so a flow built locally moves to Cloud without being rebuilt. What Amazon charges for Textract usage sits on the AWS side of your bill and is not covered here. The credential itself is created once in n8n and reused everywhere, so a second AWS node in the same instance costs you nothing but a dropdown selection.
02Which credentials do you need for AWS Textract in n8n?
One of two types. AWS (IAM) authenticates with an access key, meaning your AWS Region, an Access Key ID and a Secret Access Key, all generated from the IAM console under Security credentials. AWS (Assume Role) authenticates by assuming an IAM role through AWS STS instead, and the credentials n8n uses for that AssumeRole call are either typed into n8n or read automatically from the environment n8n runs in. The second type exists for teams self-hosting n8n on AWS infrastructure such as EKS, ECS or EC2 who prefer not to keep static keys inside n8n. Either one is created once in the Credentials menu and then offered in the node's dropdown.
03What are the limits of the AWS Textract node in n8n?
It depends on what you are asking for. The catalog gives this node one operation, Analyze Receipt or Invoice, so that is the job it handles end to end. The description of its required field, Input Data Field Name, names PNG and JPEG as supported file types, which tells you what the previous step should hand over. Anything that falls outside that operation goes through the HTTP Request node, which calls any endpoint of the API while reusing the same credential through predefined authentication. That pattern is standard in n8n, so an unusual call costs you one extra node rather than a rewrite of the workflow.
04Does the AWS Textract node react in real time?
No, because it never starts a run by itself. This tool has no trigger node in n8n, so the workflow begins somewhere else: a Schedule Trigger firing on a fixed interval, an n8n Webhook, meaning a URL a third-party service calls to launch the workflow, or the trigger of another tool already in your setup. In practice the choice follows the file. Invoices arriving by email start from the mail trigger. Scans piling up in storage suit a nightly Schedule Trigger that walks the folder. A form or an app able to post to a URL goes straight to the Webhook, and the run starts the second the file lands.
05n8n or Make for AWS Textract?
Both can call it, so the decision is about everything around it. n8n self-hosts through Docker or npm and also runs as n8n Cloud, the hosted offer, with an identical workflow in either case. Make is hosted only, with no self-hosting option, and is billed per operation. If the documents you push through Textract are sensitive and you want them staying on infrastructure you control, self-hosting settles it. If nobody on the team wants to run a server, the hosted route is lighter to start. On cost, per-operation billing stays predictable at low volume and less so once a nightly batch walks a large folder of scans.
Same platform

Other docs you might need on this stack.

Browse all integrations