Get Key-Value store record action in Zapier connector doesn't work with non-JSON values

[HonzaKirchner]

Bug report

In our Zapier connector, when I use the Get Key-Value store record action, it successfully reads the value because the number of KVS reads visible in Console increases by 1, but it doesn't return the value to Zapier.

The problem is that the Zapier integration can work only with JSON values and the record the user is using is encoded in JSON, but does not have JSON structure. The value is true.

Example of error in Zapier

Proposed solution

What

• Allow user to use JSON content type, but JSON content is true
• Allow users to work with content types other than just JSON, like text, arrays, files, etc.
• Update output of the action but keep current behaviour for JSON content type (do not break)

How

• Update the get value query https://github.com/apify/apify-zapier-integration/blob/master/src/searches/get_value.js
• The query should work with varies content types and based on content type handle value in kvs
• The output of action of non-JSON records should be

{
  "contentType": "<record content type>",
  "value": "<record value>"
}

• if the value will be file let's use build in file dehydration see https://docs.zapier.com/platform/build-cli/overview#file-dehydration
• Update action description and help text to cover allowing other than JSON values
• Add tests to cover new functionality

Bug reported here

[oleksandravalko]

@drobnikj Hi. For this solution we use stashing, which, if I get it correctly, Zapier doesn't prefer for cases like ours, when data is stably available. We opted for this approach, because we couldn't find a way how to make files dehydrate directly from Apify KV store and being presented to further steps in meaningful way. If you have some experience with that, I'd appreciate your input.
At the moment newest version 4.0.10 should be able to handle application/json records as it was previously, plus handle valid, but non-object looking JSONs and plain/text returned in {value:...} format. Big files of mentioned content types and all of other types are being dehydrated with stashing step.
File size caps we introduced for both direct requests and stashed files.
Please check the version out, you can use this KV store with mock data if you need. Here is code.
Thanks 🍀