Build a Custom Automation in Velveteen
Updated August 16, 2026
The custom builder lets Velveteen platform admins arrange a workflow from guided steps. Add actions, conditions, waits, and approvals where they belong without writing code or choosing technical targets.
During the current pilot, the builder is admin-only. Most workflows need a starting event and one action. Conditions, timing, approvals, and an Otherwise path are optional.
Build a workflow
- 1
Choose an artist or label
Start with the artist or label, give the automation a name, and choose whether it applies to all releases, one artist, or one release. - 2
Choose When
Pick the event that starts the automation. Status-based triggers also ask you to choose the status in plain language. - 3
Add each step
Use Add step after the starting event or between existing steps. Choose an action, condition, wait, or approval. - 4
Add a decision when needed
A condition starts with one check. Add up to five checks and choose All rules or Any rule. If yes continues the main path. Otherwise stops unless you add a step there. - 5
Preview and activate
Changes save automatically. Review and activate stays unavailable until the draft is complete and saved. Preview opens in a dialog, shows every possible path, and makes no changes.
Keep branches understandable
Rules stay flat and each condition has two outcomes: If yes and Otherwise. The builder does not support nested rule groups, loops, branch merging, arbitrary code, or more than two outcomes.
Removing a condition that has Otherwise steps asks for confirmation. The If yes path stays in place, while steps used only by Otherwise are removed.
Frequently asked questions
Do I need an Otherwise path?+
No. Otherwise stops by default. Add an Otherwise step only when you want different work to happen when the condition does not match.
How many checks can one condition use?+
A condition supports one to five checks. Choose All rules when every check must match or Any rule when one matching check is enough.
Can branches join again later?+
No. Each path ends independently so the workflow remains clear and safe to edit.
What if two tabs edit the same draft?+
Autosave uses a revision check. A stale save shows a conflict instead of silently overwriting the newer draft.
Related articles
Automations overview
A central workflow hub for release operations, recipes, custom automations, runs, waits, approvals, and recovery.
Recipes
Start with a release recipe, see why a dependency is unavailable, and install a draft without activating it.
Runs and recovery
Read a run timeline, approve high-impact steps, reconcile unknown outcomes, and recover without duplicating effects.