- Home
- Resources
- Integrations
- Summarize
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
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.
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.
Parameters index
Aggregation
fieldsToSummarize.aggregationWhat 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.
Field
fieldsToSummarize.fieldWhat 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, socostand not{{ $json.cost }}.
Include Empty Values
fieldsToSummarize.includeEmptyWhat 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.
Separator
fieldsToSummarize.separateByWhat 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.
Custom Separator
fieldsToSummarize.customSeparatorWhat 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.
Fields to Split By
fieldsToSplitByWhat 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).
Continue if Field Not Found
options.continueIfFieldNotFoundWhat 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.
Disable Dot Notation
options.disableDotNotationWhat 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.childis disallowed and the name is read literally; turned off, dot notation keeps working.
order.total as a flat name, where the literal reading is the correct one.Output Format
options.outputFormatWhat 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.
Ignore items without valid fields to group by
options.skipEmptySplitFieldsWhat 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.
Need help automating Summarize with n8n?
A person reads every message.
Summarize node questions
01Is the n8n Summarize node included on n8n Cloud and self-hosted?
02What do you need to make the Summarize node work?
03What are the limits of the Summarize node?
04When do you choose Summarize rather than doing the maths elsewhere?
05n8n or Make for this kind of aggregation?
Get our weekly integration tips.
No spam. Unsubscribe anytime.
