Considering that there are no built-in components to achieve what I need. After reviewing the suggested template in the discussion, I think that way may be better than using action: custom.
I did the testing it in my dashboard, and it worked without issues.
My card now looks like this:
- type: custom:button-card
icon: mdi:play
template:
- tap_multi_calls
variables:
tap_multi_calls:
actions:
- action: call-service
service: script.do_something
- action: navigate
navigation_path: /dashboard/secondary
confirmation: false
Thank you for this info!