Lesson 1 5 min
Get your workflow ready
A listing is used by people you've never met. Make sure your workflow is saved to the cloud, tested, clearly named and free of secrets.
Cloud first
Only cloud workflows can be published, so you need to be signed in. Move a local workflow to your account with Move to cloud. Installing from the Marketplace needs an account too.
The checklist
- Saved, stable and tested: run it a few times to confirm it works.
- Nodes clearly named and organised.
- A plain note on every step (next lesson).
- No secrets in normal fields: keys and tokens live in Credentials, because a node’s normal fields travel with the workflow when you share it.
- Browser selectors generic enough to work for others, or explained.
What installers fill in
Some fields are always left blank for installers, and you can choose to blank other values too, such as the sheet or topic you used. Whoever installs the workflow fills them in, from a Ready to run checklist that opens with the canvas. Fields you chose to blank when you first published stay blank in every later version.
Key takeaways
- Only cloud workflows can be published, so sign in first.
- Test it a few times and give every node a clear name.
- Secrets belong in credentials; the secret check blocks publishing otherwise.