Productivity · 15 pre-built actions
Google Calendar integration with Nexus
Schedule and track events as part of a workflow. Calendar and event operations, attendee management and event watching let scheduling happen inside governed processes.
Pre-built actions
What you can automate
15 pre-built Google Calendar actions, grouped by what they work on.
15
PRE-BUILT ACTIONS
- 01Events and Calendars actions create and update meetings.
- 02Attendees actions add and remove participants.
- 03Event watch actions start and stop watching for event changes.
Workflow
How it fits into a Nexus workflow
Google Calendar 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 Calendar 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
Onboarding schedule
A new starter receives the induction meetings their role requires.
Change window booking
An approved change books the maintenance window and invites the operators.
Offboarding cleanup
Future events owned by a leaver are reassigned or cancelled.
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 Calendar connector questions
- Which Google Calendar actions are pre-built?
- Nexus includes 15 pre-built Google Calendar actions across Calendars, Events, Attendees and Event watch.
- Can Google Calendar start a workflow?
- Runs that use Google Calendar start from a webhook, a schedule or another trigger source. Google Calendar steps run as actions inside the workflow.
- What if the operation I need is not pre-built?
- Use the Google Calendar 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 Drive connector
Files, folders and sharing.
- Workday connector
Employee, payroll and recruitment actions.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how Google Calendar 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.