n8n

n8n is a workflow automation platform built around configurable "nodes" that connect to external services. The documentation here focuses on its Google Drive node and HTTP Request node, which together let you automate file storage tasks and call almost any REST API. It targets users and teams who need custom integrations—particularly those comfortable working with cloud services and basic API concepts.

The Google Drive node is a dedicated integration that automates common Drive operations such as creating, moving, sharing, and deleting files, folders, and shared drives. For services without a native node—or for unsupported Google Drive operations—you can use the HTTP Request node to construct arbitrary REST calls. According to the docs, this HTTP node can also be attached to an AI agent within n8n and used as a tool, enabling agent-driven API calls as part of multi-step workflows.

The Google Drive node covers a broad set of operations and is well-documented, including file/folder search and shared drive management. When you hit a limitation—an operation the node doesn't support—the documentation explicitly recommends falling back to the HTTP Request node and reusing the same credentials, which gives you full access to the underlying Google API. There are also ready-made templates showcasing real-world automations, including fully automated AI video generation and publishing, AI video workflows using Google Veo3, and asking questions about PDFs using AI.

The HTTP Request node is powerful but assumes you understand REST APIs, methods, and authentication. You can configure it via parameters or import a curl command, but non-technical users may find this node harder to use. While the docs mention attaching it to an AI agent as a tool, they don’t specify which AI models are used or how data is handled from a privacy perspective—those details will depend on the external AI services you connect. Pricing information for n8n isn’t provided in the referenced content, and this is not a simple personal chat assistant; it’s better suited to builders who want to design and run autonomous, multi-step workflows that interact with external APIs and services.