Documentation Grafana Cloud Alerts and IRM IRM Configure Integrations Integration reference Incident integrations Google Workspace

Google Workspace integration for Grafana IRM

The Google Workspace integration for Grafana IRM automates administrative tasks associated with incident response, allowing your team to focus on resolving incidents. This integration automatically links Google Meet meetings and Google Drive files directly to incidents.

Benefits of the Google Workspace integration

• Automatically create Google Meet meetings when incidents are declared
• Generate pre-formatted Google Docs for incident documentation and post-incident reviews
• Populate documents with dynamic incident data using template variables
• Access all incident-related resources directly from the incident details page

Before you begin

To use the Google Workspace integration, you need:

• A Google Workspace account with appropriate permissions
• Authorization to grant Grafana IRM access to Google Calendar and Drive
• Editor or Admin permissions in Grafana IRM

Configure the Google Workspace integration

1. Navigate to IRM > Integrations in the Grafana menu
2. Select the Apps tab
3. Click the Google Workspace tile
4. Click Sign in with Google
5. When redirected to authenticate with Google, enter your credentials for the account you wish to connect

After authentication, the integration will:

• Create a new Google Calendar for incident events
• Create a new Google Drive folder to store incident documents

Links to these resources are provided on the integration details page.

Configure automated actions

After installing the integration, configure actions to automatically create Google Meet meetings and Google Drive documents for each incident.

Create Google Meet meetings automatically

To configure automatic creation of Google Meet meetings:

1. From the Google Workspace integration settings, click Configure Actions
2. For the Create a Google Calendar event with a meeting action, click Add Trigger
3. Set the trigger to When an incident is declared
4. Click Add Action

Once configured, a “Join Google Meet” link will be automatically included in each new incident.

Create Google Drive documents automatically

To configure automatic creation of Google Drive documents:

1. From the Google Workspace integration settings, click Configure Actions
2. For the New Google Doc from template action, click Add Trigger
3. Set the trigger to When an incident is declared
4. Click Add Action

Once configured, an “Open Google Docs” link will be automatically included in each new incident.

Using PIR template variables

Template variables allow you to dynamically populate Google Doc templates with incident data. This is particularly useful for Post-Incident Review (PIR) documents, ensuring they contain accurate incident information.

Add variables to your template

To add template variables to a Google Doc template:

1. Open your template document
2. Insert variables by enclosing them in double curly braces (e.g., {{ incident.title }})
3. Save the template

You can add new variables to a document even after it has been created from a template. Any added variables will be automatically updated as the incident progresses.

Using template variables

When you use a template with variables:

1. The variables are replaced with actual incident data when the document is created
2. As the incident details change, the variables in the document are automatically updated
3. URL variables like {{ incident.slack-url }} or {{ incident.url }} appear as clickable links

Supported variables

The following variables are supported in templates:

Data access

Grafana IRM respects your privacy and only accesses the minimum data necessary to provide the integration functionality:

• The integration only has access to resources (files, calendars, etc.) that it creates
• It cannot access existing Google Drive files or calendar events
• The API is used solely to:
  • Create calendar events for incidents to generate Google Meet sessions
  • Copy and update Google Doc templates for incident documentation