I don't see why it wouldn't be able to consume OData services. OData services are just a specific way of building and consuming RESTful services. So there is no special documentation to consume an OData service. The documentation available to consume a REST service should work with OData services.
Have a look at this blog post for more information regarding rest consume: Consume REST services with native microflow actions
OData (Open Data Protocol) is an OASIS standard that defines a set of best practices for building and consuming RESTful APIs. OData helps you focus on your business logic while building RESTful APIs without having to worry about the various approaches to define request and response headers, status codes, HTTP methods, URL conventions, media types, payload formats, query options, etc. OData also provides guidance for tracking changes, defining functions/actions for reusable procedures, and sending asynchronous/batch requests.
OData RESTful APIs are easy to consume. The OData metadata, a machine-readable description of the data model of the APIs, enables the creation of powerful generic client proxies and tools.
However you won't be able to benefit from the information in the OData metadata files.