Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationAI systemIntermediate

AI-Powered Google Drive Assistant

AI-Powered Google Drive Assistant is a 8-node automation blueprint connecting Google Drive, OpenAI, @n8n/n8n-nodes-langchain. Inspect its trigger, execution graph, branches, and implementation requirements.

Google DriveOpenAI@n8n/n8n-nodes-langchain

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

8

Nodes

6

Links

2

Run groups

Connected tools

3 integrations

  • Google Drive
  • OpenAI
  • LangChain

Canvas controls

Fit wide systems, then zoom into any run group.

AI-Powered Google Drive Assistant execution lanes2 run groups containing 8 workflow nodes and 6 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.When clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 2 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 2 OUTOpenAI. OpenAI node, openAi. 1 incoming and 0 outgoing connections.STEP 02OpenAIOPENAIOPENAI1 IN / 0 OUTGoogle Drive. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 02Google DriveGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTOpenAI2. OpenAI node, openAi. 1 incoming and 1 outgoing connections.STEP 03OpenAI2OPENAIOPENAI1 IN / 1 OUTOpenAI1. OpenAI node, openAi. 1 incoming and 0 outgoing connections.OUTCOMEOpenAI1OPENAIOPENAI1 IN / 0 OUTWhen chat message received. trigger node, chatTrigger. 0 incoming and 1 outgoing connections.STARTWhen chat message receivedTRIGGERCHATTRIGGER0 IN / 1 OUTOpenAI Assistent. OpenAI node, openAi. 2 incoming and 0 outgoing connections.OUTCOMEOpenAI AssistentOPENAIOPENAI2 IN / 0 OUTWindow Buffer Memory. ai node, memoryBufferWindow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Window Buffer MemoryAIMEMORYBUFFERWINDOW0 IN / 1 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.8 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

When clicking ‘Test workflow’

4 Execution Links

  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    OpenAI

    AI reasoning

    Google Drive

    Integration

  3. Step 3

    OpenAI2

    AI reasoning

  4. Outcome

    OpenAI1

    AI reasoning

02

Run Group

When chat message received

1 Execution Link1 Support Dependency

  1. Start

    When chat message received

    Trigger

  2. Outcome

    OpenAI Assistent

    AI reasoning

Attached dependencies

These nodes support the runtime above; they are not additional starts or outcomes.

1 node

  • Window Buffer Memory

    AI reasoning dependency

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.

Create a build planReturn to the atlas