This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
AppSheet does not provide any tools to handle the response of a POST/PUT/DELETE. And there is no GET request.
In other words, you can send data with webhooks, but not retrieve anything.
Workaround # 1 - Custom Apps Script
There’s a great post by @LeventK about getting started with Apps Script. You could write a script to send the webhook for you and capture the response, then write it back to the sheet.
Workaround # 2 - Integromat/Zapier/Etc
Use a 3rd party automation tool to send the webhook, capture the response and write it back to the sheet.
Workaround # 3 - Create a webhook in the other service to respond back to AppSheet
Many web services that accept incoming webhooks also have a tool to create/trigger outgoing webhooks. See if you can set up a response webhook in the other service, to send data back to that row in AppSheet.
This is by far the easiest, but it requires the other service to also have a webhook tool.
It will eliminate the need for many 3rd party integrations, and open up lots of new options for integrating with other services.
The OpenAPI spec sounds good. I’ve integrated with plenty of APIs but never designed one, so I’m not sure, but the spec looks familiar and easy to use.
@Harsh_Ch, @prithpal, @Scott_Haaland,
There are already several template variables that we can access during a workflow, like <<_UPDATEMODE>>, <<_ATTACHMENTFILE_URL>>, etc.
Would it be possible to dynamically create a new template variable to store the response during the workflow execution?
Something like <<WORKFLOWACTIONNAME_RESPONSE>>(<< POST Webhook_RESPONSE >>)
Then we could parse the response and extract a value from <<WORKFLOWACTION_RESPONSE>> in a subsequent step, and set the value to a column as the last step.
Also, are there any JSON parsing tools in the works? Something to extract a value from a path, retrieve a list of keys, or set/substitute a value at a path, etc?
Thanks for all your work on this, AppSheet devs!
I can’t wait, but I know this is a ton of work. I’m just glad to know that some kind of response handling is in the pipeline.
@GreenFlux - The issue is that WebHooks are asynchronous by nature…it’s kind of like “Fire and Forget”, as the thread that is invoking the http request doesn’t wait for a response. The feature that @Harsh_Ch mentioned will essentially provide a new kind of connector (OpenAPI Spec based REST connector) that is able to handle the synchronous interaction and it will be able to wait for the response and return it back to your workflow. And finally, we are re-working all of the workflow capabilities, and this will give you much better control over being able to do things like invoke APIs and wait for responses…pretty exciting stuff coming up, but it all takes time :). If you want to send me your specific use cases offline, I’d love to check them out and see if they will work well in the new feature sets. Email to : shaaland@google.com
LinkedIn
Twitter
