Appsheet integration with Apps Script and People API

[Gonzalo4]

Hello everyone. I have an Appsheet app with a bot that executes an Apps Script function. That was working well. I just added the People service to my Apps Script project as below:

People service added

I need the people API to create/delete contacts. I know there is another way to create/delete contacts but I think it is deprecated and I want to do it with People API. The problem is now Appsheet cannot execute any functions from Apps Script.

Apps Script last executions does not show errors, because there are no executions since I added People service to Apps Script. If I go to my bot's monitor in Appsheet I see this:

There is a similar question with no solutions here: https://www.googlecloudcommunity.com/gc/AppSheet-Q-A/Apps-Script-Authentication-Error-in-AppSheet/m-...

In my case I don't see the authorize button as well.

What can I do to use my bot again? Thanks

[WillowMobileSys]

Since this started AFTER adding calls to the People service, the Script is likely not sending the authorization to that service correctly.  I assume this is Google's service.  Even so, credentials are probably not shared.  How authorization is submitted to the external service is dependent on the API.  Please check with that service to see what their protocol is.

For example, one API I have used required a call with credentials to get back a Session ID.  All subsequent calls were made with that Session ID.  Then a follow-up call to close that Session ID.  

Generally, API's will have you submit the auth credentials as settings in the header details of the call.

I hope this helps!

[Gonzalo4 · Accepted solution]

I ended up resolving the problem myself. I'll explain the exact steps I did:

- Create a trigguer for the function causing problems.

- Apps Script made me authorize the code again before i could set the trigger up.

- Function working from Appsheet again.

I guess what i needed to do was just execute the function again so it make me authorize. I wrote the steps I did just in case. It was in fact a Google's service issue it seems. Thanks for the response.