Keep each #Action Button focused on a single target action, and defer the rest of the work to #Triggers that fire from that action's DML.

• The #Action Button performs one primary DML on a primary object (insert, update, etc.).
• One or more #Triggers listen for that DML event and orchestrate the downstream actions — additional updates, related-record creation, notifications, approvals, or any other rules-driven operations.

The user still experiences a single click, while the underlying logic stays modular and easy to maintain.