Settings

Hardcode "#welcome" into your greeting workflow and it works on exactly one server. Give the workflow a settings page instead, and anyone — a co-admin, another server, a Store user — can point it at their own channel without ever opening the canvas. Settings are what separate "my script" from "a thing others can use."

How it works

You declare the settings your workflow exposes — a channel here, a message template there, an on/off switch — and Juno renders them as a form on the workflow's page. In the graph, blocks reference settings instead of fixed values. At run time, each server's own answers flow in.

The result is one graph, many servers, zero copy-paste forks.

What makes a good setting

Expose the things a server admin would genuinely want to change:

  • Places and roles — the channel to post in, the role that marks staff. These use the same pickers as the editor, listing the server's real channels and roles.
  • Copy — welcome text, embed titles. Pair a template setting with a format block so admins can change wording without touching logic.
  • Behavior switches — thresholds, cooldowns, feature toggles.
  • Secrets — API keys for outside services. Marked sensitive, entered once, never displayed back.

And keep the list short. Every setting is a question someone has to answer before your workflow works; ten thoughtful settings beat forty exhaustive ones. Defaults help — a setting with a sensible default is one question fewer.

Required means "won't run without it"

Mark a setting required only when the workflow is genuinely meaningless without it. Required settings gate going live: a server can't turn on your workflow until they're answered, and the settings form points at exactly what's missing. Everything else should have a default and be optional.

Changing settings later

Two situations, two behaviors worth knowing:

  • An admin edits settings on a live workflow — the new answers take effect without a republish. Settings changes are cheap; that's their job.
  • You change which settings exist — that ships with the next publish. If your new version adds a required setting, servers that installed the old version will be asked to fill it in as part of upgrading, not ambushed at runtime.

Test like a stranger

Before publishing to the Store, reread your settings form as someone who has never seen your canvas: Do the labels make sense? Could you fill this in for your server in under a minute? The settings page is the first impression your workflow makes — most users will meet it long before they ever open the graph.