I've accomplished this by putting the "common" actions in a separate action list, then calling that action list (via the "Run Action List" action) when I need to execute the sequence of actions. It's sort of an "action list subroutine". Depending on the actions and your configuration, you might want/need to parameterize the action list with Action List Parameters, so that callers can provide the required input to the actions.
Mike’s suggestion is the best way to achieve this. It’s also worth noting that the Include Project action can run an action list in a separate project, so you can create a subproject (ie Subroutines.fbp5) with various action lists, and and call it from different projects.
(The only time I would advise not using a subproject is if you need to call the action list many times (ie 100s or 1000s of times per build), in which case it’s better if it lives in the same project (less performance overhead.) 10-20 times should be unnoticeable.