# An AI summary of every deliverable

> When a document is sent, n8n downloads it, extracts the text and writes a five-line summary for the project log. How to do it with colis, what to watch, and where it is written down.

Canonical: https://colis-site.vercel.app/en/use-cases/resume-ia-des-livrables · Markdown: https://colis-site.vercel.app/en/use-cases/resume-ia-des-livrables.md · Français: https://colis-site.vercel.app/use-cases/resume-ia-des-livrables

When a document is sent, n8n downloads it, extracts the text and writes a five-line summary for the project log.

```text
Colis Trigger       parcel.sent
If                  {{ $json.data.oneTime }} is false
HTTP Request        GET …/api/transfers/{{ $json.data.code }}/raw  (as a file)
Extract from File   PDF → text
Basic LLM Chain     "Résume ce document en cinq lignes."
Notion / Slack      the summary, on the project's page
```

## What is actually going on.
### The problem
You deliver reports, audits, meeting notes. The project log wants three lines, not a PDF.

### What colis does about it
A Colis Trigger on `parcel.sent`, an HTTP Request node that downloads the file, Extract from File for the text, then an LLM chain that summarises. The summary goes wherever you read: a Notion page, a Slack message, an email.

## The things that are easy to get wrong.
- **The download counts as an opening** — The deployment cannot tell n8n from the client: it records the parcel as opened and sends `parcel.opened`. Keep this workflow for parcels whose receipt you do not rely on, or trigger on `parcel.opened` instead.
- **Skip one-time parcels** — Downloading one burns it. Filter with an If on `data.oneTime`.

Packages: n8n-nodes-colis. [The n8n node, in full](https://github.com/mamadouwhile/colis/blob/main/packages/n8n-nodes-colis/README.md)