← All N8N workflows
Messaging & emailEmail SendGoogle Drive Trigger

receive google drive events and email send

Configured with Email Send, Google Drive Trigger. Review the connections and setup before adapting this template.

Workflow preview
TriggerGoogle Drive TriggerGoogle Drive TriggerMessagingSend EmailEmail Send

Node categories in this workflow

  • Trigger
  • Messaging

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.

Workflow node names, types, and operations
NodeCategoryTypeOperation
Google Drive TriggerTriggerGoogle Drive TriggerSee node parameters
Send EmailMessagingEmail SendSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. 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

  • googleDriveOAuth2Api
  • smtp

Workflow notes

receive google drive events and email send

receive google drive events and email send

Purpose and structure

This folder contains the receive google drive events and email send workflow. Its executable nodes use emailSend, googleDriveTrigger. 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

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/Emailsend/0113_Emailsend_GoogleDrive_Send_Triggered.json MIT; preserve source notices.

More in Messaging & email