Use case

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.

n8n

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

The situation

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.

Worth watching

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.

Packagesn8n-nodes-colis

Other ways to deliver.

Invoice on approval

An n8n trigger on parcel.approved: you are told, and the invoice goes out with the parcel’s code as its reference.

Change requests in your own tools

Every request for changes arrives signed on your route, with the client’s comment, ready to become a ticket.

Send it. They sign off. You know.

Your storage, a delivery page under your name, a webhook at every step. Nothing hosted by someone else.

Try the demo Deploy the delivery page GitHub