Productivity · 16 pre-built actions
Google Drive integration with Nexus
Make Google Drive part of governed document processes. Create, read, update, delete, list, copy, move, download, restore and search files and folders, and manage sharing, inside recorded workflows.
Pre-built actions
What you can automate
16 pre-built Google Drive actions, grouped by what they work on.
16
PRE-BUILT ACTIONS
- 01File and folder actions create, update, copy, move, restore and delete content.
- 02Sharing and permissions actions share, unshare and set access.
- 03Search and list actions find the documents a step needs.
Workflow
How it fits into a Nexus workflow
Google Drive steps run as pre-built actions. A run that uses them starts from a webhook, a schedule, a request in Nexus or another system's trigger source.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Call the Google Drive API with the HTTP Request node, or use GraphQL, SOAP or a database node where the system exposes one.
02
Write custom integration logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the libraries your team already uses.
03
Direct calls and code use the same vault-backed secrets, approvals, run history and audit as pre-built actions.
Examples
Workflow examples
Document intake
A new file is read, validated and filed, with exceptions routed to a person.
Access with approval
Sharing outside the organisation pauses for the data owner.
Offboarding file handover
A leaver's files are moved to the manager and sharing is removed.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
FAQ
Google Drive connector questions
- Which Google Drive actions are pre-built?
- Nexus includes 16 pre-built Google Drive actions across Files, Folders, Sharing and permissions and Search.
- Can Google Drive start a workflow?
- Runs that use Google Drive start from a webhook, a schedule or another trigger source. Google Drive steps run as actions inside the workflow.
- What if the operation I need is not pre-built?
- Use the Google Drive API through the HTTP Request node, or write the step in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript. It runs in the same workflow with the same approvals and audit.
Related reading
Continue from here
- Microsoft 365 connector
Teams, email and calendar.
- Gmail connector
Email, drafts, labels and threads.
- Human-in-the-loop
Where approval belongs in a running workflow.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how Google Drive fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.