Communications · 15 pre-built actions
Google Workspace (Gmail) integration with Nexus
Send, label and track Gmail as governed steps. Email, draft, label and thread actions, including batch delete, let mail take part in workflows with approval where policy requires.
Pre-built actions
What you can automate
15 pre-built Google Workspace (Gmail) actions, grouped by what they work on.
15
PRE-BUILT ACTIONS
- 01Email and Drafts actions send messages or prepare them for review.
- 02Labels and Threads actions organise and track conversations.
- 03Batch delete supports retention steps.
Workflow
How it fits into a Nexus workflow
Google Workspace (Gmail) 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 Workspace (Gmail) 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
Drafts for human review
A workflow prepares a draft reply that a person reviews before sending.
Labelled intake
Labelled messages are processed and the outcome is recorded.
Notification on approval
An approved request sends a confirmation to the requester.
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 Workspace (Gmail) connector questions
- Which Google Workspace (Gmail) actions are pre-built?
- Nexus includes 15 pre-built Google Workspace (Gmail) actions across Email, Drafts, Labels and Threads.
- Can Google Workspace (Gmail) start a workflow?
- Runs that use Google Workspace (Gmail) start from a webhook, a schedule or another trigger source. Google Workspace (Gmail) steps run as actions inside the workflow.
- What if the operation I need is not pre-built?
- Use the Google Workspace (Gmail) 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.
- Google Calendar connector
Calendars, events and attendees.
- 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 Workspace (Gmail) 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.