Hey everyone!
Challenge 06: The Support Queue is live! This is the third challenge of Season 2.
A support desk has 24 tickets. Build a native n8n workflow to count how many are open, then how many of those open tickets are urgent. Both questions use the same personal dataset.
Start Challenge 06 · Get the starter workflow · Read the rules
Your existing username and participant key still work. Your Challenge 04 and 05 points stay in your Season 2 total.
- The first successful personal data fetch starts your timer. The first accepted final submission stops it. Practice is untimed.
- Add your own filtering and counting. The starter’s two blank answer cards receive your computed counts; they are not extra HTTP requests.
- Submit both answers, your sanitized workflow JSON and your own explanation. Remove your participant key, credentials and pinned data from the export.
- Correct eligible submissions join the leaderboard automatically. The fastest measured completion ranks first: 15 points for first, 12 for second and third, and 11 for the rest. Exact time ties share a rank. Rewards are reviewed at season end.
- No AI assistance of any kind, including interpreting, planning, generating, debugging, solving or explaining your solution. Code, Function, AI, Agent, MCP and Tool nodes are not allowed. Read the complete native-node rules before starting.
Closes Sunday, 25 October 2026 at 23:59 IST / 18:29 UTC.
Use this thread for questions, feedback or an error. Include the stage, exact message and approximate time. Keep participant keys, credentials, personal data, final answers and complete solutions private while the challenge is open.
The submission is still bugged
Why?
@kjooleng The upload validator was rejecting normal settings metadata included in n8n workflow exports. That check is now fixed and live. We verified it with real JSON uploads and retries using fresh test accounts.
Please try uploading your workflow JSON again. You do not need to remove normal export settings to get past this check. Your original timing record and existing points have not been changed.
I am still penalised due to the submission bug
When will the bug be eliminated?
It so frustrating to see the same bug every week.
Timing is way off…
@kjooleng Your workflow is now accepted. We’re reviewing the recorded attempts and completion time to determine a fair timing correction. Your original timestamps and submission evidence will remain intact, and we’ll explain how any adjustment is calculated.
We’re also preparing a revised challenge system for the next round, with submission reliability and fair timing as priorities. Your current result remains part of this review.
Stop using cryptic language. Please use plain English. This is throwing a lot of people (at least me) off track.
Blanking Setting.key and keeping username seems contradictory. If you want to keep username, why blank out the keys?
The submission is already bugged enough. Why make it even more more confusing?
Thanks to everyone who took on The Support Queue! Challenge 06 has closed. Your recorded results and Season 2 points remain preserved.
For the export question above: keep your forum username, but clear the participantKey value in My settings. The key is private, like a password, and should not be included in an uploaded workflow. You do not need to delete the field names or normal workflow settings.
Challenge 07: The Exception Desk is now live. It is the Season 2 finale, and your C04, C05 and C06 points carry forward. Please use the C07 questions thread for the new challenge.
