Resources · n8n integration

n8n Summarize nodeConfigure Summarize in n8n.

The n8n Summarize node crunches numbers across items, the way a pivot table does. It has nothing to do with AI text summaries: it sums, counts, averages and groups the fields of the items it receives. Ten parameters, no credential, one aggregated result.

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the n8n Summarize node actually do?

Summarize aggregates the items that reach it, in a manner similar to Excel pivot tables. It reads one field across every incoming item, applies one of the 8 aggregation methods to it, and returns the result. Nothing is rewritten and no model is called here: the node does arithmetic and grouping on data that is already in the workflow. The name is misleading if you arrive expecting a text summary.

First scenario, a revenue line. A workflow pulls yesterday's order rows from Google Sheets, and Summarize runs a Sum on the amount field. Every row in, one item out, carrying the total. Add Fields to Split By set to the country column and the same run gives one total per country instead of one global figure.

Second scenario, a daily headcount. Leads land in a sheet with a source column, Summarize applies Count Unique to the email field, splits by source, and the result goes to a Slack channel as a short digest. Counting distinct values is the part nobody wants to write by hand, and it is a dropdown choice here.

Third scenario, a readable list. Concatenate on a product name field, with Separator set to New Line, turns a batch of items into a single block of text that drops straight into a Gmail message body. That is text handling, but mechanical text handling: values joined in order, nothing interpreted.

When is Summarize the wrong step? When every input item has to survive: the node replaces the batch with its aggregated result, so a workflow that still needs the individual rows downstream should aggregate on a branch, not in the main line. When the calculation is not one of the 8 methods, the arithmetic belongs elsewhere. And when the figures you want to aggregate are still sitting behind an API that no dedicated node covers, they have to be fetched first, which is what the HTTP Request node is for.

The limits are worth knowing before you build on it. The node is at version 1 and it does not open a workflow: something has to run before it, a Schedule Trigger, a Webhook, or the trigger of a tool. Field names are typed as text, so a renamed column silently breaks the aggregation unless Continue if Field Not Found is turned on. If pivot logic in n8n is new to you, the n8n training covers the workflow patterns these aggregations sit in.

Parameters

Which parameters does the Summarize node expose?

The Summarize node has 10 parameters. For each one: the node as you configure it in n8n, what the parameter changes, and our field notes.

01

Aggregation

fieldsToSummarize.aggregation

What you see in n8n

Notes & use cases

Aggregation decides how the values of the field you want to summarize get combined into one result. Pick it first, because the other fields that appear depend on the method chosen.

Key parameters

  • Sum, Average, Min and Max: the numeric methods, for amounts, quantities and scores.
  • Count and Count Unique: how many values came in, and how many distinct ones.
  • Append and Concatenate: keep the values themselves, as a list or as one joined string.
Use cases
on a batch of order rows, Sum over the amount field returns the day's revenue as a single item.
02

Field

fieldsToSummarize.field

What you see in n8n

Notes & use cases

This is where the aggregation gets pointed at something. Field holds the name of an input field that you want to summarize, and it is typed as text rather than picked from a list, so the spelling has to match the incoming data exactly.

Key parameters

  • Field: the name of an input field you want to summarize, entered as text (placeholder e.g. cost, hint: Enter the field name as text). The name goes in, not the value, so cost and not {{ $json.cost }}.
Use cases
a column renamed upstream is the usual reason an aggregation returns nothing, so check this spelling first.
03

Include Empty Values

fieldsToSummarize.includeEmpty

What you see in n8n

Notes & use cases

Some items arrive with the field present but blank. This toggle appears alongside the Append and Concatenate methods and settles what happens to those blanks.

Key parameters

  • Include Empty Values: turned on, empty values take their place in the appended or concatenated result; left off, they are dropped from it.
Use cases
when the aggregated list has to line up position by position with another list, keeping the blanks preserves the alignment.
04

Separator

fieldsToSummarize.separateBy

What you see in n8n

Notes & use cases

Concatenating values glues them together, and Separator is what goes between them. The hint in the panel says it plainly: what to insert between values.

Key parameters

  • Comma, Comma and Space: the two readable defaults for an inline list.
  • New Line, Space, None: one value per line, a single space, or no separator at all.
  • Other: opens the Custom Separator field.
Use cases
New Line turns a batch of product names into a block you can paste into an email body without extra formatting.
05

Custom Separator

fieldsToSummarize.customSeparator

What you see in n8n

Notes & use cases

Only the five separators in the dropdown are offered by default. Selecting the other value reveals this text field, where you type whatever the output actually needs.

Key parameters

  • Custom Separator: free text, used in place of the dropdown choice once Separator is set to Other.
Use cases
a pipe or a semicolon between values when the concatenated string feeds a system that reads one specific delimiter.
06

