Invoke REST Service Action

0

Please add:

1. New response type "Multipart"

Support multipart HTTP responses in the "Invoke REST Web Service" action, not only multipart request bodies.

2. Add header and response code/body mapping for response type "Binary"

HTTP headers are independent from the body type and should be accessible for mapping even when the response body is handled as binary stream / attachment.

Typical use cases:

* file download + metadata headers
* OCR/AI APIs returning metadata in headers
* presigned URLs
* correlation IDs
* filename/content-disposition handling

3. Add new response type "Text" / "Raw"

Currently the action supports only:

* Binary
* JSON

A plain text / raw response mode is missing.

This causes problems with APIs returning:

* CSV
* text/plain
* XML without JSON wrapping
* custom text formats

without requiring JSON deserialization.

4. Decouple response parsing from mapping capabilities

Currently:

* JSON mode enables response/header mapping
* Binary mode disables it

The response metadata (headers/status code) should always be available independently from body parsing mode.

5. Add support for content-type aware handling

Example:

* application/json => JSON parsing
* text/csv => text mode
* application/octet-stream => binary mode

Currently JSON mode appears to force Newtonsoft JSON deserialization regardless of actual response content type.

6. Allow mapping of:

* HTTP status code
* raw response body
* response headers

for all response modes.

This would significantly improve compatibility with modern REST APIs.