muklion.blogg.se

You can create a simple fixed-syntax command parser, use advanced AIĪnd language processing libraries or services, or anything else appropriateįor your particular goals. Google Chat does not constrain the way in which you implement your app's Status, or for some kinds of app prototyping. Incoming webhooks are best suited for simple, one-off apps to report alerts or This approach is "hardcoded" to a specificĬhat space and does not allow user interaction, and this type of app cannot be You can create an app that just injects messages to a chat space, using calls to Such an app using Apps Script, with its built-in It can be much simpler-especially in terms of auth-to implement Google Chat and Google Workspace services would look like this: This is especially usefulįor apps that also integrate with Google WorkspaceĪnd write data using Google Sheets, Slides, Calendar, Drive, and so on.Ĭonsider how an implementation would look not implemented in Apps Script. You can create your app logic entirely in Apps Script. In this arrangement, the app implementation still must use HTTP for sending Google Cloud Pub/Sub- the app implementation subscribes to a topic If the app implementations reside behind a firewall, Google Chat may be This allows the implementation to make use of existing libraries and components In this design, youĬonfigure Google Chat to integrate with a remote service via HTTP: Or other HTTP implementation in on-premises servers. One of the most common ways that apps are implemented is using a web service Where to instantiate your code, and how it interacts with Google Chat, This logic needs to be implemented in your code, using whatever libraries Google Chat supports integration with app, but does not implement the app See Choosing a service architecture for helpĭeciding which approach is best for your apps. This section describes some of the most common architectural approaches used

This chapter helps guide you on your choice of implementation architecture when