Is the return values from Gemini API too complex to return by webhook?

[hhoanganh]

Hi everyone, as a free user, I am trying to call Gemini API by using webhook, free account cannot use appscript.
I can call the API and get the response as the bot monitoring result below.
For the return value, as i tried with: text / response.text / parts.text / content.parts.text / candidates.content.parts.text, ... still get the same error "Key not found".
I want to ask is this because of the Limitation of return values mentioned here  ?

[WillowMobileSys]

In short, yes I believe it is too complex.  The "text" key seems to be buried several layers deep - Response->Candidates->content->parts->text

Allowing return values from an API call is relatively new.  I believe AppSheet currently only supports ONE nested level of returned objects - for Script or API calls.  The below is aimed at Scripts but I believe it applies to API calls as well - especially the section on "Type Limitations"

Use return values from Apps Script task 

There are alternatives. 

If Gemini supports scripting and calls into other API's, you could call AppSheet API from the Gemini system. 

There are also integrator services (e.g. Make) which have connectors to many systems.  I know Make supports the AppSheet API.  If they also support Gemini, you may be able to use Make as a go-between - to extract the data from the Gemini API, transform it and then submit it into the AppSheet API.

I hope this helps!

[hhoanganh]

Thank you. I’m just exploring the limits of what AppSheet's free version can do. I’ll try other options as well—maybe some new ideas will help.