Use cases
Hand the work over. Let the answer do the rest.
Four ways of delivering, and three things that can happen once your client answers.
01Deliver
From your machine to your client.
The delivery page for people, the CLI for pipelines, and the same receipt behind both.
colis-drop · colis
Get a mock-up signed off
A PDF or an image sent under a code, previewed by the client in the page, approved in one click or sent back with a comment.
colis · colis-drop
Deliver from CI
Every test build sent from CI under a code, and the client’s answer coming back as a status: approved, or changes.
colis-drop
Deliver heavy files
Up to 2 GB by default, sent by the browser straight to your bucket, in parts, resumed if the connection drops.
colis-drop
A confidential delivery
A password the client types once, a short lifetime, and a code that is gone at the first download.
02Automate
What happens once they answer.
Every step is a signed webhook. n8n, or a route of your own, takes it from there.
n8n-nodes-colis
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.
@colis/protocol
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.
n8n-nodes-colis
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.
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.