У нас вы можете посмотреть бесплатно Appsmith: Google OAuth Consent Flow (Same Mechanism for Calendar/Contacts Verification) или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
This video demonstrates the Google OAuth 2.0 consent flow within an Appsmith application, specifically showing the connection of Google Drive to our AI Agent feature. This process is intended to assist with Google API verification. 🔗 Appsmith Instance Shown: test.appsmithai.com The OAuth client ID used in this demonstration is the same one configured to request scopes for Google Calendar, Google Contacts, and Google Directory when users integrate those services into their Appsmith applications. *Key Steps Shown in This Video (Google Drive Example):* (0:00) Logging into Appsmith using Google SSO. (0:07) Navigating the Appsmith dashboard and creating/opening an "AI Agent" application. (0:17) Accessing the query/datasource section within the AI Agent. (0:24) Showing the "AI Datasource" configuration. (0:28) Editing the AI Datasource to add a new "Knowledge Source." (0:32) Selecting "Google Drive" as the knowledge source. (0:37) Clicking "Connect Account" to initiate the Google OAuth flow for Google Drive. (0:39) The Google Account chooser screen. (0:41) Google's intermediate "Sign in to Appsmith" confirmation screen. (0:46) The Google OAuth consent screen, displaying permissions required for Google Drive access by "Appsmith" (or your project name). (0:52) Granting permissions by clicking "Allow." (0:55) Confirmation of Google Drive connection within Appsmith. *Relevance to Google Calendar, Contacts & Directory Verification:* While this video specifically demonstrates the Google Drive integration: 1. The *OAuth mechanism and user experience* for connecting Google Calendar (or Contacts/Directory) is identical. 2. Users would select "Google Calendar" as a datasource (instead of Google Drive as a knowledge base). 3. They would then be presented with a similar Google OAuth consent screen, but it would display the following requested scopes relevant to Calendar/Contacts/Directory: `https://www.googleapis.com/auth/calendar.e...` (View and edit events on all your calendars) `https://www.googleapis.com/auth/contacts.r...` (See and download your contacts) `https://www.googleapis.com/auth/contacts.o...` (See and download contact info automatically saved in your "Other contacts") `https://www.googleapis.com/auth/directory....` (See and download your organization's G Suite directory) This demonstration is provided to show how users authorize our application to access their Google data via the standard OAuth 2.0 flow. For any questions regarding specific scope justifications, please reach out to integrations@appsmith.com