Get a detailed overview of this resourceList the top 5 use cases for this resourceBuild a program using gcp.monitoring.NotificationChannelRepository[Google Cloud (GCP) Classic pulumi/pulumi-gcp](https://github.com/pulumi/pulumi-gcp)LicenseApache-2.0NotesThis Pulumi package is based on the [`google-beta` Terraform Provider](https://github.com/hashicorp/terraform-provider-google-beta).

1. [Packages](/content/registry/index.html)
2. [Packages](/content/registry/packages/index.html)
3. [Google Cloud (GCP) Classic](/content/registry/packages/gcp/index.html)
4. [API Docs](/content/registry/packages/gcp/api-docs/index.html)
5. [monitoring](/content/registry/packages/gcp/api-docs/monitoring/index.html)
6. [NotificationChannel](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/index.html)

Google Cloud v9.26.0, Jun 9 26

Google Cloud v9.26.0, Jun 9 26

Viewing docs for Google Cloud v9.26.0

published on Tuesday, Jun 9, 2026 by Pulumi

[Schema (JSON)](/content/registry/packages/gcp/schema.json)

[pulumi/pulumi-gcp](https://github.com/pulumi/pulumi-gcp)

v9.26.0 (9.x, latest)v8.41.1 (8.x)v7.38.0 (7.x)

# gcp.monitoring.NotificationChannel [Anchor](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/\#gcp-monitoring-notificationchannel/index.html)

Explore with Neo

[Explain this resource](https://app.pulumi.com/neo?prompt=Explain+the+resource+gcp.monitoring.NotificationChannel.+Provide+a+detailed+overview+of+its+purpose%2C+architecture%2C+and+typical+responsibilities.&prefer_signup=true) [Show real-world scenarios](https://app.pulumi.com/neo?prompt=List+the+top+five+real-world+scenarios+where+gcp.monitoring.NotificationChannel+delivers+the+most+value.+Describe+why+it+is+useful+for+each.&prefer_signup=true) [Provision a new instance](https://app.pulumi.com/neo?prompt=Generate+a+Pulumi+program+that+provisions+gcp.monitoring.NotificationChannel.+Include+any+required+configuration+and+showcase+best+practices.&prefer_signup=true)

Viewing docs for Google Cloud v9.26.0

published on Tuesday, Jun 9, 2026 by Pulumi

[Schema (JSON)](/content/registry/packages/gcp/schema.json)

[pulumi/pulumi-gcp](https://github.com/pulumi/pulumi-gcp)

v9.26.0 (9.x, latest)v8.41.1 (8.x)v7.38.0 (7.x)

## On this page

## On this page

- [Example Usage](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#example-usage/index.html)
- [Notification Channel Basic](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#notification-channel-basic/index.html)
- [Notification Channel Sensitive](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#notification-channel-sensitive/index.html)
- [Create NotificationChannel Resource](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#create/index.html)
- [Constructor syntax](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#constructor-syntax/index.html)
- [Constructor example](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#constructor-example/index.html)
- [NotificationChannel Resource Properties](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#properties/index.html)
- [Inputs](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#inputs/index.html)
- [Outputs](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#outputs/index.html)
- [Look up Existing NotificationChannel Resource](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#look-up/index.html)
- [Supporting Types](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#supporting-types/index.html)
- [Import](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#import/index.html)
- [Package Details](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#package-details/index.html)

* * *

Related Resources

[monitoring.AlertPolicy](/content/registry/packages/gcp/api-docs/monitoring/alertpolicy/index.html)

[billing.Budget](/content/registry/packages/gcp/api-docs/billing/budget/index.html)

[secretmanager.SecretIamBinding](/content/registry/packages/gcp/api-docs/secretmanager/secretiambinding/index.html)

[organizations.Project](/content/registry/packages/gcp/api-docs/organizations/project/index.html)

[projects.Service](/content/registry/packages/gcp/api-docs/projects/service/index.html)

- Copy Page

- [Request a Change](https://github.com/pulumi/registry/issues/new?body=File:%20[themes%2fdefault%2fcontent/%2fregistry%2fpackages%2fgcp%2fapi-docs%2fmonitoring%2fnotificationchannel](https%3a%2f%2fwww.pulumi.com%2fregistry%2fpackages%2fgcp%2fapi-docs%2fmonitoring%2fnotificationchannel%2f))

[Scroll to top](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/# "Scroll to top"/index.html)

A NotificationChannel is a medium through which an alert is delivered
when a policy violation is detected. Examples of channels include email, SMS,
and third-party messaging applications. Fields containing sensitive information
like authentication tokens or contact info are only partially populated on retrieval.

Notification Channels are designed to be flexible and are made up of a supported `type`
and labels to configure that channel. Each `type` has specific labels that need to be
present for that channel to be correctly configured. The labels that are required to be
present for one channel `type` are often different than those required for another.
Due to these loose constraints it’s often best to set up a channel through the UI
and import it to the provider when setting up a brand new channel type to determine which
labels are required.

A list of supported channels per project the `list` endpoint can be
accessed programmatically or through the api explorer at https://cloud.google.com/monitoring/api/ref\_v3/rest/v3/projects.notificationChannelDescriptors/list .
This provides the channel type and all of the required labels that must be passed.

To get more information about NotificationChannel, see:

- [API documentation](https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.notificationChannels)
- How-to Guides
  - [Monitoring API Documentation](https://cloud.google.com/monitoring/api/v3/)
  - [Notification Options](https://cloud.google.com/monitoring/support/notification-options)

> **Note:** All arguments marked as write-only values will not be stored in the state: `sensitive_labels.auth_token_wo`, `sensitive_labels.password_wo`, `sensitive_labels.service_key_wo`.
> Read more about Write-only Arguments.

## Example Usage [Anchor](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/\#example-usage/index.html)

### Notification Channel Basic [Anchor](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/\#notification-channel-basic/index.html)

- TypeScript
- Python
- Go
- C#
- Java
- YAML
- HCL PREVIEW

```typescript
import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";

const basic = new gcp.monitoring.NotificationChannel("basic", {
    displayName: "Test Notification Channel",
    type: "email",
    labels: {
        email_address: "fake_email@blahblah.com",
    },
    forceDelete: false,
});
```

Copy

```python
import pulumi
import pulumi_gcp as gcp

basic = gcp.monitoring.NotificationChannel("basic",
    display_name="Test Notification Channel",
    type="email",
    labels={
        "email_address": "fake_email@blahblah.com",
    },
    force_delete=False)
```

Copy

```go
package main

import (
	"github.com/pulumi/pulumi-gcp/sdk/v9/go/gcp/monitoring"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := monitoring.NewNotificationChannel(ctx, "basic", &monitoring.NotificationChannelArgs{
			DisplayName: pulumi.String("Test Notification Channel"),
			Type:        pulumi.String("email"),
			Labels: pulumi.StringMap{
				"email_address": pulumi.String("fake_email@blahblah.com"),
			},
			ForceDelete: pulumi.Bool(false),
		})
		if err != nil {
			return err
		}
		return nil
	})
}
```

Copy

```csharp
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Gcp = Pulumi.Gcp;

return await Deployment.RunAsync(() =>
{
    var basic = new Gcp.Monitoring.NotificationChannel("basic", new()
    {
        DisplayName = "Test Notification Channel",
        Type = "email",
        Labels =
        {
            { "email_address", "fake_email@blahblah.com" },
        },
        ForceDelete = false,
    });

});
```

Copy

```java
package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.gcp.monitoring.NotificationChannel;
import com.pulumi.gcp.monitoring.NotificationChannelArgs;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

public static void stack(Context ctx) {
        var basic = new NotificationChannel("basic", NotificationChannelArgs.builder()
            .displayName("Test Notification Channel")
            .type("email")
            .labels(Map.of("email_address", "fake_email@blahblah.com"))
            .forceDelete(false)
            .build());

}
}
```

Copy

```yaml
resources:
  basic:
    type: gcp:monitoring:NotificationChannel
    properties:
      displayName: Test Notification Channel
      type: email
      labels:
        email_address: fake_email@blahblah.com
      forceDelete: false
```

Copy

```hcl
pulumi {
  required_providers {
    gcp = {
      source = "pulumi/gcp"
    }
  }
}

resource "gcp_monitoring_notificationchannel" "basic" {
  display_name = "Test Notification Channel"
  type         = "email"
  labels = {
    "email_address" = "fake_email@blahblah.com"
  }
  force_delete = false
}
```

Copy

### Notification Channel Sensitive [Anchor](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/\#notification-channel-sensitive/index.html)

- TypeScript
- Python
- Go
- C#
- Java
- YAML
- HCL PREVIEW

```typescript
import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";

const _default = new gcp.monitoring.NotificationChannel("default", {
    displayName: "Test Slack Channel",
    type: "slack",
    labels: {
        channel_name: "#foobar",
    },
    sensitiveLabels: {
        authToken: "one",
    },
});
```

Copy

```python
import pulumi
import pulumi_gcp as gcp

default = gcp.monitoring.NotificationChannel("default",
    display_name="Test Slack Channel",
    type="slack",
    labels={
        "channel_name": "#foobar",
    },
    sensitive_labels={
        "auth_token": "one",
    })
```

Copy

```go
package main

import (
	"github.com/pulumi/pulumi-gcp/sdk/v9/go/gcp/monitoring"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := monitoring.NewNotificationChannel(ctx, "default", &monitoring.NotificationChannelArgs{
			DisplayName: pulumi.String("Test Slack Channel"),
			Type:        pulumi.String("slack"),
			Labels: pulumi.StringMap{
				"channel_name": pulumi.String("#foobar"),
			},
			SensitiveLabels: &monitoring.NotificationChannelSensitiveLabelsArgs{
				AuthToken: pulumi.String("one"),
			},
		})
		if err != nil {
			return err
		}
		return nil
	})
}
```

Copy

```csharp
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Gcp = Pulumi.Gcp;

return await Deployment.RunAsync(() =>
{
    var @default = new Gcp.Monitoring.NotificationChannel("default", new()
    {
        DisplayName = "Test Slack Channel",
        Type = "slack",
        Labels =
        {
            { "channel_name", "#foobar" },
        },
        SensitiveLabels = new Gcp.Monitoring.Inputs.NotificationChannelSensitiveLabelsArgs
        {
            AuthToken = "one",
        },
    });

});
```

Copy

```java
package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.gcp.monitoring.NotificationChannel;
import com.pulumi.gcp.monitoring.NotificationChannelArgs;
import com.pulumi.gcp.monitoring.inputs.NotificationChannelSensitiveLabelsArgs;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

public static void stack(Context ctx) {
        var default_ = new NotificationChannel("default", NotificationChannelArgs.builder()
            .displayName("Test Slack Channel")
            .type("slack")
            .labels(Map.of("channel_name", "#foobar"))
            .sensitiveLabels(NotificationChannelSensitiveLabelsArgs.builder()
                .authToken("one")
                .build())
            .build());

}
}
```

Copy

```yaml
resources:
  default:
    type: gcp:monitoring:NotificationChannel
    properties:
      displayName: Test Slack Channel
      type: slack
      labels:
        channel_name: '#foobar'
      sensitiveLabels:
        authToken: one
```

Copy

```hcl
pulumi {
  required_providers {
    gcp = {
      source = "pulumi/gcp"
    }
  }
}

resource "gcp_monitoring_notificationchannel" "default" {
  display_name = "Test Slack Channel"
  type         = "slack"
  labels = {
    "channel_name" = "#foobar"
  }
  sensitive_labels = {
    auth_token = "one"
  }
}
```

Copy

## Create NotificationChannel Resource [Anchor](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/\#create/index.html)

Resources are created with functions called constructors. To learn more about declaring and configuring resources, see [Resources](/content/docs/concepts/resources/index.html).

### Constructor syntax [Anchor](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/\#constructor-syntax/index.html)

- TypeScript
- Python
- Go
- C#
- Java
- YAML
- HCL PREVIEW

```typescript
new NotificationChannel(name: string, args: NotificationChannelArgs, opts?: CustomResourceOptions);
```

```python
@overload
def NotificationChannel(resource_name: str,
                        args: NotificationChannelArgs,
                        opts: Optional[ResourceOptions] = None)

@overload
def NotificationChannel(resource_name: str,
                        opts: Optional[ResourceOptions] = None,
                        type: Optional[str] = None,
                        deletion_policy: Optional[str] = None,
                        description: Optional[str] = None,
                        display_name: Optional[str] = None,
                        enabled: Optional[bool] = None,
                        force_delete: Optional[bool] = None,
                        labels: Optional[Mapping[str, str]] = None,
                        project: Optional[str] = None,
                        sensitive_labels: Optional[NotificationChannelSensitiveLabelsArgs] = None,
                        user_labels: Optional[Mapping[str, str]] = None)
```

```go
func NewNotificationChannel(ctx *Context, name string, args NotificationChannelArgs, opts ...ResourceOption) (*NotificationChannel, error)
```

```csharp
public NotificationChannel(string name, NotificationChannelArgs args, CustomResourceOptions? opts = null)
```

```java
public NotificationChannel(String name, NotificationChannelArgs args)
public NotificationChannel(String name, NotificationChannelArgs args, CustomResourceOptions options)
```

```yaml
type: gcp:monitoring:NotificationChannel
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
```

```hcl
resource "gcp_monitoring_notificationchannel" "name" {
    # resource properties
}
```

#### Parameters [Anchor](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/\#parameters/index.html)

nameThis property is required.stringThe unique name of the resource.argsThis property is required.[NotificationChannelArgs](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#inputs/index.html)The arguments to resource properties.opts[CustomResourceOptions](/content/docs/reference/pkg/nodejs/pulumi/pulumi/#CustomResourceOptions/index.html)Bag of options to control resource's behavior.

resource\_nameThis property is required.strThe unique name of the resource.argsThis property is required.[NotificationChannelArgs](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#inputs/index.html)The arguments to resource properties.opts[ResourceOptions](/content/docs/reference/pkg/python/pulumi/#pulumi.ResourceOptions)Bag of options to control resource's behavior.

ctx[Context](https://pkg.go.dev/github.com/pulumi/pulumi/sdk/v3/go/pulumi?tab=doc#Context)Context object for the current deployment.nameThis property is required.stringThe unique name of the resource.argsThis property is required.[NotificationChannelArgs](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#inputs/index.html)The arguments to resource properties.opts[ResourceOption](https://pkg.go.dev/github.com/pulumi/pulumi/sdk/v3/go/pulumi?tab=doc#ResourceOption)Bag of options to control resource's behavior.

nameThis property is required.stringThe unique name of the resource.argsThis property is required.[NotificationChannelArgs](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#inputs/index.html)The arguments to resource properties.opts[CustomResourceOptions](/content/docs/reference/pkg/dotnet/Pulumi/Pulumi.CustomResourceOptions.html)Bag of options to control resource's behavior.

nameThis property is required.StringThe unique name of the resource.argsThis property is required.[NotificationChannelArgs](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#inputs/index.html)The arguments to resource properties.optionsCustomResourceOptionsBag of options to control resource's behavior.

### Constructor example [Anchor](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/\#constructor-example/index.html)

The following reference example uses placeholder values for all [input properties](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#inputs/index.html).

- TypeScript
- Python
- Go
- C#
- Java
- YAML
- HCL PREVIEW

```csharp
var notificationChannelResource = new Gcp.Monitoring.NotificationChannel("notificationChannelResource", new()
{
    Type = "string",
    DeletionPolicy = "string",
    Description = "string",
    DisplayName = "string",
    Enabled = false,
    ForceDelete = false,
    Labels =
    {
        { "string", "string" },
    },
    Project = "string",
    SensitiveLabels = new Gcp.Monitoring.Inputs.NotificationChannelSensitiveLabelsArgs
    {
        AuthToken = "string",
        AuthTokenWo = "string",
        AuthTokenWoVersion = "string",
        Password = "string",
        PasswordWo = "string",
        PasswordWoVersion = "string",
        ServiceKey = "string",
        ServiceKeyWo = "string",
        ServiceKeyWoVersion = "string",
    },
    UserLabels =
    {
        { "string", "string" },
    },
});
```

Copy

```go
example, err := monitoring.NewNotificationChannel(ctx, "notificationChannelResource", &monitoring.NotificationChannelArgs{
	Type:           pulumi.String("string"),
	DeletionPolicy: pulumi.String("string"),
	Description:    pulumi.String("string"),
	DisplayName:    pulumi.String("string"),
	Enabled:        pulumi.Bool(false),
	ForceDelete:    pulumi.Bool(false),
	Labels: pulumi.StringMap{
		"string": pulumi.String("string"),
	},
	Project: pulumi.String("string"),
	SensitiveLabels: &monitoring.NotificationChannelSensitiveLabelsArgs{
		AuthToken:           pulumi.String("string"),
		AuthTokenWo:         pulumi.String("string"),
		AuthTokenWoVersion:  pulumi.String("string"),
		Password:            pulumi.String("string"),
		PasswordWo:          pulumi.String("string"),
		PasswordWoVersion:   pulumi.String("string"),
		ServiceKey:          pulumi.String("string"),
		ServiceKeyWo:        pulumi.String("string"),
		ServiceKeyWoVersion: pulumi.String("string"),
	},
	UserLabels: pulumi.StringMap{
		"string": pulumi.String("string"),
	},
})
```

Copy

```hcl
resource "gcp_monitoring_notificationchannel" "notificationChannelResource" {
  type            = "string"
  deletion_policy = "string"
  description     = "string"
  display_name    = "string"
  enabled         = false
  force_delete    = false
  labels = {
    "string" = "string"
  }
  project = "string"
  sensitive_labels = {
    auth_token             = "string"
    auth_token_wo          = "string"
    auth_token_wo_version  = "string"
    password               = "string"
    password_wo            = "string"
    password_wo_version    = "string"
    service_key            = "string"
    service_key_wo         = "string"
    service_key_wo_version = "string"
  }
  user_labels = {
    "string" = "string"
  }
}
```

Copy

```java
var notificationChannelResource = new NotificationChannel("notificationChannelResource", NotificationChannelArgs.builder()
    .type("string")
    .deletionPolicy("string")
    .description("string")
    .displayName("string")
    .enabled(false)
    .forceDelete(false)
    .labels(Map.of("string", "string"))
    .project("string")
    .sensitiveLabels(NotificationChannelSensitiveLabelsArgs.builder()
        .authToken("string")
        .authTokenWo("string")
        .authTokenWoVersion("string")
        .password("string")
        .passwordWo("string")
        .passwordWoVersion("string")
        .serviceKey("string")
        .serviceKeyWo("string")
        .serviceKeyWoVersion("string")
        .build())
    .userLabels(Map.of("string", "string"))
    .build());
```

Copy

```python
notification_channel_resource = gcp.monitoring.NotificationChannel("notificationChannelResource",
    type="string",
    deletion_policy="string",
    description="string",
    display_name="string",
    enabled=False,
    force_delete=False,
    labels={
        "string": "string",
    },
    project="string",
    sensitive_labels={
        "auth_token": "string",
        "auth_token_wo": "string",
        "auth_token_wo_version": "string",
        "password": "string",
        "password_wo": "string",
        "password_wo_version": "string",
        "service_key": "string",
        "service_key_wo": "string",
        "service_key_wo_version": "string",
    },
    user_labels={
        "string": "string",
    })
```

Copy

```typescript
const notificationChannelResource = new gcp.monitoring.NotificationChannel("notificationChannelResource", {
    type: "string",
    deletionPolicy: "string",
    description: "string",
    displayName: "string",
    enabled: false,
    forceDelete: false,
    labels: {
        string: "string",
    },
    project: "string",
    sensitiveLabels: {
        authToken: "string",
        authTokenWo: "string",
        authTokenWoVersion: "string",
        password: "string",
        passwordWo: "string",
        passwordWoVersion: "string",
        serviceKey: "string",
        serviceKeyWo: "string",
        serviceKeyWoVersion: "string",
    },
    userLabels: {
        string: "string",
    },
});
```

Copy

```yaml
type: gcp:monitoring:NotificationChannel
properties:
    deletionPolicy: string
    description: string
    displayName: string
    enabled: false
    forceDelete: false
    labels:
        string: string
    project: string
    sensitiveLabels:
        authToken: string
        authTokenWo: string
        authTokenWoVersion: string
        password: string
        passwordWo: string
        passwordWoVersion: string
        serviceKey: string
        serviceKeyWo: string
        serviceKeyWoVersion: string
    type: string
    userLabels:
        string: string
```

Copy

## NotificationChannel Resource Properties [Anchor](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/\#properties/index.html)

To learn more about resource properties and how to use them, see [Inputs and Outputs](/content/docs/intro/concepts/inputs-outputs/index.html) in the Architecture and Concepts docs.

### Inputs [Anchor](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/\#inputs/index.html)

In Python, inputs that are objects can be passed either as [argument classes or as dictionary literals](/content/docs/languages-sdks/python/#inputs-and-outputs/index.html).

The NotificationChannel resource accepts the following [input](/content/docs/intro/concepts/inputs-outputs/index.html) properties:

[Type](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#type_csharp/index.html)This property is required.stringThe type of the notification channel. This field matches the value of the NotificationChannelDescriptor.type field. See https://cloud.google.com/monitoring/api/ref\_v3/rest/v3/projects.notificationChannelDescriptors/list to get the list of valid values such as "email", "slack", etc...[DeletionPolicy](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#deletionpolicy_csharp/index.html)stringWhether Terraform will be prevented from destroying the resource. Defaults to DELETE.
When a 'terraform destroy' or 'pulumi up' would delete the resource,
the command will fail if this field is set to "PREVENT" in Terraform state.
When set to "ABANDON", the command will remove the resource from Terraform
management without updating or deleting the resource in the API.
When set to "DELETE", deleting the resource is allowed.[Description](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#description_csharp/index.html)stringAn optional human-readable description of this notification channel. This description may provide additional details, beyond the display name, for the channel. This may not exceed 1024 Unicode characters.[DisplayName](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#displayname_csharp/index.html)stringAn optional human-readable name for this notification channel. It is recommended that you specify a non-empty and unique name in order to make it easier to identify the channels in your project, though this is not enforced. The display name is limited to 512 Unicode characters.[Enabled](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#enabled_csharp/index.html)boolWhether notifications are forwarded to the described channel. This makes it possible to disable delivery of notifications to a particular channel without removing the channel from all alerting policies that reference the channel. This is a more convenient approach when the change is temporary and you want to receive notifications from the same set of alerting policies on the channel at some point in the future.[ForceDelete](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#forcedelete_csharp/index.html)boolIf true, the notification channel will be deleted regardless
of its use in alert policies (the policies will be updated
to remove the channel). If false, channels that are still
referenced by an existing alerting policy will fail to be
deleted in a delete operation.[Labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#labels_csharp/index.html)Dictionary<string, string>Configuration fields that define the channel and its behavior. The
permissible and required labels are specified in the
NotificationChannelDescriptor corresponding to the type field.
Labels with sensitive data are obfuscated by the API and therefore the provider cannot
determine if there are upstream changes to these fields. They can also be configured via
the sensitiveLabels block, but cannot be configured in both places.[Project](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#project_csharp/index.html)Changes to this property will trigger replacement.stringThe ID of the project in which the resource belongs.
If it is not provided, the provider project is used.[SensitiveLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#sensitivelabels_csharp/index.html)[NotificationChannelSensitiveLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#notificationchannelsensitivelabels/index.html)Different notification type behaviors are configured primarily using the the `labels` field on this
resource. This block contains the labels which contain secrets or passwords so that they can be marked
sensitive and hidden from plan output. The name of the field, eg: password, will be the key
in the `labels` map in the api request.
Credentials may not be specified in both locations and will cause an error. Changing from one location
to a different credential configuration in the config will require an apply to update state.
Structure is documented below.[UserLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#userlabels_csharp/index.html)Dictionary<string, string>User-supplied key/value data that does not need to conform to the corresponding NotificationChannelDescriptor's schema, unlike the labels field. This field is intended to be used for organizing and identifying the NotificationChannel objects.The field can contain up to 64 entries. Each key and value is limited to 63 Unicode characters or 128 bytes, whichever is smaller. Labels and values can contain only lowercase letters, numerals, underscores, and dashes. Keys must begin with a letter.

[Type](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#type_go/index.html)This property is required.stringThe type of the notification channel. This field matches the value of the NotificationChannelDescriptor.type field. See https://cloud.google.com/monitoring/api/ref\_v3/rest/v3/projects.notificationChannelDescriptors/list to get the list of valid values such as "email", "slack", etc...[DeletionPolicy](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#deletionpolicy_go/index.html)stringWhether Terraform will be prevented from destroying the resource. Defaults to DELETE.
When a 'terraform destroy' or 'pulumi up' would delete the resource,
the command will fail if this field is set to "PREVENT" in Terraform state.
When set to "ABANDON", the command will remove the resource from Terraform
management without updating or deleting the resource in the API.
When set to "DELETE", deleting the resource is allowed.[Description](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#description_go/index.html)stringAn optional human-readable description of this notification channel. This description may provide additional details, beyond the display name, for the channel. This may not exceed 1024 Unicode characters.[DisplayName](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#displayname_go/index.html)stringAn optional human-readable name for this notification channel. It is recommended that you specify a non-empty and unique name in order to make it easier to identify the channels in your project, though this is not enforced. The display name is limited to 512 Unicode characters.[Enabled](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#enabled_go/index.html)boolWhether notifications are forwarded to the described channel. This makes it possible to disable delivery of notifications to a particular channel without removing the channel from all alerting policies that reference the channel. This is a more convenient approach when the change is temporary and you want to receive notifications from the same set of alerting policies on the channel at some point in the future.[ForceDelete](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#forcedelete_go/index.html)boolIf true, the notification channel will be deleted regardless
of its use in alert policies (the policies will be updated
to remove the channel). If false, channels that are still
referenced by an existing alerting policy will fail to be
deleted in a delete operation.[Labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#labels_go/index.html)map\[string\]stringConfiguration fields that define the channel and its behavior. The
permissible and required labels are specified in the
NotificationChannelDescriptor corresponding to the type field.
Labels with sensitive data are obfuscated by the API and therefore the provider cannot
determine if there are upstream changes to these fields. They can also be configured via
the sensitiveLabels block, but cannot be configured in both places.[Project](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#project_go/index.html)Changes to this property will trigger replacement.stringThe ID of the project in which the resource belongs.
If it is not provided, the provider project is used.[SensitiveLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#sensitivelabels_go/index.html)[NotificationChannelSensitiveLabelsArgs](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#notificationchannelsensitivelabels/index.html)Different notification type behaviors are configured primarily using the the `labels` field on this
resource. This block contains the labels which contain secrets or passwords so that they can be marked
sensitive and hidden from plan output. The name of the field, eg: password, will be the key
in the `labels` map in the api request.
Credentials may not be specified in both locations and will cause an error. Changing from one location
to a different credential configuration in the config will require an apply to update state.
Structure is documented below.[UserLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#userlabels_go/index.html)map\[string\]stringUser-supplied key/value data that does not need to conform to the corresponding NotificationChannelDescriptor's schema, unlike the labels field. This field is intended to be used for organizing and identifying the NotificationChannel objects.The field can contain up to 64 entries. Each key and value is limited to 63 Unicode characters or 128 bytes, whichever is smaller. Labels and values can contain only lowercase letters, numerals, underscores, and dashes. Keys must begin with a letter.

[type](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#type_hcl/index.html)This property is required.stringThe type of the notification channel. This field matches the value of the NotificationChannelDescriptor.type field. See https://cloud.google.com/monitoring/api/ref\_v3/rest/v3/projects.notificationChannelDescriptors/list to get the list of valid values such as "email", "slack", etc...[deletion\_policy](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#deletion_policy_hcl/index.html)stringWhether Terraform will be prevented from destroying the resource. Defaults to DELETE.
When a 'terraform destroy' or 'pulumi up' would delete the resource,
the command will fail if this field is set to "PREVENT" in Terraform state.
When set to "ABANDON", the command will remove the resource from Terraform
management without updating or deleting the resource in the API.
When set to "DELETE", deleting the resource is allowed.[description](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#description_hcl/index.html)stringAn optional human-readable description of this notification channel. This description may provide additional details, beyond the display name, for the channel. This may not exceed 1024 Unicode characters.[display\_name](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#display_name_hcl/index.html)stringAn optional human-readable name for this notification channel. It is recommended that you specify a non-empty and unique name in order to make it easier to identify the channels in your project, though this is not enforced. The display name is limited to 512 Unicode characters.[enabled](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#enabled_hcl/index.html)boolWhether notifications are forwarded to the described channel. This makes it possible to disable delivery of notifications to a particular channel without removing the channel from all alerting policies that reference the channel. This is a more convenient approach when the change is temporary and you want to receive notifications from the same set of alerting policies on the channel at some point in the future.[force\_delete](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#force_delete_hcl/index.html)boolIf true, the notification channel will be deleted regardless
of its use in alert policies (the policies will be updated
to remove the channel). If false, channels that are still
referenced by an existing alerting policy will fail to be
deleted in a delete operation.[labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#labels_hcl/index.html)map(string)Configuration fields that define the channel and its behavior. The
permissible and required labels are specified in the
NotificationChannelDescriptor corresponding to the type field.
Labels with sensitive data are obfuscated by the API and therefore the provider cannot
determine if there are upstream changes to these fields. They can also be configured via
the sensitiveLabels block, but cannot be configured in both places.[project](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#project_hcl/index.html)Changes to this property will trigger replacement.stringThe ID of the project in which the resource belongs.
If it is not provided, the provider project is used.[sensitive\_labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#sensitive_labels_hcl/index.html)[object](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#notificationchannelsensitivelabels/index.html)Different notification type behaviors are configured primarily using the the `labels` field on this
resource. This block contains the labels which contain secrets or passwords so that they can be marked
sensitive and hidden from plan output. The name of the field, eg: password, will be the key
in the `labels` map in the api request.
Credentials may not be specified in both locations and will cause an error. Changing from one location
to a different credential configuration in the config will require an apply to update state.
Structure is documented below.[user\_labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#user_labels_hcl/index.html)map(string)User-supplied key/value data that does not need to conform to the corresponding NotificationChannelDescriptor's schema, unlike the labels field. This field is intended to be used for organizing and identifying the NotificationChannel objects.The field can contain up to 64 entries. Each key and value is limited to 63 Unicode characters or 128 bytes, whichever is smaller. Labels and values can contain only lowercase letters, numerals, underscores, and dashes. Keys must begin with a letter.

[type](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#type_java/index.html)This property is required.StringThe type of the notification channel. This field matches the value of the NotificationChannelDescriptor.type field. See https://cloud.google.com/monitoring/api/ref\_v3/rest/v3/projects.notificationChannelDescriptors/list to get the list of valid values such as "email", "slack", etc...[deletionPolicy](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#deletionpolicy_java/index.html)StringWhether Terraform will be prevented from destroying the resource. Defaults to DELETE.
When a 'terraform destroy' or 'pulumi up' would delete the resource,
the command will fail if this field is set to "PREVENT" in Terraform state.
When set to "ABANDON", the command will remove the resource from Terraform
management without updating or deleting the resource in the API.
When set to "DELETE", deleting the resource is allowed.[description](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#description_java/index.html)StringAn optional human-readable description of this notification channel. This description may provide additional details, beyond the display name, for the channel. This may not exceed 1024 Unicode characters.[displayName](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#displayname_java/index.html)StringAn optional human-readable name for this notification channel. It is recommended that you specify a non-empty and unique name in order to make it easier to identify the channels in your project, though this is not enforced. The display name is limited to 512 Unicode characters.[enabled](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#enabled_java/index.html)BooleanWhether notifications are forwarded to the described channel. This makes it possible to disable delivery of notifications to a particular channel without removing the channel from all alerting policies that reference the channel. This is a more convenient approach when the change is temporary and you want to receive notifications from the same set of alerting policies on the channel at some point in the future.[forceDelete](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#forcedelete_java/index.html)BooleanIf true, the notification channel will be deleted regardless
of its use in alert policies (the policies will be updated
to remove the channel). If false, channels that are still
referenced by an existing alerting policy will fail to be
deleted in a delete operation.[labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#labels_java/index.html)Map<String,String>Configuration fields that define the channel and its behavior. The
permissible and required labels are specified in the
NotificationChannelDescriptor corresponding to the type field.
Labels with sensitive data are obfuscated by the API and therefore the provider cannot
determine if there are upstream changes to these fields. They can also be configured via
the sensitiveLabels block, but cannot be configured in both places.[project](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#project_java/index.html)Changes to this property will trigger replacement.StringThe ID of the project in which the resource belongs.
If it is not provided, the provider project is used.[sensitiveLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#sensitivelabels_java/index.html)[NotificationChannelSensitiveLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#notificationchannelsensitivelabels/index.html)Different notification type behaviors are configured primarily using the the `labels` field on this
resource. This block contains the labels which contain secrets or passwords so that they can be marked
sensitive and hidden from plan output. The name of the field, eg: password, will be the key
in the `labels` map in the api request.
Credentials may not be specified in both locations and will cause an error. Changing from one location
to a different credential configuration in the config will require an apply to update state.
Structure is documented below.[userLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#userlabels_java/index.html)Map<String,String>User-supplied key/value data that does not need to conform to the corresponding NotificationChannelDescriptor's schema, unlike the labels field. This field is intended to be used for organizing and identifying the NotificationChannel objects.The field can contain up to 64 entries. Each key and value is limited to 63 Unicode characters or 128 bytes, whichever is smaller. Labels and values can contain only lowercase letters, numerals, underscores, and dashes. Keys must begin with a letter.

[type](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#type_nodejs/index.html)This property is required.stringThe type of the notification channel. This field matches the value of the NotificationChannelDescriptor.type field. See https://cloud.google.com/monitoring/api/ref\_v3/rest/v3/projects.notificationChannelDescriptors/list to get the list of valid values such as "email", "slack", etc...[deletionPolicy](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#deletionpolicy_nodejs/index.html)stringWhether Terraform will be prevented from destroying the resource. Defaults to DELETE.
When a 'terraform destroy' or 'pulumi up' would delete the resource,
the command will fail if this field is set to "PREVENT" in Terraform state.
When set to "ABANDON", the command will remove the resource from Terraform
management without updating or deleting the resource in the API.
When set to "DELETE", deleting the resource is allowed.[description](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#description_nodejs/index.html)stringAn optional human-readable description of this notification channel. This description may provide additional details, beyond the display name, for the channel. This may not exceed 1024 Unicode characters.[displayName](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#displayname_nodejs/index.html)stringAn optional human-readable name for this notification channel. It is recommended that you specify a non-empty and unique name in order to make it easier to identify the channels in your project, though this is not enforced. The display name is limited to 512 Unicode characters.[enabled](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#enabled_nodejs/index.html)booleanWhether notifications are forwarded to the described channel. This makes it possible to disable delivery of notifications to a particular channel without removing the channel from all alerting policies that reference the channel. This is a more convenient approach when the change is temporary and you want to receive notifications from the same set of alerting policies on the channel at some point in the future.[forceDelete](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#forcedelete_nodejs/index.html)booleanIf true, the notification channel will be deleted regardless
of its use in alert policies (the policies will be updated
to remove the channel). If false, channels that are still
referenced by an existing alerting policy will fail to be
deleted in a delete operation.[labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#labels_nodejs/index.html){\[key: string\]: string}Configuration fields that define the channel and its behavior. The
permissible and required labels are specified in the
NotificationChannelDescriptor corresponding to the type field.
Labels with sensitive data are obfuscated by the API and therefore the provider cannot
determine if there are upstream changes to these fields. They can also be configured via
the sensitiveLabels block, but cannot be configured in both places.[project](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#project_nodejs/index.html)Changes to this property will trigger replacement.stringThe ID of the project in which the resource belongs.
If it is not provided, the provider project is used.[sensitiveLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#sensitivelabels_nodejs/index.html)[NotificationChannelSensitiveLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#notificationchannelsensitivelabels/index.html)Different notification type behaviors are configured primarily using the the `labels` field on this
resource. This block contains the labels which contain secrets or passwords so that they can be marked
sensitive and hidden from plan output. The name of the field, eg: password, will be the key
in the `labels` map in the api request.
Credentials may not be specified in both locations and will cause an error. Changing from one location
to a different credential configuration in the config will require an apply to update state.
Structure is documented below.[userLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#userlabels_nodejs/index.html){\[key: string\]: string}User-supplied key/value data that does not need to conform to the corresponding NotificationChannelDescriptor's schema, unlike the labels field. This field is intended to be used for organizing and identifying the NotificationChannel objects.The field can contain up to 64 entries. Each key and value is limited to 63 Unicode characters or 128 bytes, whichever is smaller. Labels and values can contain only lowercase letters, numerals, underscores, and dashes. Keys must begin with a letter.

[type](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#type_python/index.html)This property is required.strThe type of the notification channel. This field matches the value of the NotificationChannelDescriptor.type field. See https://cloud.google.com/monitoring/api/ref\_v3/rest/v3/projects.notificationChannelDescriptors/list to get the list of valid values such as "email", "slack", etc...[deletion\_policy](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#deletion_policy_python/index.html)strWhether Terraform will be prevented from destroying the resource. Defaults to DELETE.
When a 'terraform destroy' or 'pulumi up' would delete the resource,
the command will fail if this field is set to "PREVENT" in Terraform state.
When set to "ABANDON", the command will remove the resource from Terraform
management without updating or deleting the resource in the API.
When set to "DELETE", deleting the resource is allowed.[description](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#description_python/index.html)strAn optional human-readable description of this notification channel. This description may provide additional details, beyond the display name, for the channel. This may not exceed 1024 Unicode characters.[display\_name](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#display_name_python/index.html)strAn optional human-readable name for this notification channel. It is recommended that you specify a non-empty and unique name in order to make it easier to identify the channels in your project, though this is not enforced. The display name is limited to 512 Unicode characters.[enabled](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#enabled_python/index.html)boolWhether notifications are forwarded to the described channel. This makes it possible to disable delivery of notifications to a particular channel without removing the channel from all alerting policies that reference the channel. This is a more convenient approach when the change is temporary and you want to receive notifications from the same set of alerting policies on the channel at some point in the future.[force\_delete](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#force_delete_python/index.html)boolIf true, the notification channel will be deleted regardless
of its use in alert policies (the policies will be updated
to remove the channel). If false, channels that are still
referenced by an existing alerting policy will fail to be
deleted in a delete operation.[labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#labels_python/index.html)Mapping\[str, str\]Configuration fields that define the channel and its behavior. The
permissible and required labels are specified in the
NotificationChannelDescriptor corresponding to the type field.
Labels with sensitive data are obfuscated by the API and therefore the provider cannot
determine if there are upstream changes to these fields. They can also be configured via
the sensitiveLabels block, but cannot be configured in both places.[project](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#project_python/index.html)Changes to this property will trigger replacement.strThe ID of the project in which the resource belongs.
If it is not provided, the provider project is used.[sensitive\_labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#sensitive_labels_python/index.html)[NotificationChannelSensitiveLabelsArgs](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#notificationchannelsensitivelabels/index.html)Different notification type behaviors are configured primarily using the the `labels` field on this
resource. This block contains the labels which contain secrets or passwords so that they can be marked
sensitive and hidden from plan output. The name of the field, eg: password, will be the key
in the `labels` map in the api request.
Credentials may not be specified in both locations and will cause an error. Changing from one location
to a different credential configuration in the config will require an apply to update state.
Structure is documented below.[user\_labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#user_labels_python/index.html)Mapping\[str, str\]User-supplied key/value data that does not need to conform to the corresponding NotificationChannelDescriptor's schema, unlike the labels field. This field is intended to be used for organizing and identifying the NotificationChannel objects.The field can contain up to 64 entries. Each key and value is limited to 63 Unicode characters or 128 bytes, whichever is smaller. Labels and values can contain only lowercase letters, numerals, underscores, and dashes. Keys must begin with a letter.

[type](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#type_yaml/index.html)This property is required.StringThe type of the notification channel. This field matches the value of the NotificationChannelDescriptor.type field. See https://cloud.google.com/monitoring/api/ref\_v3/rest/v3/projects.notificationChannelDescriptors/list to get the list of valid values such as "email", "slack", etc...[deletionPolicy](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#deletionpolicy_yaml/index.html)StringWhether Terraform will be prevented from destroying the resource. Defaults to DELETE.
When a 'terraform destroy' or 'pulumi up' would delete the resource,
the command will fail if this field is set to "PREVENT" in Terraform state.
When set to "ABANDON", the command will remove the resource from Terraform
management without updating or deleting the resource in the API.
When set to "DELETE", deleting the resource is allowed.[description](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#description_yaml/index.html)StringAn optional human-readable description of this notification channel. This description may provide additional details, beyond the display name, for the channel. This may not exceed 1024 Unicode characters.[displayName](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#displayname_yaml/index.html)StringAn optional human-readable name for this notification channel. It is recommended that you specify a non-empty and unique name in order to make it easier to identify the channels in your project, though this is not enforced. The display name is limited to 512 Unicode characters.[enabled](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#enabled_yaml/index.html)BooleanWhether notifications are forwarded to the described channel. This makes it possible to disable delivery of notifications to a particular channel without removing the channel from all alerting policies that reference the channel. This is a more convenient approach when the change is temporary and you want to receive notifications from the same set of alerting policies on the channel at some point in the future.[forceDelete](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#forcedelete_yaml/index.html)BooleanIf true, the notification channel will be deleted regardless
of its use in alert policies (the policies will be updated
to remove the channel). If false, channels that are still
referenced by an existing alerting policy will fail to be
deleted in a delete operation.[labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#labels_yaml/index.html)Map<String>Configuration fields that define the channel and its behavior. The
permissible and required labels are specified in the
NotificationChannelDescriptor corresponding to the type field.
Labels with sensitive data are obfuscated by the API and therefore the provider cannot
determine if there are upstream changes to these fields. They can also be configured via
the sensitiveLabels block, but cannot be configured in both places.[project](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#project_yaml/index.html)Changes to this property will trigger replacement.StringThe ID of the project in which the resource belongs.
If it is not provided, the provider project is used.[sensitiveLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#sensitivelabels_yaml/index.html)[Property Map](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#notificationchannelsensitivelabels/index.html)Different notification type behaviors are configured primarily using the the `labels` field on this
resource. This block contains the labels which contain secrets or passwords so that they can be marked
sensitive and hidden from plan output. The name of the field, eg: password, will be the key
in the `labels` map in the api request.
Credentials may not be specified in both locations and will cause an error. Changing from one location
to a different credential configuration in the config will require an apply to update state.
Structure is documented below.[userLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#userlabels_yaml/index.html)Map<String>User-supplied key/value data that does not need to conform to the corresponding NotificationChannelDescriptor's schema, unlike the labels field. This field is intended to be used for organizing and identifying the NotificationChannel objects.The field can contain up to 64 entries. Each key and value is limited to 63 Unicode characters or 128 bytes, whichever is smaller. Labels and values can contain only lowercase letters, numerals, underscores, and dashes. Keys must begin with a letter.

### Outputs [Anchor](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/\#outputs/index.html)

All [input](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#inputs/index.html) properties are implicitly available as output properties. Additionally, the NotificationChannel resource produces the following output properties:

[Id](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#id_csharp/index.html)stringThe provider-assigned unique ID for this managed resource.[Name](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#name_csharp/index.html)stringThe full REST resource name for this channel. The syntax is:
projects/\[PROJECT\_ID\]/notificationChannels/\[CHANNEL\_ID\]
The \[CHANNEL\_ID\] is automatically assigned by the server on creation.[VerificationStatus](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#verificationstatus_csharp/index.html)stringIndicates whether this channel has been verified or not. On a ListNotificationChannels or GetNotificationChannel operation, this field is expected to be populated.If the value is UNVERIFIED, then it indicates that the channel is non-functioning (it both requires verification and lacks verification); otherwise, it is assumed that the channel works.If the channel is neither VERIFIED nor UNVERIFIED, it implies that the channel is of a type that does not require verification or that this specific channel has been exempted from verification because it was created prior to verification being required for channels of this type.This field cannot be modified using a standard UpdateNotificationChannel operation. To change the value of this field, you must call VerifyNotificationChannel.

[Id](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#id_go/index.html)stringThe provider-assigned unique ID for this managed resource.[Name](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#name_go/index.html)stringThe full REST resource name for this channel. The syntax is:
projects/\[PROJECT\_ID\]/notificationChannels/\[CHANNEL\_ID\]
The \[CHANNEL\_ID\] is automatically assigned by the server on creation.[VerificationStatus](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#verificationstatus_go/index.html)stringIndicates whether this channel has been verified or not. On a ListNotificationChannels or GetNotificationChannel operation, this field is expected to be populated.If the value is UNVERIFIED, then it indicates that the channel is non-functioning (it both requires verification and lacks verification); otherwise, it is assumed that the channel works.If the channel is neither VERIFIED nor UNVERIFIED, it implies that the channel is of a type that does not require verification or that this specific channel has been exempted from verification because it was created prior to verification being required for channels of this type.This field cannot be modified using a standard UpdateNotificationChannel operation. To change the value of this field, you must call VerifyNotificationChannel.

[id](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#id_hcl/index.html)stringThe provider-assigned unique ID for this managed resource.[name](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#name_hcl/index.html)stringThe full REST resource name for this channel. The syntax is:
projects/\[PROJECT\_ID\]/notificationChannels/\[CHANNEL\_ID\]
The \[CHANNEL\_ID\] is automatically assigned by the server on creation.[verification\_status](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#verification_status_hcl/index.html)stringIndicates whether this channel has been verified or not. On a ListNotificationChannels or GetNotificationChannel operation, this field is expected to be populated.If the value is UNVERIFIED, then it indicates that the channel is non-functioning (it both requires verification and lacks verification); otherwise, it is assumed that the channel works.If the channel is neither VERIFIED nor UNVERIFIED, it implies that the channel is of a type that does not require verification or that this specific channel has been exempted from verification because it was created prior to verification being required for channels of this type.This field cannot be modified using a standard UpdateNotificationChannel operation. To change the value of this field, you must call VerifyNotificationChannel.

[id](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#id_java/index.html)StringThe provider-assigned unique ID for this managed resource.[name](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#name_java/index.html)StringThe full REST resource name for this channel. The syntax is:
projects/\[PROJECT\_ID\]/notificationChannels/\[CHANNEL\_ID\]
The \[CHANNEL\_ID\] is automatically assigned by the server on creation.[verificationStatus](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#verificationstatus_java/index.html)StringIndicates whether this channel has been verified or not. On a ListNotificationChannels or GetNotificationChannel operation, this field is expected to be populated.If the value is UNVERIFIED, then it indicates that the channel is non-functioning (it both requires verification and lacks verification); otherwise, it is assumed that the channel works.If the channel is neither VERIFIED nor UNVERIFIED, it implies that the channel is of a type that does not require verification or that this specific channel has been exempted from verification because it was created prior to verification being required for channels of this type.This field cannot be modified using a standard UpdateNotificationChannel operation. To change the value of this field, you must call VerifyNotificationChannel.

[id](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#id_nodejs/index.html)stringThe provider-assigned unique ID for this managed resource.[name](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#name_nodejs/index.html)stringThe full REST resource name for this channel. The syntax is:
projects/\[PROJECT\_ID\]/notificationChannels/\[CHANNEL\_ID\]
The \[CHANNEL\_ID\] is automatically assigned by the server on creation.[verificationStatus](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#verificationstatus_nodejs/index.html)stringIndicates whether this channel has been verified or not. On a ListNotificationChannels or GetNotificationChannel operation, this field is expected to be populated.If the value is UNVERIFIED, then it indicates that the channel is non-functioning (it both requires verification and lacks verification); otherwise, it is assumed that the channel works.If the channel is neither VERIFIED nor UNVERIFIED, it implies that the channel is of a type that does not require verification or that this specific channel has been exempted from verification because it was created prior to verification being required for channels of this type.This field cannot be modified using a standard UpdateNotificationChannel operation. To change the value of this field, you must call VerifyNotificationChannel.

[id](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#id_python/index.html)strThe provider-assigned unique ID for this managed resource.[name](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#name_python/index.html)strThe full REST resource name for this channel. The syntax is:
projects/\[PROJECT\_ID\]/notificationChannels/\[CHANNEL\_ID\]
The \[CHANNEL\_ID\] is automatically assigned by the server on creation.[verification\_status](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#verification_status_python/index.html)strIndicates whether this channel has been verified or not. On a ListNotificationChannels or GetNotificationChannel operation, this field is expected to be populated.If the value is UNVERIFIED, then it indicates that the channel is non-functioning (it both requires verification and lacks verification); otherwise, it is assumed that the channel works.If the channel is neither VERIFIED nor UNVERIFIED, it implies that the channel is of a type that does not require verification or that this specific channel has been exempted from verification because it was created prior to verification being required for channels of this type.This field cannot be modified using a standard UpdateNotificationChannel operation. To change the value of this field, you must call VerifyNotificationChannel.

[id](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#id_yaml/index.html)StringThe provider-assigned unique ID for this managed resource.[name](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#name_yaml/index.html)StringThe full REST resource name for this channel. The syntax is:
projects/\[PROJECT\_ID\]/notificationChannels/\[CHANNEL\_ID\]
The \[CHANNEL\_ID\] is automatically assigned by the server on creation.[verificationStatus](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#verificationstatus_yaml/index.html)StringIndicates whether this channel has been verified or not. On a ListNotificationChannels or GetNotificationChannel operation, this field is expected to be populated.If the value is UNVERIFIED, then it indicates that the channel is non-functioning (it both requires verification and lacks verification); otherwise, it is assumed that the channel works.If the channel is neither VERIFIED nor UNVERIFIED, it implies that the channel is of a type that does not require verification or that this specific channel has been exempted from verification because it was created prior to verification being required for channels of this type.This field cannot be modified using a standard UpdateNotificationChannel operation. To change the value of this field, you must call VerifyNotificationChannel.

## Look up Existing NotificationChannel Resource [Anchor](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/\#look-up/index.html)

Get an existing NotificationChannel resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.

- TypeScript
- Python
- Go
- C#
- Java
- YAML
- HCL PREVIEW

```typescript
public static get(name: string, id: Input<ID>, state?: NotificationChannelState, opts?: CustomResourceOptions): NotificationChannel
```

```python
@staticmethod
def get(resource_name: str,
        id: str,
        opts: Optional[ResourceOptions] = None,
        deletion_policy: Optional[str] = None,
        description: Optional[str] = None,
        display_name: Optional[str] = None,
        enabled: Optional[bool] = None,
        force_delete: Optional[bool] = None,
        labels: Optional[Mapping[str, str]] = None,
        name: Optional[str] = None,
        project: Optional[str] = None,
        sensitive_labels: Optional[NotificationChannelSensitiveLabelsArgs] = None,
        type: Optional[str] = None,
        user_labels: Optional[Mapping[str, str]] = None,
        verification_status: Optional[str] = None) -> NotificationChannel
```

```go
func GetNotificationChannel(ctx *Context, name string, id IDInput, state *NotificationChannelState, opts ...ResourceOption) (*NotificationChannel, error)
```

```csharp
public static NotificationChannel Get(string name, Input<string> id, NotificationChannelState? state, CustomResourceOptions? opts = null)
```

```java
public static NotificationChannel get(String name, Output<String> id, NotificationChannelState state, CustomResourceOptions options)
```

```yaml
resources:  _:    type: gcp:monitoring:NotificationChannel    get:      id: ${id}
```

```hcl
import {
  to = gcp_monitoring_notificationchannel.example
  id = "${id}"
}
```

nameThis property is required.The unique name of the resulting resource.idThis property is required.The _unique_ provider ID of the resource to lookup.stateAny extra arguments used during the lookup.optsA bag of options that control this resource's behavior.

resource\_nameThis property is required.The unique name of the resulting resource.idThis property is required.The _unique_ provider ID of the resource to lookup.

The following state arguments are supported:

[DeletionPolicy](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_deletionpolicy_csharp/index.html)stringWhether Terraform will be prevented from destroying the resource. Defaults to DELETE.
When a 'terraform destroy' or 'pulumi up' would delete the resource,
the command will fail if this field is set to "PREVENT" in Terraform state.
When set to "ABANDON", the command will remove the resource from Terraform
management without updating or deleting the resource in the API.
When set to "DELETE", deleting the resource is allowed.[Description](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_description_csharp/index.html)stringAn optional human-readable description of this notification channel. This description may provide additional details, beyond the display name, for the channel. This may not exceed 1024 Unicode characters.[DisplayName](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_displayname_csharp/index.html)stringAn optional human-readable name for this notification channel. It is recommended that you specify a non-empty and unique name in order to make it easier to identify the channels in your project, though this is not enforced. The display name is limited to 512 Unicode characters.[Enabled](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_enabled_csharp/index.html)boolWhether notifications are forwarded to the described channel. This makes it possible to disable delivery of notifications to a particular channel without removing the channel from all alerting policies that reference the channel. This is a more convenient approach when the change is temporary and you want to receive notifications from the same set of alerting policies on the channel at some point in the future.[ForceDelete](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_forcedelete_csharp/index.html)boolIf true, the notification channel will be deleted regardless
of its use in alert policies (the policies will be updated
to remove the channel). If false, channels that are still
referenced by an existing alerting policy will fail to be
deleted in a delete operation.[Labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_labels_csharp/index.html)Dictionary<string, string>Configuration fields that define the channel and its behavior. The
permissible and required labels are specified in the
NotificationChannelDescriptor corresponding to the type field.
Labels with sensitive data are obfuscated by the API and therefore the provider cannot
determine if there are upstream changes to these fields. They can also be configured via
the sensitiveLabels block, but cannot be configured in both places.[Name](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_name_csharp/index.html)stringThe full REST resource name for this channel. The syntax is:
projects/\[PROJECT\_ID\]/notificationChannels/\[CHANNEL\_ID\]
The \[CHANNEL\_ID\] is automatically assigned by the server on creation.[Project](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_project_csharp/index.html)Changes to this property will trigger replacement.stringThe ID of the project in which the resource belongs.
If it is not provided, the provider project is used.[SensitiveLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_sensitivelabels_csharp/index.html)[NotificationChannelSensitiveLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#notificationchannelsensitivelabels/index.html)Different notification type behaviors are configured primarily using the the `labels` field on this
resource. This block contains the labels which contain secrets or passwords so that they can be marked
sensitive and hidden from plan output. The name of the field, eg: password, will be the key
in the `labels` map in the api request.
Credentials may not be specified in both locations and will cause an error. Changing from one location
to a different credential configuration in the config will require an apply to update state.
Structure is documented below.[Type](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_type_csharp/index.html)stringThe type of the notification channel. This field matches the value of the NotificationChannelDescriptor.type field. See https://cloud.google.com/monitoring/api/ref\_v3/rest/v3/projects.notificationChannelDescriptors/list to get the list of valid values such as "email", "slack", etc...[UserLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_userlabels_csharp/index.html)Dictionary<string, string>User-supplied key/value data that does not need to conform to the corresponding NotificationChannelDescriptor's schema, unlike the labels field. This field is intended to be used for organizing and identifying the NotificationChannel objects.The field can contain up to 64 entries. Each key and value is limited to 63 Unicode characters or 128 bytes, whichever is smaller. Labels and values can contain only lowercase letters, numerals, underscores, and dashes. Keys must begin with a letter.[VerificationStatus](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_verificationstatus_csharp/index.html)stringIndicates whether this channel has been verified or not. On a ListNotificationChannels or GetNotificationChannel operation, this field is expected to be populated.If the value is UNVERIFIED, then it indicates that the channel is non-functioning (it both requires verification and lacks verification); otherwise, it is assumed that the channel works.If the channel is neither VERIFIED nor UNVERIFIED, it implies that the channel is of a type that does not require verification or that this specific channel has been exempted from verification because it was created prior to verification being required for channels of this type.This field cannot be modified using a standard UpdateNotificationChannel operation. To change the value of this field, you must call VerifyNotificationChannel.

[DeletionPolicy](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_deletionpolicy_go/index.html)stringWhether Terraform will be prevented from destroying the resource. Defaults to DELETE.
When a 'terraform destroy' or 'pulumi up' would delete the resource,
the command will fail if this field is set to "PREVENT" in Terraform state.
When set to "ABANDON", the command will remove the resource from Terraform
management without updating or deleting the resource in the API.
When set to "DELETE", deleting the resource is allowed.[Description](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_description_go/index.html)stringAn optional human-readable description of this notification channel. This description may provide additional details, beyond the display name, for the channel. This may not exceed 1024 Unicode characters.[DisplayName](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_displayname_go/index.html)stringAn optional human-readable name for this notification channel. It is recommended that you specify a non-empty and unique name in order to make it easier to identify the channels in your project, though this is not enforced. The display name is limited to 512 Unicode characters.[Enabled](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_enabled_go/index.html)boolWhether notifications are forwarded to the described channel. This makes it possible to disable delivery of notifications to a particular channel without removing the channel from all alerting policies that reference the channel. This is a more convenient approach when the change is temporary and you want to receive notifications from the same set of alerting policies on the channel at some point in the future.[ForceDelete](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_forcedelete_go/index.html)boolIf true, the notification channel will be deleted regardless
of its use in alert policies (the policies will be updated
to remove the channel). If false, channels that are still
referenced by an existing alerting policy will fail to be
deleted in a delete operation.[Labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_labels_go/index.html)map\[string\]stringConfiguration fields that define the channel and its behavior. The
permissible and required labels are specified in the
NotificationChannelDescriptor corresponding to the type field.
Labels with sensitive data are obfuscated by the API and therefore the provider cannot
determine if there are upstream changes to these fields. They can also be configured via
the sensitiveLabels block, but cannot be configured in both places.[Name](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_name_go/index.html)stringThe full REST resource name for this channel. The syntax is:
projects/\[PROJECT\_ID\]/notificationChannels/\[CHANNEL\_ID\]
The \[CHANNEL\_ID\] is automatically assigned by the server on creation.[Project](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_project_go/index.html)Changes to this property will trigger replacement.stringThe ID of the project in which the resource belongs.
If it is not provided, the provider project is used.[SensitiveLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_sensitivelabels_go/index.html)[NotificationChannelSensitiveLabelsArgs](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#notificationchannelsensitivelabels/index.html)Different notification type behaviors are configured primarily using the the `labels` field on this
resource. This block contains the labels which contain secrets or passwords so that they can be marked
sensitive and hidden from plan output. The name of the field, eg: password, will be the key
in the `labels` map in the api request.
Credentials may not be specified in both locations and will cause an error. Changing from one location
to a different credential configuration in the config will require an apply to update state.
Structure is documented below.[Type](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_type_go/index.html)stringThe type of the notification channel. This field matches the value of the NotificationChannelDescriptor.type field. See https://cloud.google.com/monitoring/api/ref\_v3/rest/v3/projects.notificationChannelDescriptors/list to get the list of valid values such as "email", "slack", etc...[UserLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_userlabels_go/index.html)map\[string\]stringUser-supplied key/value data that does not need to conform to the corresponding NotificationChannelDescriptor's schema, unlike the labels field. This field is intended to be used for organizing and identifying the NotificationChannel objects.The field can contain up to 64 entries. Each key and value is limited to 63 Unicode characters or 128 bytes, whichever is smaller. Labels and values can contain only lowercase letters, numerals, underscores, and dashes. Keys must begin with a letter.[VerificationStatus](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_verificationstatus_go/index.html)stringIndicates whether this channel has been verified or not. On a ListNotificationChannels or GetNotificationChannel operation, this field is expected to be populated.If the value is UNVERIFIED, then it indicates that the channel is non-functioning (it both requires verification and lacks verification); otherwise, it is assumed that the channel works.If the channel is neither VERIFIED nor UNVERIFIED, it implies that the channel is of a type that does not require verification or that this specific channel has been exempted from verification because it was created prior to verification being required for channels of this type.This field cannot be modified using a standard UpdateNotificationChannel operation. To change the value of this field, you must call VerifyNotificationChannel.

[deletion\_policy](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_deletion_policy_hcl/index.html)stringWhether Terraform will be prevented from destroying the resource. Defaults to DELETE.
When a 'terraform destroy' or 'pulumi up' would delete the resource,
the command will fail if this field is set to "PREVENT" in Terraform state.
When set to "ABANDON", the command will remove the resource from Terraform
management without updating or deleting the resource in the API.
When set to "DELETE", deleting the resource is allowed.[description](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_description_hcl/index.html)stringAn optional human-readable description of this notification channel. This description may provide additional details, beyond the display name, for the channel. This may not exceed 1024 Unicode characters.[display\_name](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_display_name_hcl/index.html)stringAn optional human-readable name for this notification channel. It is recommended that you specify a non-empty and unique name in order to make it easier to identify the channels in your project, though this is not enforced. The display name is limited to 512 Unicode characters.[enabled](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_enabled_hcl/index.html)boolWhether notifications are forwarded to the described channel. This makes it possible to disable delivery of notifications to a particular channel without removing the channel from all alerting policies that reference the channel. This is a more convenient approach when the change is temporary and you want to receive notifications from the same set of alerting policies on the channel at some point in the future.[force\_delete](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_force_delete_hcl/index.html)boolIf true, the notification channel will be deleted regardless
of its use in alert policies (the policies will be updated
to remove the channel). If false, channels that are still
referenced by an existing alerting policy will fail to be
deleted in a delete operation.[labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_labels_hcl/index.html)map(string)Configuration fields that define the channel and its behavior. The
permissible and required labels are specified in the
NotificationChannelDescriptor corresponding to the type field.
Labels with sensitive data are obfuscated by the API and therefore the provider cannot
determine if there are upstream changes to these fields. They can also be configured via
the sensitiveLabels block, but cannot be configured in both places.[name](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_name_hcl/index.html)stringThe full REST resource name for this channel. The syntax is:
projects/\[PROJECT\_ID\]/notificationChannels/\[CHANNEL\_ID\]
The \[CHANNEL\_ID\] is automatically assigned by the server on creation.[project](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_project_hcl/index.html)Changes to this property will trigger replacement.stringThe ID of the project in which the resource belongs.
If it is not provided, the provider project is used.[sensitive\_labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_sensitive_labels_hcl/index.html)[object](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#notificationchannelsensitivelabels/index.html)Different notification type behaviors are configured primarily using the the `labels` field on this
resource. This block contains the labels which contain secrets or passwords so that they can be marked
sensitive and hidden from plan output. The name of the field, eg: password, will be the key
in the `labels` map in the api request.
Credentials may not be specified in both locations and will cause an error. Changing from one location
to a different credential configuration in the config will require an apply to update state.
Structure is documented below.[type](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_type_hcl/index.html)stringThe type of the notification channel. This field matches the value of the NotificationChannelDescriptor.type field. See https://cloud.google.com/monitoring/api/ref\_v3/rest/v3/projects.notificationChannelDescriptors/list to get the list of valid values such as "email", "slack", etc...[user\_labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_user_labels_hcl/index.html)map(string)User-supplied key/value data that does not need to conform to the corresponding NotificationChannelDescriptor's schema, unlike the labels field. This field is intended to be used for organizing and identifying the NotificationChannel objects.The field can contain up to 64 entries. Each key and value is limited to 63 Unicode characters or 128 bytes, whichever is smaller. Labels and values can contain only lowercase letters, numerals, underscores, and dashes. Keys must begin with a letter.[verification\_status](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_verification_status_hcl/index.html)stringIndicates whether this channel has been verified or not. On a ListNotificationChannels or GetNotificationChannel operation, this field is expected to be populated.If the value is UNVERIFIED, then it indicates that the channel is non-functioning (it both requires verification and lacks verification); otherwise, it is assumed that the channel works.If the channel is neither VERIFIED nor UNVERIFIED, it implies that the channel is of a type that does not require verification or that this specific channel has been exempted from verification because it was created prior to verification being required for channels of this type.This field cannot be modified using a standard UpdateNotificationChannel operation. To change the value of this field, you must call VerifyNotificationChannel.

[deletionPolicy](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_deletionpolicy_java/index.html)StringWhether Terraform will be prevented from destroying the resource. Defaults to DELETE.
When a 'terraform destroy' or 'pulumi up' would delete the resource,
the command will fail if this field is set to "PREVENT" in Terraform state.
When set to "ABANDON", the command will remove the resource from Terraform
management without updating or deleting the resource in the API.
When set to "DELETE", deleting the resource is allowed.[description](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_description_java/index.html)StringAn optional human-readable description of this notification channel. This description may provide additional details, beyond the display name, for the channel. This may not exceed 1024 Unicode characters.[displayName](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_displayname_java/index.html)StringAn optional human-readable name for this notification channel. It is recommended that you specify a non-empty and unique name in order to make it easier to identify the channels in your project, though this is not enforced. The display name is limited to 512 Unicode characters.[enabled](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_enabled_java/index.html)BooleanWhether notifications are forwarded to the described channel. This makes it possible to disable delivery of notifications to a particular channel without removing the channel from all alerting policies that reference the channel. This is a more convenient approach when the change is temporary and you want to receive notifications from the same set of alerting policies on the channel at some point in the future.[forceDelete](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_forcedelete_java/index.html)BooleanIf true, the notification channel will be deleted regardless
of its use in alert policies (the policies will be updated
to remove the channel). If false, channels that are still
referenced by an existing alerting policy will fail to be
deleted in a delete operation.[labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_labels_java/index.html)Map<String,String>Configuration fields that define the channel and its behavior. The
permissible and required labels are specified in the
NotificationChannelDescriptor corresponding to the type field.
Labels with sensitive data are obfuscated by the API and therefore the provider cannot
determine if there are upstream changes to these fields. They can also be configured via
the sensitiveLabels block, but cannot be configured in both places.[name](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_name_java/index.html)StringThe full REST resource name for this channel. The syntax is:
projects/\[PROJECT\_ID\]/notificationChannels/\[CHANNEL\_ID\]
The \[CHANNEL\_ID\] is automatically assigned by the server on creation.[project](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_project_java/index.html)Changes to this property will trigger replacement.StringThe ID of the project in which the resource belongs.
If it is not provided, the provider project is used.[sensitiveLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_sensitivelabels_java/index.html)[NotificationChannelSensitiveLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#notificationchannelsensitivelabels/index.html)Different notification type behaviors are configured primarily using the the `labels` field on this
resource. This block contains the labels which contain secrets or passwords so that they can be marked
sensitive and hidden from plan output. The name of the field, eg: password, will be the key
in the `labels` map in the api request.
Credentials may not be specified in both locations and will cause an error. Changing from one location
to a different credential configuration in the config will require an apply to update state.
Structure is documented below.[type](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_type_java/index.html)StringThe type of the notification channel. This field matches the value of the NotificationChannelDescriptor.type field. See https://cloud.google.com/monitoring/api/ref\_v3/rest/v3/projects.notificationChannelDescriptors/list to get the list of valid values such as "email", "slack", etc...[userLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_userlabels_java/index.html)Map<String,String>User-supplied key/value data that does not need to conform to the corresponding NotificationChannelDescriptor's schema, unlike the labels field. This field is intended to be used for organizing and identifying the NotificationChannel objects.The field can contain up to 64 entries. Each key and value is limited to 63 Unicode characters or 128 bytes, whichever is smaller. Labels and values can contain only lowercase letters, numerals, underscores, and dashes. Keys must begin with a letter.[verificationStatus](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_verificationstatus_java/index.html)StringIndicates whether this channel has been verified or not. On a ListNotificationChannels or GetNotificationChannel operation, this field is expected to be populated.If the value is UNVERIFIED, then it indicates that the channel is non-functioning (it both requires verification and lacks verification); otherwise, it is assumed that the channel works.If the channel is neither VERIFIED nor UNVERIFIED, it implies that the channel is of a type that does not require verification or that this specific channel has been exempted from verification because it was created prior to verification being required for channels of this type.This field cannot be modified using a standard UpdateNotificationChannel operation. To change the value of this field, you must call VerifyNotificationChannel.

[deletionPolicy](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_deletionpolicy_nodejs/index.html)stringWhether Terraform will be prevented from destroying the resource. Defaults to DELETE.
When a 'terraform destroy' or 'pulumi up' would delete the resource,
the command will fail if this field is set to "PREVENT" in Terraform state.
When set to "ABANDON", the command will remove the resource from Terraform
management without updating or deleting the resource in the API.
When set to "DELETE", deleting the resource is allowed.[description](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_description_nodejs/index.html)stringAn optional human-readable description of this notification channel. This description may provide additional details, beyond the display name, for the channel. This may not exceed 1024 Unicode characters.[displayName](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_displayname_nodejs/index.html)stringAn optional human-readable name for this notification channel. It is recommended that you specify a non-empty and unique name in order to make it easier to identify the channels in your project, though this is not enforced. The display name is limited to 512 Unicode characters.[enabled](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_enabled_nodejs/index.html)booleanWhether notifications are forwarded to the described channel. This makes it possible to disable delivery of notifications to a particular channel without removing the channel from all alerting policies that reference the channel. This is a more convenient approach when the change is temporary and you want to receive notifications from the same set of alerting policies on the channel at some point in the future.[forceDelete](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_forcedelete_nodejs/index.html)booleanIf true, the notification channel will be deleted regardless
of its use in alert policies (the policies will be updated
to remove the channel). If false, channels that are still
referenced by an existing alerting policy will fail to be
deleted in a delete operation.[labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_labels_nodejs/index.html){\[key: string\]: string}Configuration fields that define the channel and its behavior. The
permissible and required labels are specified in the
NotificationChannelDescriptor corresponding to the type field.
Labels with sensitive data are obfuscated by the API and therefore the provider cannot
determine if there are upstream changes to these fields. They can also be configured via
the sensitiveLabels block, but cannot be configured in both places.[name](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_name_nodejs/index.html)stringThe full REST resource name for this channel. The syntax is:
projects/\[PROJECT\_ID\]/notificationChannels/\[CHANNEL\_ID\]
The \[CHANNEL\_ID\] is automatically assigned by the server on creation.[project](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_project_nodejs/index.html)Changes to this property will trigger replacement.stringThe ID of the project in which the resource belongs.
If it is not provided, the provider project is used.[sensitiveLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_sensitivelabels_nodejs/index.html)[NotificationChannelSensitiveLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#notificationchannelsensitivelabels/index.html)Different notification type behaviors are configured primarily using the the `labels` field on this
resource. This block contains the labels which contain secrets or passwords so that they can be marked
sensitive and hidden from plan output. The name of the field, eg: password, will be the key
in the `labels` map in the api request.
Credentials may not be specified in both locations and will cause an error. Changing from one location
to a different credential configuration in the config will require an apply to update state.
Structure is documented below.[type](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_type_nodejs/index.html)stringThe type of the notification channel. This field matches the value of the NotificationChannelDescriptor.type field. See https://cloud.google.com/monitoring/api/ref\_v3/rest/v3/projects.notificationChannelDescriptors/list to get the list of valid values such as "email", "slack", etc...[userLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_userlabels_nodejs/index.html){\[key: string\]: string}User-supplied key/value data that does not need to conform to the corresponding NotificationChannelDescriptor's schema, unlike the labels field. This field is intended to be used for organizing and identifying the NotificationChannel objects.The field can contain up to 64 entries. Each key and value is limited to 63 Unicode characters or 128 bytes, whichever is smaller. Labels and values can contain only lowercase letters, numerals, underscores, and dashes. Keys must begin with a letter.[verificationStatus](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_verificationstatus_nodejs/index.html)stringIndicates whether this channel has been verified or not. On a ListNotificationChannels or GetNotificationChannel operation, this field is expected to be populated.If the value is UNVERIFIED, then it indicates that the channel is non-functioning (it both requires verification and lacks verification); otherwise, it is assumed that the channel works.If the channel is neither VERIFIED nor UNVERIFIED, it implies that the channel is of a type that does not require verification or that this specific channel has been exempted from verification because it was created prior to verification being required for channels of this type.This field cannot be modified using a standard UpdateNotificationChannel operation. To change the value of this field, you must call VerifyNotificationChannel.

[deletion\_policy](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_deletion_policy_python/index.html)strWhether Terraform will be prevented from destroying the resource. Defaults to DELETE.
When a 'terraform destroy' or 'pulumi up' would delete the resource,
the command will fail if this field is set to "PREVENT" in Terraform state.
When set to "ABANDON", the command will remove the resource from Terraform
management without updating or deleting the resource in the API.
When set to "DELETE", deleting the resource is allowed.[description](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_description_python/index.html)strAn optional human-readable description of this notification channel. This description may provide additional details, beyond the display name, for the channel. This may not exceed 1024 Unicode characters.[display\_name](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_display_name_python/index.html)strAn optional human-readable name for this notification channel. It is recommended that you specify a non-empty and unique name in order to make it easier to identify the channels in your project, though this is not enforced. The display name is limited to 512 Unicode characters.[enabled](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_enabled_python/index.html)boolWhether notifications are forwarded to the described channel. This makes it possible to disable delivery of notifications to a particular channel without removing the channel from all alerting policies that reference the channel. This is a more convenient approach when the change is temporary and you want to receive notifications from the same set of alerting policies on the channel at some point in the future.[force\_delete](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_force_delete_python/index.html)boolIf true, the notification channel will be deleted regardless
of its use in alert policies (the policies will be updated
to remove the channel). If false, channels that are still
referenced by an existing alerting policy will fail to be
deleted in a delete operation.[labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_labels_python/index.html)Mapping\[str, str\]Configuration fields that define the channel and its behavior. The
permissible and required labels are specified in the
NotificationChannelDescriptor corresponding to the type field.
Labels with sensitive data are obfuscated by the API and therefore the provider cannot
determine if there are upstream changes to these fields. They can also be configured via
the sensitiveLabels block, but cannot be configured in both places.[name](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_name_python/index.html)strThe full REST resource name for this channel. The syntax is:
projects/\[PROJECT\_ID\]/notificationChannels/\[CHANNEL\_ID\]
The \[CHANNEL\_ID\] is automatically assigned by the server on creation.[project](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_project_python/index.html)Changes to this property will trigger replacement.strThe ID of the project in which the resource belongs.
If it is not provided, the provider project is used.[sensitive\_labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_sensitive_labels_python/index.html)[NotificationChannelSensitiveLabelsArgs](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#notificationchannelsensitivelabels/index.html)Different notification type behaviors are configured primarily using the the `labels` field on this
resource. This block contains the labels which contain secrets or passwords so that they can be marked
sensitive and hidden from plan output. The name of the field, eg: password, will be the key
in the `labels` map in the api request.
Credentials may not be specified in both locations and will cause an error. Changing from one location
to a different credential configuration in the config will require an apply to update state.
Structure is documented below.[type](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_type_python/index.html)strThe type of the notification channel. This field matches the value of the NotificationChannelDescriptor.type field. See https://cloud.google.com/monitoring/api/ref\_v3/rest/v3/projects.notificationChannelDescriptors/list to get the list of valid values such as "email", "slack", etc...[user\_labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_user_labels_python/index.html)Mapping\[str, str\]User-supplied key/value data that does not need to conform to the corresponding NotificationChannelDescriptor's schema, unlike the labels field. This field is intended to be used for organizing and identifying the NotificationChannel objects.The field can contain up to 64 entries. Each key and value is limited to 63 Unicode characters or 128 bytes, whichever is smaller. Labels and values can contain only lowercase letters, numerals, underscores, and dashes. Keys must begin with a letter.[verification\_status](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_verification_status_python/index.html)strIndicates whether this channel has been verified or not. On a ListNotificationChannels or GetNotificationChannel operation, this field is expected to be populated.If the value is UNVERIFIED, then it indicates that the channel is non-functioning (it both requires verification and lacks verification); otherwise, it is assumed that the channel works.If the channel is neither VERIFIED nor UNVERIFIED, it implies that the channel is of a type that does not require verification or that this specific channel has been exempted from verification because it was created prior to verification being required for channels of this type.This field cannot be modified using a standard UpdateNotificationChannel operation. To change the value of this field, you must call VerifyNotificationChannel.

[deletionPolicy](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_deletionpolicy_yaml/index.html)StringWhether Terraform will be prevented from destroying the resource. Defaults to DELETE.
When a 'terraform destroy' or 'pulumi up' would delete the resource,
the command will fail if this field is set to "PREVENT" in Terraform state.
When set to "ABANDON", the command will remove the resource from Terraform
management without updating or deleting the resource in the API.
When set to "DELETE", deleting the resource is allowed.[description](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_description_yaml/index.html)StringAn optional human-readable description of this notification channel. This description may provide additional details, beyond the display name, for the channel. This may not exceed 1024 Unicode characters.[displayName](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_displayname_yaml/index.html)StringAn optional human-readable name for this notification channel. It is recommended that you specify a non-empty and unique name in order to make it easier to identify the channels in your project, though this is not enforced. The display name is limited to 512 Unicode characters.[enabled](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_enabled_yaml/index.html)BooleanWhether notifications are forwarded to the described channel. This makes it possible to disable delivery of notifications to a particular channel without removing the channel from all alerting policies that reference the channel. This is a more convenient approach when the change is temporary and you want to receive notifications from the same set of alerting policies on the channel at some point in the future.[forceDelete](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_forcedelete_yaml/index.html)BooleanIf true, the notification channel will be deleted regardless
of its use in alert policies (the policies will be updated
to remove the channel). If false, channels that are still
referenced by an existing alerting policy will fail to be
deleted in a delete operation.[labels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_labels_yaml/index.html)Map<String>Configuration fields that define the channel and its behavior. The
permissible and required labels are specified in the
NotificationChannelDescriptor corresponding to the type field.
Labels with sensitive data are obfuscated by the API and therefore the provider cannot
determine if there are upstream changes to these fields. They can also be configured via
the sensitiveLabels block, but cannot be configured in both places.[name](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_name_yaml/index.html)StringThe full REST resource name for this channel. The syntax is:
projects/\[PROJECT\_ID\]/notificationChannels/\[CHANNEL\_ID\]
The \[CHANNEL\_ID\] is automatically assigned by the server on creation.[project](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_project_yaml/index.html)Changes to this property will trigger replacement.StringThe ID of the project in which the resource belongs.
If it is not provided, the provider project is used.[sensitiveLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_sensitivelabels_yaml/index.html)[Property Map](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#notificationchannelsensitivelabels/index.html)Different notification type behaviors are configured primarily using the the `labels` field on this
resource. This block contains the labels which contain secrets or passwords so that they can be marked
sensitive and hidden from plan output. The name of the field, eg: password, will be the key
in the `labels` map in the api request.
Credentials may not be specified in both locations and will cause an error. Changing from one location
to a different credential configuration in the config will require an apply to update state.
Structure is documented below.[type](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_type_yaml/index.html)StringThe type of the notification channel. This field matches the value of the NotificationChannelDescriptor.type field. See https://cloud.google.com/monitoring/api/ref\_v3/rest/v3/projects.notificationChannelDescriptors/list to get the list of valid values such as "email", "slack", etc...[userLabels](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_userlabels_yaml/index.html)Map<String>User-supplied key/value data that does not need to conform to the corresponding NotificationChannelDescriptor's schema, unlike the labels field. This field is intended to be used for organizing and identifying the NotificationChannel objects.The field can contain up to 64 entries. Each key and value is limited to 63 Unicode characters or 128 bytes, whichever is smaller. Labels and values can contain only lowercase letters, numerals, underscores, and dashes. Keys must begin with a letter.[verificationStatus](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#state_verificationstatus_yaml/index.html)StringIndicates whether this channel has been verified or not. On a ListNotificationChannels or GetNotificationChannel operation, this field is expected to be populated.If the value is UNVERIFIED, then it indicates that the channel is non-functioning (it both requires verification and lacks verification); otherwise, it is assumed that the channel works.If the channel is neither VERIFIED nor UNVERIFIED, it implies that the channel is of a type that does not require verification or that this specific channel has been exempted from verification because it was created prior to verification being required for channels of this type.This field cannot be modified using a standard UpdateNotificationChannel operation. To change the value of this field, you must call VerifyNotificationChannel.

## Supporting Types [Anchor](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/\#supporting-types/index.html)

#### NotificationChannelSensitiveLabels  , NotificationChannelSensitiveLabelsArgs   [Anchor](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/\#notificationchannelsensitivelabels/index.html)

[AuthToken](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#authtoken_csharp/index.html)stringAn authorization token for a notification channel. Channel types that support this field include: slack
**Note**: This property is sensitive and will not be displayed in the plan.[AuthTokenWo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#authtokenwo_csharp/index.html)string

**NOTE:** This field is write-only and its value will not be updated in state as part of read operations.
(Optional, Write-Only)
An authorization token for a notification channel. Channel types that support this field include: slack
**Note**: This property is write-only and will not be read from the API.

> **Note:** One of `authToken` or `authTokenWo` can only be set.

[AuthTokenWoVersion](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#authtokenwoversion_csharp/index.html)stringTriggers update of `authTokenWo` write-only. Increment this value when an update to `authTokenWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)[Password](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#password_csharp/index.html)stringAn password for a notification channel. Channel types that support this field include: webhookBasicauth
**Note**: This property is sensitive and will not be displayed in the plan.[PasswordWo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#passwordwo_csharp/index.html)string

**NOTE:** This field is write-only and its value will not be updated in state as part of read operations.
(Optional, Write-Only)
An password for a notification channel. Channel types that support this field include: webhookBasicauth
**Note**: This property is write-only and will not be read from the API.

> **Note:** One of `password` or `passwordWo` can only be set.

[PasswordWoVersion](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#passwordwoversion_csharp/index.html)stringTriggers update of `passwordWo` write-only. Increment this value when an update to `passwordWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)[ServiceKey](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#servicekey_csharp/index.html)stringAn servicekey token for a notification channel. Channel types that support this field include: pagerduty
**Note**: This property is sensitive and will not be displayed in the plan.[ServiceKeyWo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#servicekeywo_csharp/index.html)string

**NOTE:** This field is write-only and its value will not be updated in state as part of read operations.
(Optional, Write-Only)
An servicekey token for a notification channel. Channel types that support this field include: pagerduty
**Note**: This property is write-only and will not be read from the API.

> **Note:** One of `serviceKey` or `serviceKeyWo` can only be set.

[ServiceKeyWoVersion](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#servicekeywoversion_csharp/index.html)stringTriggers update of `serviceKeyWo` write-only. Increment this value when an update to `serviceKeyWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)

[AuthToken](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#authtoken_go/index.html)stringAn authorization token for a notification channel. Channel types that support this field include: slack
**Note**: This property is sensitive and will not be displayed in the plan.[AuthTokenWo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#authtokenwo_go/index.html)string

> **Note:** One of `authToken` or `authTokenWo` can only be set.

[AuthTokenWoVersion](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#authtokenwoversion_go/index.html)stringTriggers update of `authTokenWo` write-only. Increment this value when an update to `authTokenWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)[Password](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#password_go/index.html)stringAn password for a notification channel. Channel types that support this field include: webhookBasicauth
**Note**: This property is sensitive and will not be displayed in the plan.[PasswordWo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#passwordwo_go/index.html)string

> **Note:** One of `password` or `passwordWo` can only be set.

[PasswordWoVersion](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#passwordwoversion_go/index.html)stringTriggers update of `passwordWo` write-only. Increment this value when an update to `passwordWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)[ServiceKey](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#servicekey_go/index.html)stringAn servicekey token for a notification channel. Channel types that support this field include: pagerduty
**Note**: This property is sensitive and will not be displayed in the plan.[ServiceKeyWo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#servicekeywo_go/index.html)string

> **Note:** One of `serviceKey` or `serviceKeyWo` can only be set.

[ServiceKeyWoVersion](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#servicekeywoversion_go/index.html)stringTriggers update of `serviceKeyWo` write-only. Increment this value when an update to `serviceKeyWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)

[auth\_token](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#auth_token_hcl/index.html)stringAn authorization token for a notification channel. Channel types that support this field include: slack
**Note**: This property is sensitive and will not be displayed in the plan.[auth\_token\_wo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#auth_token_wo_hcl/index.html)string

> **Note:** One of `authToken` or `authTokenWo` can only be set.

[auth\_token\_wo\_version](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#auth_token_wo_version_hcl/index.html)stringTriggers update of `authTokenWo` write-only. Increment this value when an update to `authTokenWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)[password](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#password_hcl/index.html)stringAn password for a notification channel. Channel types that support this field include: webhookBasicauth
**Note**: This property is sensitive and will not be displayed in the plan.[password\_wo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#password_wo_hcl/index.html)string

> **Note:** One of `password` or `passwordWo` can only be set.

[password\_wo\_version](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#password_wo_version_hcl/index.html)stringTriggers update of `passwordWo` write-only. Increment this value when an update to `passwordWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)[service\_key](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#service_key_hcl/index.html)stringAn servicekey token for a notification channel. Channel types that support this field include: pagerduty
**Note**: This property is sensitive and will not be displayed in the plan.[service\_key\_wo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#service_key_wo_hcl/index.html)string

> **Note:** One of `serviceKey` or `serviceKeyWo` can only be set.

[service\_key\_wo\_version](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#service_key_wo_version_hcl/index.html)stringTriggers update of `serviceKeyWo` write-only. Increment this value when an update to `serviceKeyWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)

[authToken](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#authtoken_java/index.html)StringAn authorization token for a notification channel. Channel types that support this field include: slack
**Note**: This property is sensitive and will not be displayed in the plan.[authTokenWo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#authtokenwo_java/index.html)String

> **Note:** One of `authToken` or `authTokenWo` can only be set.

[authTokenWoVersion](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#authtokenwoversion_java/index.html)StringTriggers update of `authTokenWo` write-only. Increment this value when an update to `authTokenWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)[password](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#password_java/index.html)StringAn password for a notification channel. Channel types that support this field include: webhookBasicauth
**Note**: This property is sensitive and will not be displayed in the plan.[passwordWo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#passwordwo_java/index.html)String

> **Note:** One of `password` or `passwordWo` can only be set.

[passwordWoVersion](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#passwordwoversion_java/index.html)StringTriggers update of `passwordWo` write-only. Increment this value when an update to `passwordWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)[serviceKey](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#servicekey_java/index.html)StringAn servicekey token for a notification channel. Channel types that support this field include: pagerduty
**Note**: This property is sensitive and will not be displayed in the plan.[serviceKeyWo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#servicekeywo_java/index.html)String

> **Note:** One of `serviceKey` or `serviceKeyWo` can only be set.

[serviceKeyWoVersion](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#servicekeywoversion_java/index.html)StringTriggers update of `serviceKeyWo` write-only. Increment this value when an update to `serviceKeyWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)

[authToken](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#authtoken_nodejs/index.html)stringAn authorization token for a notification channel. Channel types that support this field include: slack
**Note**: This property is sensitive and will not be displayed in the plan.[authTokenWo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#authtokenwo_nodejs/index.html)string

> **Note:** One of `authToken` or `authTokenWo` can only be set.

[authTokenWoVersion](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#authtokenwoversion_nodejs/index.html)stringTriggers update of `authTokenWo` write-only. Increment this value when an update to `authTokenWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)[password](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#password_nodejs/index.html)stringAn password for a notification channel. Channel types that support this field include: webhookBasicauth
**Note**: This property is sensitive and will not be displayed in the plan.[passwordWo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#passwordwo_nodejs/index.html)string

> **Note:** One of `password` or `passwordWo` can only be set.

[passwordWoVersion](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#passwordwoversion_nodejs/index.html)stringTriggers update of `passwordWo` write-only. Increment this value when an update to `passwordWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)[serviceKey](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#servicekey_nodejs/index.html)stringAn servicekey token for a notification channel. Channel types that support this field include: pagerduty
**Note**: This property is sensitive and will not be displayed in the plan.[serviceKeyWo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#servicekeywo_nodejs/index.html)string

> **Note:** One of `serviceKey` or `serviceKeyWo` can only be set.

[serviceKeyWoVersion](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#servicekeywoversion_nodejs/index.html)stringTriggers update of `serviceKeyWo` write-only. Increment this value when an update to `serviceKeyWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)

[auth\_token](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#auth_token_python/index.html)strAn authorization token for a notification channel. Channel types that support this field include: slack
**Note**: This property is sensitive and will not be displayed in the plan.[auth\_token\_wo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#auth_token_wo_python/index.html)str

> **Note:** One of `authToken` or `authTokenWo` can only be set.

[auth\_token\_wo\_version](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#auth_token_wo_version_python/index.html)strTriggers update of `authTokenWo` write-only. Increment this value when an update to `authTokenWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)[password](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#password_python/index.html)strAn password for a notification channel. Channel types that support this field include: webhookBasicauth
**Note**: This property is sensitive and will not be displayed in the plan.[password\_wo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#password_wo_python/index.html)str

> **Note:** One of `password` or `passwordWo` can only be set.

[password\_wo\_version](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#password_wo_version_python/index.html)strTriggers update of `passwordWo` write-only. Increment this value when an update to `passwordWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)[service\_key](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#service_key_python/index.html)strAn servicekey token for a notification channel. Channel types that support this field include: pagerduty
**Note**: This property is sensitive and will not be displayed in the plan.[service\_key\_wo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#service_key_wo_python/index.html)str

> **Note:** One of `serviceKey` or `serviceKeyWo` can only be set.

[service\_key\_wo\_version](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#service_key_wo_version_python/index.html)strTriggers update of `serviceKeyWo` write-only. Increment this value when an update to `serviceKeyWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)

[authToken](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#authtoken_yaml/index.html)StringAn authorization token for a notification channel. Channel types that support this field include: slack
**Note**: This property is sensitive and will not be displayed in the plan.[authTokenWo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#authtokenwo_yaml/index.html)String

> **Note:** One of `authToken` or `authTokenWo` can only be set.

[authTokenWoVersion](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#authtokenwoversion_yaml/index.html)StringTriggers update of `authTokenWo` write-only. Increment this value when an update to `authTokenWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)[password](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#password_yaml/index.html)StringAn password for a notification channel. Channel types that support this field include: webhookBasicauth
**Note**: This property is sensitive and will not be displayed in the plan.[passwordWo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#passwordwo_yaml/index.html)String

> **Note:** One of `password` or `passwordWo` can only be set.

[passwordWoVersion](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#passwordwoversion_yaml/index.html)StringTriggers update of `passwordWo` write-only. Increment this value when an update to `passwordWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)[serviceKey](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#servicekey_yaml/index.html)StringAn servicekey token for a notification channel. Channel types that support this field include: pagerduty
**Note**: This property is sensitive and will not be displayed in the plan.[serviceKeyWo](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#servicekeywo_yaml/index.html)String

> **Note:** One of `serviceKey` or `serviceKeyWo` can only be set.

[serviceKeyWoVersion](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/#servicekeywoversion_yaml/index.html)StringTriggers update of `serviceKeyWo` write-only. Increment this value when an update to `serviceKeyWo` is needed. For more info see [updating write-only arguments](https://www.terraform.io/docs/providers/google/guides/using_write_only_arguments.html#updating-write-only-arguments)

## Import [Anchor](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/\#import/index.html)

NotificationChannel can be imported using any of these accepted formats:

- `{{name}}`

When using the `pulumi import` command, NotificationChannel can be imported using one of the formats above. For example:

```sh
$ pulumi import gcp:monitoring/notificationChannel:NotificationChannel default {{name}}
```

Copy

To learn more about importing existing cloud resources, see [Importing resources](/content/docs/using-pulumi/adopting-pulumi/import/index.html).

## Package Details [Anchor](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/\#package-details/index.html)

Viewing docs for Google Cloud v9.26.0

published on Tuesday, Jun 9, 2026 by Pulumi

[Schema (JSON)](/content/registry/packages/gcp/schema.json)

[pulumi/pulumi-gcp](https://github.com/pulumi/pulumi-gcp)

v9.26.0 (9.x, latest)v8.41.1 (8.x)v7.38.0 (7.x)

## On this page

## On this page

* * *

Related Resources

[monitoring.AlertPolicy](/content/registry/packages/gcp/api-docs/monitoring/alertpolicy/index.html)

[billing.Budget](/content/registry/packages/gcp/api-docs/billing/budget/index.html)

[secretmanager.SecretIamBinding](/content/registry/packages/gcp/api-docs/secretmanager/secretiambinding/index.html)

[organizations.Project](/content/registry/packages/gcp/api-docs/organizations/project/index.html)

[projects.Service](/content/registry/packages/gcp/api-docs/projects/service/index.html)

- Copy Page

[Scroll to top](/content/registry/packages/gcp/api-docs/monitoring/notificationchannel/# "Scroll to top"/index.html)

#### Try Pulumi Cloud free.  Your team will thank you.

[Start free trial](https://app.pulumi.com/signup?utm_source=registry&utm_medium=right-rail-banner&utm_campaign=try-pulumi-cloud&iaid=docs-try-pulumi-cloud-ad)