Currently, only custom fields embedded within the document are accessible in the Power Automate connector.
However, in my use case, I need to route signed agreements dynamically to specific repositories (e.g. SharePoint or other storage) based on metadata that is not part of the document itself.
At the moment, the only workaround is to include a tag in the agreement name. This approach is not reliable, as users can modify or remove the tag, which introduces risks for misrouting documents.
To address this, it would be highly valuable to make sender-level custom field values retrievable within Power Automate flows.
This would enable a more robust and maintainable approach by allowing routing logic to rely on structured metadata defined at the sender level, rather than on editable agreement names.