Skip to content
Start learning
Menu

Contribute

Submit a workflow to the library

Anything you send through GitHub is public the moment you send it, even if deleted later. Remove every key, password, URL, email and name first. Then send the workflow by GitHub issue with a link to your own gist. A script checks it, a person reads it, and it is listed under your name as submitted, with its checks not yet run.

Submit on GitHub (free account needed)Ask a question first

Not open yetOpens when the first workflow passes its checks. One submission at a time per person until one is published. A reply within 3 working days.

01Two ways in

By GitHub issue now, by form once the store is live

Both land in the same queue and get the same checks. The file stays yours: you link to your own gist, we never copy it into our repository.

GitHub, from day oneNot open yet

Open the submission issue in the todkett organisation. It asks for:

  • The title, the track and the tool it runs in.
  • One line in the library's shape: Starts when X. Ends with Y.
  • The steps, one per line, each marked rule, AI, person or output.
  • A link to your own public gist holding the workflow file. Not a pull request: a pull request publishes the file into our repository the moment it opens, and closing it does not remove it from history. With a gist you keep control.

Within minutes a check runs on the linked file and comments with the result. If a key was found, revoke it now; it is already public.

The form, once the store is liveNot built yet

For people without a GitHub account. The same fields as the issue, a link to a public gist or repository or the file pasted with a cap, three required boxes, an optional name and one link, and the contact consent. It waits for the lead store and the spam check.

Until then, without a GitHub account: write to hello@todkett.com with the same details and a link to your file. Never paste a key into an email either.

02The release check

What the check refuses, and what we refuse outright

The script decides safety; a person decides sense. Nobody at Todkett reads a workflow file for danger by eye. The list is public, so you can check your file before you send it.

The script refuses a file that holds any of these

  1. 01

    Steps that run commands on a machine

    An Execute Command step, a remote shell step, or any step that moves files to or from a server by file transfer.

  2. 02

    Steps that touch files on disk

    A local file trigger, and steps that read or write files on the machine n8n runs on.

  3. 03

    A workflow that calls another workflow outside the file

    An Execute Workflow step pointing at a workflow by id or by address. Only a workflow carried inside the file is allowed.

  4. 04

    Code steps that reach out of the sandbox

    A Code step whose JavaScript contains require, fetch, process, eval or child_process, or whose Python imports modules, opens files or runs exec.

  5. 05

    Instance variables

    Any $env or $vars expression anywhere in the file. Settings go in a Config step, in plain sight.

  6. 06

    Addresses not from the Config step

    An HTTP Request step whose address is not a value read from the step named Config, or whose address carries a literal host around the expression.

  7. 07

    Secrets and account traces

    The script strips credential ids, tokens, keys, passwords and resource-picker leftovers, and names each credential so you can add your own. A file with a private name on our list is refused.

Its report names the step and the reason. It never prints a secret. Any schedule in the file ships switched off, and every credential is kept by name only, so others see which accounts a workflow needs and never a value.

Refused outright, whatever the script says

  1. 01

    Anything that scrapes a site against its terms.

  2. 02

    Anything that sends messages to people who did not agree to receive them.

  3. 03

    Anything that moves money.

  4. 04

    Anything that touches a health or legal decision without a person step.

  5. 05

    Anything that claims an outcome it cannot show.

  6. 06

    A file that is someone else's work reposted. Send what you built or have the right to share.

03Licence and terms

Free to copy, credit required

Every workflow with the Stress tested badge that Todkett owns outright downloads free. The paid product, if one ever comes, is a room with people in it, not files.

The library licence

Todkett’s own bundles are published under Creative Commons Attribution 4.0: reuse, adapt and share them, for any purpose, with credit to Todkett. A contributed file on the second shelf stays under its contributor’s name and licence, at their own address.

No lawyer has reviewed these terms yet; they are written to be plain and fair, and they will be read by one before the first bundle ships. The terms of use cover the rest of the site.

What you confirm when you submit

  1. 01

    You built the workflow, or you have the right to share it. Client or employer work may belong to them: check first.

  2. 02

    You removed every credential, key, address, email, company name and person's name before sending it.

  3. 03

    You give Todkett a licence to list, publish and adapt it, and you are credited by the name you give, with one link.

  4. 04

    Todkett may refuse, delist or remove it at its own discretion, and will do so on your request.

  5. 05

    You are 18 or older.

04After you send it

What happens next, step by step

Most submitted workflows stay on the second shelf for a long time. That is said here so nobody waits for a page that is weeks of testing away.

  1. 01

    The script checks the file

    Within minutes on GitHub. It strips secrets, applies the list above and comments with the result. A file that fails is never listed.

  2. 02

    A person reads it for sense

    Within 3 working days you get a reply. It may say only that the workflow is in the queue for the weekly slot. The AI label is set from the steps, not from the description.

  3. 03

    It is listed as submitted

    One line on its track page and here: the title, your name, the date, and a link to the exact version of your file that was read, shown with the words “the file we read on [date]”. If the file is later deleted or changed, the line is removed.

  4. 04

    The 8 checks, when the slot allows

    Run in a separate n8n with throwaway accounts, never in our main instance. A full page, with the Stress tested badge and a free copy, comes only after every check has passed in a recorded run.

  5. 05

    One at a time

    One open submission per person until one of yours is published. Send the one you know best.

The 8 checks are described on the about page. To report a workflow that is yours, unsafe or breaks the rules, write to hello@todkett.com. We acknowledge within 3 working days and delist the item while we check. The rules of talk and the reply promise are on the community page.