The first Community Weekly Challenge is open: The Ledger Never Forgets.
Four stages, and each answer is the key to the next one.
Every file in this challenge is an append-only log. Nothing is edited and nothing is deleted: a change is just a new row. Rows arrive shuffled, corrections arrive after the thing they correct, and money is sometimes a number and sometimes a string, in the same column. Your job is to read it carefully and fold that history back down into the present, four times over.
It is solvable with core n8n nodes. Code nodes are allowed and never required.
Everyone gets their own data. Your dataset is generated from your forum username, so no two people share a file or an answer at any stage. A copied answer is simply a wrong answer, which means you can talk about method in this thread as much as you like without giving anything away.
Start here
The starter workflow is an importable n8n file with every request already built, each stage in its own labelled block, and sticky notes explaining what that stage asks for and what comes back. There are no answers in it. The folding is yours to write. If you would rather start from a blank canvas, everything it contains is also on the challenge page.
There is also a fixed sample ledger with its answer published, which needs no key and does not start your clock:
GET https://marketing.app.n8n.cloud/webhook/cwc/challenge-00/sample
It covers all six event types and both format traps, so if your pipeline reproduces the published answer, your fold is right and it is worth spending your clock. (That one returns raw JSON rather than a page, so point an HTTP Request node at it rather than clicking it.)
Three things worth knowing before you fetch
Your clock starts when you fetch your data, not when the challenge opens. You are ranked on how long you took, not on when you finished, so a late start costs you nothing. Reading the brief, thinking about it, and building against the sample are all untimed. Fetch when you are ready to sit down with it.
Check each stage before you move on. A wrong answer is not refused. It quietly opens a different, complete, equally real file, and you would fold that one perfectly and still be wrong. There is a check endpoint that tells you, per stage, whether a pair is right and what to look at if it is not. A badly formed answer costs you nothing. Submitting does not tell you which stage missed, so use the check.
Your participant key is a password, not a username. It arrives as a private message here on the forum, it is never shown on a page, and every endpoint needs your username and your key together. Because fetching your data is what starts your clock, anybody holding your key could start it for you, so please never paste it in a thread, including this one. Lost it? Reset it with the same username and email, and the old one retires immediately.
Points, and your record
Solving is worth 10. Finishing first adds 5, second or third adds 2, anywhere else adds 1. Your total carries from one challenge to the next and only resets when a new season starts, so turning up every week beats winning once.
Everyone who registers also gets a permanent public page showing what you have solved, where you finished and your points. It sits at a fixed address, needs no key to view, and stays at the same URL as new challenges are added. It is yours to share.
Closes Saturday 12 September, 23:59 UTC.
Ask here
This thread is the place. Questions about the rules, the formats, an endpoint behaving oddly, anything that reads ambiguously: ask, and the answer helps whoever comes next. Nobody can hand you the answer anyway, because your data is yours.
Please do not post a full solution until the challenge closes. Afterwards, share it everywhere. That is the point.
Good luck.