Conditions decide which triggered records enter an action path. Use the catalog item reference when routing item-specific fulfillment. A short description can change and may be shared by different items, so it is a weaker identity. Combine conditions deliberately: AND narrows a path, while OR can admit records outside the intended process.
Actions can update the triggering record, create tasks, request approval, or record notes. Data pills pass values from the trigger or earlier actions into later actions. Keep the source of a value clear, especially when a user field can be blank. Test the action result, not only the saved definition. An active flow with the wrong condition is still wrong. A successful positive test also needs a negative control proving unrelated records don't receive tasks.