---
title: "Use Blueprints | Grafana Cloud documentation"
description: "Start a new Grafana Workflow from the Blueprints library and customize it for your team."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Use Blueprints

> Note
> 
> Grafana Workflows is currently in [public preview](/docs/release-life-cycle/). Grafana Labs offers limited support, and breaking changes might occur prior to the feature being made generally available.

Blueprints are prebuilt workflow templates that cover common automation scenarios. Use a blueprint when you want a working starting point instead of building a workflow from scratch.

Each blueprint is a ready-to-edit workflow definition. After you choose one, you customize the name, fill in any team-specific values such as Slack channel IDs, and save it like any other workflow.

## Before you begin

To use Blueprints, you need:

- A Grafana Cloud account with Workflows enabled for your stack
- The integrations the blueprint’s steps use

Check what a blueprint needs before you choose it:

- **Slack**: Blueprints that post to Slack or create Slack channels need Grafana IRM with Slack connected. For details, refer to [Configure Slack for Grafana IRM](/docs/grafana-cloud/alerting-and-irm/irm/integrations/chat-and-collaboration/slack/).
- **Microsoft Teams**: **Microsoft Teams incident bridge**, **Broadcast key updates to Microsoft Teams**, **Announce on-call changes in Microsoft Teams**, and **Weekly incident metrics to Microsoft Teams** need the Grafana IRM Microsoft Teams integration. For details, refer to [Microsoft Teams integration for Grafana IRM](/docs/grafana-cloud/alerting-and-irm/irm/integrations/chat-and-collaboration/ms-teams/).
- **Grafana Assistant**: **AI alert triage**, **Draft post-incident review**, **On-call handoff report**, **Weekly service health summary**, and **Morning operations briefing** need Grafana Assistant in use on your stack.
- **API tokens**: **Annotate dashboards with incidents**, **Create Jira issue for incident follow-ups**, **On-call notification audit**, **Run GitHub Actions remediation**, and **Weekly incident metrics to Microsoft Teams** call an API with a token you store as a workflow secret. For details, refer to [Customize the blueprint](#customize-the-blueprint).
- **Python**: Blueprints that run Python code need no extra setup.

## Open the Blueprints library

The Blueprints library opens in the **Create workflow** dialog box. You can open it from the Workflows home page or from the workflow list.

To open the library from the home page:

1. In Grafana Cloud, open the **Workflows** app.
2. Click **Create workflow**.

To open the library from the workflow list:

1. Go to **Manage workflows**.
2. Click **New workflow**.

The **Create workflow** dialog box opens with the available blueprints. To build a workflow without a blueprint, click **Start from scratch** instead.

## Find the right blueprint

Use the controls at the top of the dialog box to narrow down the list:

- **Category**: Select a category, for example, **Incidents** or **Alerts**.
- **Search**: Enter text in **Search by title** to filter cards by title or description.

Each card shows the blueprint title, a short description of what it does, the trigger type, and the icons of the steps it includes.

## Browse the available blueprints

The library groups blueprints into categories. Use these tables to find a starting point before you open the library.

### Incidents

Incident blueprints react to changes on Grafana IRM incidents, such as a new critical incident, a severity change, or a resolution.

Expand table

| Blueprint                                    | What it does                                                                                                        |
|----------------------------------------------|---------------------------------------------------------------------------------------------------------------------|
| **Major incident kickoff**                   | Creates the incident Slack channel, assigns the on-call commander, posts a help message, and bookmarks the runbook. |
| **Assign commander from schedule**           | Makes the on-call user from your incident commander schedule the commander of new incidents that don’t have one.    |
| **Microsoft Teams incident bridge**          | Opens a Teams meeting for critical incidents and announces it with a join button.                                   |
| **Invite on-call from incident label**       | Invites the labeled team’s on-call engineer when a `team` label is added to an incident.                            |
| **Broadcast key updates to Microsoft Teams** | Shares key updates on critical and major incidents in a Teams channel.                                              |
| **Escalate severity changes**                | Pages leadership when an incident becomes Critical and posts a heads-up for Major.                                  |
| **Enforce severity before resolve**          | Reopens incidents that are resolved while their severity is still Pending.                                          |
| **Require incident fields on resolve**       | Nudges the team to fill in required custom fields and labels after resolution.                                      |
| **Draft post-incident review**               | Uses Grafana Assistant to draft a review as a Grafana Notebook and shares an executive summary with the link.       |
| **Archive incident channel after resolve**   | Archives the incident Slack channel a day after resolution.                                                         |

### On-call

On-call blueprints react to rotation changes on Grafana IRM schedules.

Expand table

| Blueprint                                       | What it does                                                                                     |
|-------------------------------------------------|--------------------------------------------------------------------------------------------------|
| **On-call handoff report**                      | Uses Grafana Assistant to write a handoff report from the past week and posts it to Slack.       |
| **Welcome the incoming on-call**                | Sends a Slack direct message to whoever just went on call.                                       |
| **Announce on-call changes in Microsoft Teams** | Posts who is now on call to a Teams channel.                                                     |
| **On-call notification audit**                  | Reports who has no verified phone number, or important notification rules that can’t reach them. |

### Alerts

Alert blueprints react to new Grafana IRM alert groups.

Expand table

| Blueprint                                 | What it does                                                                                |
|-------------------------------------------|---------------------------------------------------------------------------------------------|
| **Declare incident for critical alerts**  | Declares an incident when an alert group has a `severity=critical` label.                   |
| **AI alert triage**                       | Uses Grafana Assistant to investigate new alert groups and escalates when needed.           |
| **Route alerts to team channels**         | Posts each alert group to the Slack channel of the team that owns it.                       |
| **Invite on-call from alert group label** | Invites the labeled team’s on-call engineer when a `team` label is added to an alert group. |

### Reports

Report blueprints run on a schedule and post summaries.

Expand table

| Blueprint                                      | What it does                                                                                      |
|------------------------------------------------|---------------------------------------------------------------------------------------------------|
| **Weekly service health summary**              | Uses Grafana Assistant to review the health of your services every Friday.                        |
| **Weekly incident metrics to Microsoft Teams** | Computes incident counts and time to resolve, then posts a scorecard to Teams.                    |
| **Morning operations briefing**                | Uses Grafana Assistant to post active incidents and firing alerts to Slack every weekday morning. |

### Integrations

Integration blueprints connect Workflows to other tools with the HTTP call step.

Expand table

| Blueprint                                     | What it does                                                                                         |
|-----------------------------------------------|------------------------------------------------------------------------------------------------------|
| **Annotate dashboards with incidents**        | Adds an annotation that spans each resolved incident to your Grafana dashboards.                     |
| **Create Jira issue for incident follow-ups** | Opens a Jira issue for follow-up work and links it on the incident.                                  |
| **Run GitHub Actions remediation**            | Starts a GitHub Actions workflow you choose when an alert group labeled `auto_remediate=true` fires. |
| **Vendor status page watch**                  | Posts to Slack when a vendor opens an incident on their status page.                                 |

### Basics

Basics blueprints are runnable examples that need no setup. Use them to learn how workflows work.

Expand table

| Blueprint                            | What it does                                                                         |
|--------------------------------------|--------------------------------------------------------------------------------------|
| **Learn: expressions and branching** | Shows CEL expressions, step outputs, switch branches, and filters.                   |
| **Learn: shape data with Python**    | Shows how the Python step reads the workflow context and passes JSON to later steps. |

## Create a workflow from a blueprint

Select a card in the **Create workflow** dialog box.

The editor opens with the blueprint’s steps already filled in, in an unsaved workflow named “Blueprint: *BLUEPRINT\_TITLE*”. To rename it, click the workflow title. Workflows gives the workflow a random unique ID the first time you save it. The workflow is disabled by default so you can finish customizing it before it runs.

## Customize the blueprint

Most blueprints leave one or more inputs empty for you to fill in. For example, a Slack-based blueprint expects you to pick the channel, and an on-call blueprint expects you to set the IRM schedule name.

Blueprints that call an external API, such as Jira, GitHub, or the Grafana HTTP API, reference a workflow secret by name, for example, `grafana-api-token`. Create a secret with that name before you run the workflow. For details, refer to [Manage secrets](/docs/grafana-cloud/platform/workflows/manage-secrets).

To customize a blueprint:

1. Select each step in the workflow tree to open its configuration panel.
2. Update the inputs that are empty or contain placeholder values.
3. Adjust any condition strings, message templates, or wait durations to match your team’s process.
4. Click **Save**. If the workflow has no folder yet, choose one in the **Select a folder** dialog box.
5. Turn on **Enable**, then click **Save** again.
6. Click **Run** in the editor header to test the workflow with a sample event. For details, refer to [Configure triggers](/docs/grafana-cloud/platform/workflows/configure-triggers/#trigger-workflows-manually).

After it’s saved and enabled, the workflow also runs automatically when its trigger conditions are met.

For details on the editor, refer to [Create workflows](/docs/grafana-cloud/platform/workflows/create-workflows).

## Next steps

- [Get started with Grafana Workflows](/docs/grafana-cloud/platform/workflows/get-started)
- [Create workflows](/docs/grafana-cloud/platform/workflows/create-workflows)
- [Configure triggers](/docs/grafana-cloud/platform/workflows/configure-triggers)
- [Use CEL expressions](/docs/grafana-cloud/platform/workflows/use-expressions)
- [Step and trigger types reference](/docs/grafana-cloud/platform/workflows/reference)