Connect Google Drive Knowledge to an Assistant
Authorize the account, select approved files in Drive Picker, confirm a non-empty selection, and inspect the result before testing answers.

Authorization is only the first step
Connecting a Google account and importing useful material are separate events. In Resonoon, Google Docs knowledge uses the Google Drive Picker. Authorizing access makes the picker workflow available, but it does not add documents by itself. The team still has to browse, choose a non-empty selection, and confirm it. This distinction matters when someone expects the assistant to answer from a handbook immediately after account authorization. Until a selection is confirmed, treat the source as not yet imported.
Before opening the picker, define the assistant's job and the questions its sources should support. A booking assistant may need appointment rules and cancellation terms, while an internal operations assistant may need different material. Decide which files are appropriate and who is allowed to approve them. This is a team decision, not something account authorization resolves. A connected account may expose many files, but access to a file does not mean it belongs in a customer-facing knowledge set.
Select, confirm, and inspect
In the knowledge-source management flow, use the visible connect and browse operations to reach the Drive selection experience. Review the file names and choose only relevant material. Confirm a non-empty selection to start the import and save it. If the picker closes without a confirmed selection, do not assume anything was added. Reopen the source workflow and inspect what is selected. The interface's visible state is more reliable evidence than the fact that an account was authorized earlier.
For example, a clinic might connect the account used by its communications team and select a patient-facing appointment guide. It should not include internal staffing notes merely because they appear beside the guide. Before confirmation, check that the chosen document is the approved version and covers the intended audience. If there are similarly named drafts, ask the document owner to identify the canonical one. Importing a plausible-looking file first and planning to sort it out later can make unsupported answers available in the meantime.
After confirming, inspect the source state and displayed errors. A connected account is not proof of a successful import, and an attempted selection is not proof that every intended file was saved. Read any status and error information actually shown. Do not assume a particular status label, completion time, or background process that the interface has not displayed. If the result is unclear, review the account and file selection, then use only the retry or sync controls visible in the product.
Verify with questions that matter
Choose several representative questions before importing. One should be directly answerable from the selected material. Another should depend on a condition such as appointment changes or eligibility. A third can cover a subject intentionally excluded from the selection. Write down the expected answer and the source passage for each. After import, test those exact questions in the assistant test experience and compare the response with the material. A confident answer is not enough; check that it preserves dates, qualifications, and exceptions.
Suppose the booking guide states that cancellations require notice, but says nothing about rescheduling. A test asking “How do I cancel?” checks direct coverage. “Can I move tomorrow's appointment?” checks whether the assistant invents a procedure that the source does not state. If the answer is unsupported, add or revise approved source material, or define a safe response boundary. Do not treat account connection as a content fix. Keep a record of the question, expected result, observed result, and document version so the next review can reproduce the check.
Maintain the source deliberately
Source selection has an owner after import. Decide who approves changes to the underlying Drive documents, who reviews visible source status, and what events trigger a retest. A change to a cancellation policy is a sensible trigger; a typographic correction may not require the same review. The product provides source management operations, including save, sync, and delete, but the business remains responsible for deciding which document is authoritative and whether an answer is acceptable.
Do not promise that edits in Drive propagate immediately. Check the source's displayed state and last-synced details before planning customer communications around a change. If an important policy has changed, use the documented sync workflow where available, inspect its result, then rerun affected questions. Keep the previous expected answers in the review log long enough to compare what changed. For background on the assistant experience, see the AI chatbot widget.
A reliable connection is a repeatable sequence: authorize the account, choose the right files, confirm the non-empty selection, inspect what the interface reports, and test the answers that depend on those files. Each step has different evidence. Keeping them distinct prevents a connected account from being mistaken for verified knowledge and gives the team a clear response when an answer is missing or stale.