Summarisation

Module 3 · Section 4 of 6

Summarisation

Summarisation inside a workflow usually looks like: I have a long document, I want a short version before I route or store it.

Same setup as classification. Basic LLM Chain node. System prompt:

Summarise the following in three sentences. Be specific. No filler.

The user message is the document content. The output is the summary, which you can store, send as a notification, or use as input to the next step.

Where this is useful: I pull RSS items from several feeds as part of a daily newsletter aggregation workflow. Before routing to the “relevant” or “skip” branch, I have a summarisation step that condenses each item to two sentences. The classification then runs on the summary, not the full article. This is faster and cheaper, and the summary captures enough signal for the classifier to work accurately.