The Store & reuse
You don't have to build everything yourself. The Store is where finished workflows live — install one as-is, remix one into your own, or depend on one as a foundation to build against.
Three ways to use someone else's work
Install when you want the thing it does. Pick a workflow, answer its settings, turn it on. You never need to open the canvas.
Remix when you want almost the thing it does. Remixing copies the workflow into your server as your own draft — reword the messages, add a step, delete what you don't need, publish as yours. The original is untouched, and your copy won't change when the original updates.
Depend when you're building on top of it. Add another workflow as a dependency and its public functions and events show up in your block library like built-ins: a ticket workflow's "ticket opened" event, an economy workflow's "award points" function. Your workflow stays small and focused; the foundation does the heavy lifting.
Rule of thumb: install to use, remix to own, depend to extend.
Dependencies don't move under you
When you depend on a workflow, you build against the exact version you picked. If its author publishes an update tomorrow, nothing about your workflow changes — no surprise breakage from someone else's release schedule.
Upgrading is your call, made in the editor: it shows what changed in the new version — especially to the functions and events you're using — and re-checks your graph against it before anything is saved. If the new version reshapes something you rely on, you find out there, not in production.
Being worth depending on
Publish to the Store and other builders may start standing on your workflow. What they see is exactly what you marked public — your public functions, events, and types are your product:
- Name them for the person who's never seen your canvas.
- Once published, treat a public function's inputs or an event's payload as a promise: add capabilities, don't reshape existing ones. When a reshape is unavoidable, Juno has you label the change as breaking so dependents upgrade with eyes open.
- Everything you don't mark public stays private, freely changeable forever. Keep your public surface small.
Provenance
Everything that arrives via the Store keeps its receipts: where a workflow came from, which release, who published it. When you're deciding whether to trust, upgrade, or remove something, that history is on the workflow's page — and Juno won't garbage-collect a release out from under workflows that still depend on it.