Answer
No — collecting additional input data as part of an action (like a rejection reason) is only supported for Absence Request notifications specifically, because feeding that extra data back into the action handler adds significant complexity that configured notifications generally aren't built for; configured notifications otherwise only support simple, no-input actions. Before working around this, it's worth reconsidering the use case — for example, whether the extra reasoning data is genuinely needed on a small mobile screen, or whether you can instead define separate notification types for different scenarios so the user picks between two simple actions rather than typing a reason.