Skip to main content
Rootly’s Google Meet integration leverages workflows to automatically create meeting rooms when incidents occur. If you are unfamiliar with how Workflows function, please visit our Workflows documentation first.

​
Automation Options

You can automate Google Meet room creation in two ways:

Auto-Create Incident Call

Automatically create a Google Meet room at incident start using built-in settings — no workflow required.

Custom Workflow

Use workflows for conditional or advanced meeting automation with full control over triggers and actions.

​
Option 1: Auto-Create Incident Call

The Auto-Create Incident Call panel lets you automatically generate a Google Meet room whenever an incident begins, without building a workflow from scratch.
Auto-Create Incident Call panel in Rootly
It includes a full set of configuration options so you can control how the room is created, where it’s shared, and what Google Meet features are enabled. These settings let you control exactly how Google Meet call meetings behave during incidents.
Automatically spin up a meeting the moment an incident opens.
Toggle for creating Google Meet call on incident start
Add the meeting link as a bookmark in the incident’s Slack channel.
Toggle for bookmarking Google Meet call in Slack
Announce new incident calls in specific Slack channels.
Slack channel notification settings for Google Meet
Enable AI-powered recording, transcription, and summary generation.
Meeting transcript and summary settings
Use Auto-Create when you want instant, zero-configuration Google Meet automation. Build a custom workflow when you need conditions, multiple actions, or advanced routing logic.

​
Option 2: Creating a Custom Workflow

For teams that need conditional logic — such as only creating calls for SEV-1 incidents or specific teams — a custom workflow gives you full control.
1

Open Workflows

Go to Rootly → Workflows → Create Workflow.
Rootly workflows page
Create workflow button
2

Choose Workflow Type

Select your workflow type — typically Incident for meeting automation.
Workflow type selection showing Incident, Retrospective, and Pulse options
3

Configure Triggers

Triggers define when this workflow should run. Choose the event that should kick off your Google Meet room creation.
Workflow trigger configuration options
4

Add Conditions (Optional)

Conditions control when the workflow should or shouldn’t run after being triggered. Use conditions to narrow the scope of your automation.
Workflow conditions panel showing filter options
Examples:
  • Severity-based — Only create calls for SEV-1 or SEV-2 incidents
  • Team or service filters — Only for incidents impacting specific teams
  • Incident type filtering — Only when the incident kind is set to Incident (not Maintenance)
5

Add Google Meet Action

Click Add Action → Google Meet → Create Room. Configure the action settings that appear.
Add action button in workflow editor
Google Meet Create room action in action picker
Google Meet action configuration with AI Meeting Capture option
Enable AI Meeting Capture to have Rootly AI automatically capture and summarize the meeting.
6

Save the Workflow

Click Add, give your workflow a descriptive name, and click Create Workflow.

​
Variable Reference

Use these variables in workflow notifications, Slack messages, and calendar event templates.

​
Google Meet Variables

​
Incident Variables

Use the Liquid Variable Explorer to test variables with real incident data before using them in production.

​
Example Templates

Include the Google Meet link in a Slack message automatically when an incident is created:

​
Frequently Asked Questions

Each incident is associated with one Google Meet room by default. If you need additional rooms, you can create sub-incidents and configure workflows to create separate rooms for each sub-incident.
Rootly does not automatically end or delete the Google Meet room when an incident is resolved. The room remains accessible through the meeting link until it expires naturally per Google Meet’s settings.
Yes. The workflow actions work the same regardless of which connection method you used during installation. The integration handles authentication transparently.