I think you’re looking for our Transactional Session feature.
It doesn’t involve the saga directly - that would be a somewhat dangerous antipattern in the first place. But it enables you to do some initial database work and also send a message atomically (either both succeed or both fail) so the rest of the backend stuff could continue, and that initial message could be the message that starts a saga.