Fields to Split By

fieldsToSplitBy

What you see in n8n

Notes & use cases

Left empty, the node returns one figure for the whole batch. Fields to Split By is the group by statement: it breaks the summary into separate results based on the values of other fields.

Key parameters

  • Fields to Split By: the name of the input fields you want to split the summary by, entered as text, separated by commas for several of them (placeholder e.g. country, city).
Use cases
with a Sales Rep column and a Deal Amount column, a Sum on Deal Amount split by Sales Rep gives a total per rep.
07

Continue if Field Not Found

options.continueIfFieldNotFound

What you see in n8n

Notes & use cases

By default, a field to summarize that appears in none of the items stops the node with an error. This option, added from the Options collection with Add option, replaces that error with a single empty item.

Key parameters

  • Continue if Field Not Found: turned on, the node continues and returns one empty item; turned off, it keeps the default error behavior.
Use cases
a scheduled report that has to keep running on a quiet day, when the batch arrives without the column at all.
08

Disable Dot Notation

options.disableDotNotation

What you see in n8n

Notes & use cases

Nested data is the reason this option exists. n8n reads child fields in the parent.child format, which is convenient until a field name contains a dot of its own.

Key parameters

  • Disable Dot Notation: turned on, referencing child fields as parent.child is disallowed and the name is read literally; turned off, dot notation keeps working.
Use cases
incoming items whose keys already look like order.total as a flat name, where the literal reading is the correct one.
09

Output Format

options.outputFormat

What you see in n8n

Notes & use cases

Shape of the result, not content of it. This option is recommended once Fields to Split By is in use, because that is when several results exist at the same time.

Key parameters

  • Each Split in a Separate Item: one output item per split out field.
  • All Splits in a Single Item: one item that lists the split out fields.
Use cases
separate items when each group goes on to its own row or its own message, a single item when the whole table is posted in one go.
10

Ignore items without valid fields to group by

options.skipEmptySplitFields

What you see in n8n

Notes & use cases

Real batches are rarely clean. Some items simply do not carry the fields you are splitting by, and this option decides whether they still count.

Key parameters

  • Ignore items without valid fields to group by: turned on, input items that do not contain the Fields to Split By are ignored; turned off, they are kept.
Use cases
a merged batch where only part of the rows carry the country column, and the rest would otherwise form a group of their own.
Need help

Need help automating Summarize with n8n?

A person reads every message.

FAQ

Summarize node questions

01Is the n8n Summarize node included on n8n Cloud and self-hosted?
Yes. Summarize is a core node shipped with n8n, so there is nothing to install and no extra cost on the n8n side. It behaves the same on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance installed with Docker or npm under the Community Edition and its Sustainable Use license. A workflow built in one place runs the same way in the other. The page describes the highest node version read in the catalog, version 1. An older workflow may still display an earlier version with fewer options, since a node never changes version on its own.
02What do you need to make the Summarize node work?
Nothing to authenticate. This node has no credential and no Authentication selector, so there is no account to connect, no key to paste and no scope to grant. What it does need is data: the node runs on the items it receives and does not open a workflow, so something has to run before it, a Schedule Trigger, a Webhook, or the trigger of a tool. Then you name a field to summarize, choose an aggregation method, and optionally add options from the Options collection with Add option, each added option appearing as one more field in the panel.
03What are the limits of the Summarize node?
It aggregates values, and that is all it does. There is no AI here, no text rewritten and no model called: a sentence never gets shortened by this node. The methods are the 8 in the Aggregation dropdown, so any calculation outside them has to happen elsewhere in the workflow. Field names are typed as text rather than picked from the incoming data, so a renamed column breaks the aggregation unless Continue if Field Not Found is on. The node also replaces the incoming batch with its result, which means individual items are not available after it.
04When do you choose Summarize rather than doing the maths elsewhere?
Choose it when the calculation is one of the 8 built-in methods and applies to a whole batch of items: a sum, an average, a minimum, a maximum, a count, a count of distinct values, an append or a concatenation. Add Fields to Split By and you also get a group by, which is the part that saves the most time. Look elsewhere when you need every input item to continue downstream, when the aggregation depends on a condition per item, or when the figures live in an API that has to be called first.
05n8n or Make for this kind of aggregation?
It depends on four criteria, and none of them is about who wins. Hosting first: n8n can be self-hosted with Docker or npm, or used on n8n Cloud, while Make is a hosted platform with no self-hosting option. Data control follows from that, since a self-hosted instance keeps the aggregated figures on your own infrastructure. Cost model next: Make is billed per operation, which matters when a batch of items goes through a workflow every hour. Visual logic last: both build workflows visually, so the deciding factor is usually the first three points rather than the canvas.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.