A small n8n task for practising your own workflow reasoning. Read the brief, build a workflow and submit the requested answers with your workflow JSON. Each challenge page explains its task and participation dates.

An n8n instance, an n8n community account and a Weekly Challenge participant key. Use the community username shown on your forum profile. Your participant key belongs to the challenge, not your n8n login.

Yes. Read the challenge, download the starter and view public standings without connecting. Connect with your username and current participant key when you need your personal assignment, submission or saved result.

Choose Create account and enter your community username and email. Check your forum inbox for the key. Registration does not start your challenge timer. Keep your key private.

Use the opening, closing time and timezone published on the current challenge page. A visible page or downloadable starter does not mean submissions are open. New data requests, answer checks and submissions must meet the challenge window.

Read the brief and the fields shown on that challenge's submission form. Answer ranges, required files and explanations can differ between challenges. Earlier challenge pages and saved results retain their original rules.

It verifies your community username and participant key so the page can show your personal actions and saved status. Connecting alone does not fetch your personal data or start the timer. Never enter your n8n password in the participant key field.

Check your community username and use your latest participant key. Remove accidental spaces when copying them. A replaced key no longer works. If connection still fails, keep the exact error and reference ID and contact the organisers privately. Connecting does not start your timer.

Choose Recover key and use your community username and registered email. A replacement is sent to your forum inbox. Use that new key for future requests. Recovery preserves your original assignment, timing, accepted submission and points.

Check the private messages in the same community account you registered. Do not create several accounts or post your email or key publicly. Contact the organisers with your community username and the registration or recovery error, if one appeared.

Recover a replacement key and contact the organisers privately. Remove the exposed key from any public post, screenshot or shared workflow you control. Treat the key as private account access.

The first successful personal data issue starts your original timer. This can happen through Start challenge or by executing the starter's personal HTTP request. Reading the brief, connecting your account and importing a starter without running that request do not start it.

C09 gives you eight personal invoices and twelve payments. Everyone uses the same field names and calculation. Personal values differ. Match posted payments by exact invoice_id, ignore cancelled invoices and pending payments, and clamp each invoice balance to zero. Every new production packet has at least one unpaid invoice. Re-fetching keeps your original data.

Fetching again returns your saved assignment and keeps the original first-fetch time. Closing a tab, reconnecting or replacing a key does not restart or pause the clock. Keep a safe local copy of your fetched data while you build.

The server records a time for your complete final request at its first processing step, before the account and workflow checks. That recorded final becomes your finish only if the same request is durably accepted. Processing after that timestamp is shown separately. A browser click or local clock is not the official timestamp.

Keep the error, request ID and approximate time with timezone, then contact the organisers. Any verified correction must be explicit and auditable. Original first-fetch and accepted records stay intact; do not assume a retry, key recovery or support message has reset your time.

Build with native n8n nodes and normal expressions. Code, Function and Function Item nodes are prohibited, including disabled or disconnected copies. Other normal native node choices, settings and editor export metadata are supported. You do not need to copy one exact node layout.

No. The challenge is for practising your own reasoning and n8n skills. Do not use AI to solve the task, plan or build the submitted workflow, generate its nodes or expressions, debug the solution, calculate answers or write the explanation.

Build and explain your own work. This also applies to AI-generated workflows that you edit before submitting.

A leaderboard position is not the goal on its own. If AI does the reasoning, you miss the practice that builds the skill. Try the steps yourself and ask for a hint in the discussion if you get stuck.

Yes. The starter fetches your personal invoices and payments and splits the two lists. It contains no practice dataset, calculation or completed solution. Read the task before running it: your first personal data issuance starts your timer. Use n8n documentation to understand native nodes and build the calculation yourself.

Submit your own work. Do not reuse someone else's completed challenge solution or submit their answers. Keep your personal data, answers and completed workflow out of the public discussion while participation is open. Follow the organisers' sharing instructions after the challenge.

Send concerns privately to the organisers with concrete information. Fast completion alone does not establish AI use. Eligible correct submissions are accepted automatically during the season; integrity and reward review take place at season end.

