Data & wires

Every wire on the canvas carries a specific kind of value — a member, a message, a piece of text, a number. The editor tracks this for you, and it's the reason a finished Juno workflow rarely breaks at runtime: bad connections get refused while you're building, not discovered by your community.

Why a wire won't connect

Drag a wire to an incompatible input and it won't snap. When that happens, hover the two ports — each tooltip names what it produces or expects. The usual causes:

  • Different kinds of value. A member output can't feed an input that wants text. Look for a utility block that gets you from one to the other — for example, picking the member's display name.
  • One vs. many. Some outputs carry a list (all matching messages, every member with a role); some inputs want exactly one. Use a block that picks, filters, or loops.
  • Might be empty. Some outputs are only sometimes present — "the message's thread" when there may be no thread. Inputs that need a definite value won't accept a maybe; handle the empty case first with a condition.

If a connection feels like it should work, the fix is almost always one small utility block in between.

Digging into rich values

Discord objects are rich: a message has an author, a channel, text, a timestamp. You don't have to carry the whole object around — blocks that output rich values let you fan out individual fields as their own outputs, so you wire exactly the piece you need.

Choice values

Some inputs take one of a fixed set — a color, a channel type, an ordering. These render as dropdowns on the block, and wires carrying them only connect to inputs expecting the same set. No spelling mistakes, no guessing at valid values.

Defining your own shapes

When your workflow starts passing the same bundle of values around — say a ticket's topic, opener, and priority — define your own structure for it in the workflow. Your structure becomes a first-class value: wires carry it, blocks fan out its fields, and functions can accept or return it. You can define your own choice sets (enums) the same way.

If you mark a structure or enum public, workflows that build on yours can use it too — that's how a workflow becomes a platform for others (see The Store & reuse).

A habit that pays off

When a wire chain grows long, pause and name things: extract a function with typed inputs, or define a structure for the bundle you keep passing. The type system rewards you — the editor can then explain your workflow back to you, port by port, in your own vocabulary.