Google Drive n8n templates

Yes - Google Drive is a first-party n8n node, so you authenticate once and the operations are available as dropdowns rather than raw API calls. 1,085 of our templates use it, across Document Processing, Email Automation, AI Agents and Workflow Utility / Tooling.

The 1,085 Google Drive templates here cluster into Document Processing, Email Automation, AI Agents and Workflow Utility / Tooling. In practice that means moving records in and out of Google Drive on a schedule, reacting to changes the moment they happen, and syncing it against the other tools in your stack so the same data does not get maintained twice.

No. These are finished workflows, not starting points - nodes, connections and field mappings are already built. You import the JSON, connect your Google Drive account, and run it.

The most common trigger types here are scheduled (780), webhook (236) and form (67), with 2 on other trigger types. Scheduled workflows poll on an interval you set, webhook workflows fire the moment the source app calls n8n, and form workflows expose a hosted form that starts the run on submit. You can swap the trigger on any template after importing it - the rest of the workflow does not care what started it.

Individual templates start at ₹49 and you download the JSON immediately after payment. 7 of these are free to download with no account. If you need more than two or three, a category bundle works out cheaper per template, and the full-library tier covers every template on the site - these 1,085 included.

Both. Each template is a plain n8n workflow JSON file, imported with Workflows → Import from File, so it runs anywhere n8n runs - n8n Cloud, Docker, or a npm install on your own server. Self-hosted instances need outbound network access to the APIs the workflow calls, which is the only difference worth planning for.