Submit unpaid_invoice_count, total_outstanding_cents and a clean exported workflow JSON. Both answers must be whole numbers. Personal production packets have at least one unpaid invoice and a positive outstanding total. An individual invoice can still have a zero balance. Your explanation is optional, up to 2,000 characters. Confirm the own-work and no-AI declarations.

Export a copy of the workflow from your n8n editor. Clear the participant key and remove passwords, credential references, pinned data and saved execution data. Keep the normal nodes, connections and settings needed to understand your solution. Upload the JSON export itself, not a screenshot, a text summary or an execution result.

No. Uploaded workflow JSON is retained as private submission evidence and is not executed by the challenge service. Submitting it does not publish it as an n8n template or a public forum post.

Read the exact message and check that the file is a valid, clean n8n workflow JSON export within the displayed size limit. Remove any prohibited Code, Function or Function Item node, even if it is disabled or disconnected. Wait for the file to finish loading before submitting. Keep your original export while preparing a clean copy.

Submit final must return an accepted result, and My result must show its saved receipt. Selecting a file or seeing a file-ready message does not submit it. Check saved status first if the response is lost.

C09 allows five incorrect mathematical answer pairs per ten minutes. Follow the delay returned by the server. File, validation, service and delivery failures do not consume this incorrect-answer allowance. Keep the same request while an outcome is unresolved.

Check My result or the saved request status before creating a new final submission. Keep the same request while its outcome is being reconciled. The page retains the selected file and answers during that process; avoid refreshing or closing it until you know the saved outcome.

If the result stays unknown, contact the organisers with the request ID and exact error. A browser error alone does not tell you whether the server saved the submission.

No. A retry after acceptance returns the original accepted receipt and does not grade a replacement upload. Keep the receipt and check your saved result. Your original acceptance and timing remain the record for that challenge.

Eligible correct submissions are accepted automatically during the season. You do not need to wait in a human workflow-review queue to appear in the standings. Season-end integrity and reward checks are separate from that acceptance.

Accepted entries are ranked by measured competition duration, from first personal data issuance to the recorded final request that is accepted. Lower durations rank higher. Exact-duration ties share rank and points. Calendar submission order and alphabetical order do not determine rank.

Rank 1 earns 15 points, ranks 2 and 3 earn 12, and later ranks earn 11. Exact-duration ties share rank and points. Rank bonuses remain provisional while participation is open because a later entrant can finish faster.

Season 3 begins with C08. Your Season 3 total adds your C08 and C09 points. Not starting C09 does not erase your C08 points. Equal totals use the published combined completion-time rule. Season 2 results, original timings and awarded points remain available separately and are not reset or carried into Season 3.

Unavailable is different from zero or unranked. Check saved status before sending a new final, keep your receipt and contact the organisers with the exact error. The service must not invent a duration or replace your original accepted result to make a ranking appear.

No. Use the published season announcement for the reward terms. Final eligibility and integrity checks happen at season end before rewards are confirmed. Do not assume a certificate, prize or other benefit unless it has been announced.

Include the challenge, your community username, the action you tried, the exact error, any request or reference ID and the approximate time with timezone. For a display problem, add your browser and device. Share only screenshots that hide keys, email addresses and private answers.

Use the challenge's Questions and discussion link for general task wording or platform problems. Send account access, private workflow evidence and personal timing issues directly to the organisers. Do not post your participant key or full submitted solution in the public thread.

Do not assume an extension or a timing credit. The organisers investigate reports and announce any verified repair, deadline change or scoped correction. Keep the original error and request information so the incident can be checked.

Public standings show community usernames and published results such as rank, points and measured time. Participant keys, registered email addresses and uploaded workflow evidence are not part of the public leaderboard. Keep secrets out of anything you share yourself.

Contact the organisers privately with your community username and a description of what you need. Do not send your participant key, n8n password or unrelated personal information. Account access and data requests should not be handled in a public challenge reply.