Data Sources
uptimeify_notification_channel
Look up one notification channel by id or by name (exactly one). Fails when no or several channels carry the name. Secrets are never returned (see secrets_set). Website overrides are not found by name.
Look up one notification channel by id or by name (exactly one). Fails when no or several channels carry the name. Secrets are never returned (see secrets_set). Website overrides are not found by name.
Example Usage
data "uptimeify_notification_channel" "ops" {
name = "Ops mail"
}
data "uptimeify_notification_channel" "by_id" {
id = "42"
}Schema
Optional
customer_id(Number) Withname: search this customer's channels too (default: organization channels only).id(String) Numeric channel id.name(String)
Read-Only
allowed_package_types(Set of String)category(String)direct(default) orintegration.conditions(String) Delivery conditions as a JSON object. Unset = always.config(String) Provider settings without secrets, as a JSON object (jsonencode({ email = "ops@example.com" })). Keys removed here are cleared.created_at(String)delay_seconds(Number) Wait before sending, 0 to 86400 seconds.is_active(Boolean)organization_id(Number)secrets_set(Map of Boolean) Which secrets are stored, e.g.{ Secret = true }(the API'shas<Secret>flags).type(String) Channel type:email,sms,webhook,incident_management,slack,discord,teams,pagerduty,pushover,opsgenie,matrix,jira,allquiet,telegram,googlechat,mattermost,rocketchat,ntfy,gotify,ilert,grafanaoncall,incidentio,squadcast,github,gitlab,linear,servicenow,lark,dingtalk,wecom.