Replace Google Drive connection
Configured with Airtable, Google Drive, Google Drive Trigger, HTTP Request, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Files / media
- Web / API
- Trigger
- Data store
- Transform
- Code
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Google Drive | Files / media | Google Drive | download |
| Upload File | Web / API | HTTP Request | POST |
| Google Drive Trigger | Trigger | Google Drive Trigger | See node parameters |
| Create Invoice | Data store | Airtable | create |
| Create Line Item | Data store | Airtable | create |
| OpenAI - Extract Line Items | Web / API | HTTP Request | POST |
| Set Fields | Transform | Edit Fields | See node parameters |
| Process Line Items | Code | Code | See node parameters |
| Webhook | Trigger | Webhook | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
airtableTokenApigoogleDriveOAuth2ApiopenAiApi
Workflow notes
AI Agent for realtime insights on meetings
AI Agent for realtime insights on meetings
Made by Mark Shcherbakov from community 5minAI
Transcribing meetings manually can be tedious and prone to error. This workflow automates the transcription process in real-time, ensuring that key discussions and decisions are accurately captured and easily accessible for later review, thus enhancing productivity and clarity in communications.
The workflow leverages n8n and LlamaParse to automatically detect new invoices in a designated Google Drive folder, parse essential billing details, and store the extracted data in a structured format. The key functionalities include:
- Real-time detection of new invoices via Google Drive triggers.
- Automated HTTP requests to initiate parsing through Lama Cloud.
- Structured storage of invoice details and line items in a database for future reference.
- Google Drive Integration: Monitors a specific folder in Google Drive for new invoice uploads.
- Parsing with LlamaParse: Automatically sends invoices for parsing and processes results through webhooks.
- Data Storage in Airtable: Creates records for invoices and their associated line items, allowing for detailed tracking.
Set up steps
Set up steps
-
Google Drive Trigger:
- Set up a trigger to detect new files in a specified folder dedicated to invoices.
-
File Upload to LlamaParse:
- Create an HTTP request that sends the invoice file to LlamaParse for parsing, including relevant header settings and webhook URL.
-
Webhook Processing:
- Establish a webhook node to handle parsed results from LlamaParse, extracting needed invoice details effectively.
-
Invoice Record Creation:
- Create initial records for invoices in your database using the parsed details received from the webhook.
-
Line Item Processing:
- Transform string data into structured line item arrays and create individual records for each item linked to the main invoice.
Replace Google Drive connection
Replace Google Drive connection
Purpose and structure
This folder contains the Replace Google Drive connection workflow. Its executable nodes use airtable, code, googleDrive, googleDriveTrigger, httpRequest, set, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Google Drive Trigger, Webhook
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Code/0669_Code_Webhook_Create_Webhook.json MIT; preserve source notices.
Canvas section labels
These name areas of the original canvas; they do not include explanatory instructions.
- Scenario 1
- Scenario 2
- Replace Google Drive connection
- Replace API key in header
- Replace OpenAI connection
- Replace Airtable connection