Blocks
Blocks are the vocabulary you build with. This page covers how to get the most out of them: reading a block at a glance, configuring it, and understanding the badges the library shows you.
Reading a block
Every block on the canvas shows its title, its inputs on one side, and its outputs on the other. Color tells you what kind of value a port carries, so related ports look related across the whole canvas. Required inputs are marked — a block with an unfilled required input is one of the first things validation will point at.
Give blocks your own titles and descriptions as you go. The defaults describe what a block is; your rename should say what it's for.
Configuration vs. inputs
Blocks have two kinds of knobs, and it helps to keep them straight:
- Inputs are the values a block consumes each run — the member to greet, the text to send. They change from run to run, so they usually arrive by wire.
- Configuration shapes the block itself — which event a trigger listens for, how many options a select menu has, which stored counter a state block reads. You set it once in the block's panel, and it can even change what ports the block shows.
Some blocks grow with their configuration: add three options to a choice menu and the block sprouts an input (or an outcome) per option. Trim the configuration and the extra ports fold away.
Picking channels, roles, and secrets
Inputs that refer to your server — a channel, a role — come with a picker listing what's actually there, so you select "#welcome" rather than pasting ids. Two things worth knowing:
- The picker also encodes why the workflow needs the resource ("send messages here", "assign this role"), which feeds the permission summary you review before publishing.
- Sensitive values (API keys, tokens) use secret inputs. The value is stored securely and referenced by the workflow; it never sits in the graph where someone reading the canvas could see it.
Badges in the library
The block library is honest about what will actually work on your server:
-
Best effort — the block works, but if Discord fails at exactly the wrong moment its effect may not be retried automatically. Fine for a greeting; think twice for anything you'd call critical.
-
Unavailable — the block can't currently run and can't be added. It stays visible so you know it exists, with a note explaining why.
-
Deprecated — being phased out. Existing uses keep working, and the note points you at the replacement to use for new builds.
-
Permissions — some blocks need the Juno bot to hold specific Discord permissions. The editor totals these across your whole workflow so there's one list to check, rather than a surprise at runtime.
Where blocks come from
The built-in library covers Discord and general utilities, but it isn't the whole story: workflows you install or depend on can add their public functions and events to your picker too. Building a ticket add-on on top of a ticket workflow feels the same as using the standard blocks — see The Store & reuse.