Compliance Document Workflow with Google Drive

Get KYC packets and contracts out of Google Drive and into review without re-keying. Import files as knowledge, use your own Drive in chat, or pass link-shared files to a Jinba Flow workflow.

Book a Demo
  1. Drive link submitted A reviewer passes in the file's link
  2. Extract the fields Pull structured data from the document
  3. Completeness check Flag what is missing before review
  4. Reviewer sign-off Owner approves or sends it back
  5. Record the outcome Output kept in the run history

What you can do with Google Drive + Jinba

  • Import Drive Files as Knowledge

    Browse or search My Drive and add files to Jinba App's knowledge base. Google Docs, Sheets and Slides arrive as Word, Excel and PowerPoint files, and Re-fetch pulls in the latest version when a file changes.

  • Your Own Drive, in Chat

    Connect your Google account and ask the AI to work with your Drive files in chat. Only you can use the connection, and its token is never passed to the AI.

  • Hand Files to a Governed Workflow

    A Drive file enters a Jinba Flow workflow through its link, so it must be shared by link; keep sensitive files on the import or chat path. Runs start from chat, a form, a schedule or an API call.

  • Review Before Anything Moves On

    Add an approval step and the workflow run pauses until a reviewer approves or rejects it, with a comment when the workflow requires one. The decision is made right in the chat or the run console.

How teams use it

Review KYC Files from Drive in Chat

Import a customer's KYC files from Drive into Jinba App, ask the AI to check them against your checklist, and run your team's published review workflow from the same chat.

Contract Intake by Link

Pass a contract's Drive link to a Jinba Flow workflow that extracts key clauses, classifies the document and routes it for approval. Use this path for documents your policy allows to be shared by link.

A Policy Library the AI Can Reference

Import policy and procedure documents from Drive into knowledge so answers in chat draw on your own rules, and use Re-fetch to pick up each revision.

Frequently Asked Questions

Everything you need to know about Jinba. Can't find the answer you're looking for? Reach out to our support team.

Can a workflow start automatically when a file lands in a Google Drive folder?

No. Jinba has no Google Drive folder trigger. A Jinba Flow run starts from chat, a form, a schedule or an API call, and a Drive file reaches the workflow through its link.

Does a Drive file have to be shared by link for a workflow to read it?

For Jinba Flow, yes: the workflow fetches the file from its link, so the link has to open without signing in. For sensitive files such as KYC documents, import them into Jinba App's knowledge base or use your own Drive connection in chat instead, where you sign in with your own Google account.

Who can use my Google Drive connection?

Only you. The connection uses your own Google account, other members of your workspace cannot reach your Drive through it, and the token is stored encrypted and never passed to the AI. You can disconnect at any time.

What happens to Google Docs, Sheets and Slides when I import them?

They arrive as Word, Excel and PowerPoint files, and Google Drawings arrive as PDF. Other Google-native formats cannot be imported, each file can be up to 25 MB, and Re-fetch pulls in the latest version.

Is there a record of what a workflow did with a file?

Yes. Every Jinba Flow run is kept in its run history with the inputs it received and the outputs it produced, and an approval step pauses the run until a reviewer decides.

Bring Google Drive into Your Review Process

Talk to our team about getting Drive documents into governed review workflows for your bank, insurer, or compliance-heavy organization.

Book a Demo