Youwee LogoYouwee

Workflows

Workflows are the place where Youwee stops being just a downloader and starts behaving like a repeatable pipeline. Use them when you want the same post-download steps to happen in the same order every time.

Think in steps, not one giant automation

The strongest workflow setups are usually short and predictable. Instead of building one huge chain, define a few clear steps that are easy to test and easy to recover if something fails.

  1. Capture or queue the media.
  2. Finish the download itself.
  3. Run one or more follow-up plugin steps.
  4. Review the result through logs, notifications, or the final destination.

Workflow patterns that make sense in practice

Download, then notify

The simplest useful workflow is a notification after success or failure. This is a good first test because it proves the plugin is actually firing when you expect.

Download, then upload

This is the normal next step for storage plugins. Let Youwee finish locally first, then push the file to Drive, a NAS, or another destination.

Download, then process or clean up

Some workflows make a second pass after the file lands, such as moving it, renaming it, exporting something else, or preparing it for another app.

Triggers, order, and failure behavior

In the plugin workflow UI, order matters. Steps run from top to bottom, so the first step should usually be the safest and most essential one.

  • Choose the trigger: after download, when queued, before start, or when failed.
  • Set the order: move the most important step higher in the list.
  • Choose failure behavior: either continue to the next step or stop the chain when a step fails.

Test with small jobs first

Before you trust a workflow on large downloads or important media, run it against a small test file. That helps you verify timing, destination, and plugin behavior without creating a bigger mess.

  • Start with one plugin step, not five.
  • Check plugin logs if the output is not what you expected.
  • Only add another step after the first one is stable.

Design rules that keep workflows sane

  • Prefer short chains over giant “do everything” workflows.
  • Keep upload, notify, and cleanup steps distinct so failures stay obvious.
  • Use stop-on-failure when a later step depends on an earlier result.
  • Use continue-on-failure when later steps are independent and still worth running.