Lists the notification integrations in your account.
The output includes metadata and properties of each notification integration.
CREATE NOTIFICATION INTEGRATION , ALTER NOTIFICATION INTEGRATION , DESCRIBE NOTIFICATION INTEGRATION, DROP INTEGRATION
SHOW NOTIFICATION INTEGRATIONS [ LIKE '<pattern>' ]
Copy
Parameters¶LIKE 'pattern'
Optionally filters the command output by object name. The filter uses case-insensitive pattern matching, with support for SQL wildcard characters (% and _).
For example, the following patterns return the same results:
... LIKE '%testing%' ...
... LIKE '%TESTING%' ...
. Default: No value (no filtering is applied to the output).
The output of the command includes the following columns, which describe the properties and metadata of the object:
Column
Description
name
Name of the notification integration.
type
Type of the notification integration. The value can be one of the following:
QUEUE - AZURE_STORAGE_QUEUE: For inbound notifications from Azure Event Grid topics.
QUEUE - GCP_PUBSUB: For inbound and outbound notifications to and from Google Pub/Sub topics.
QUEUE - AWS_SNS: For outbound notifications to Amazon SNS topics.
QUEUE - AZURE_EVENT_GRID: For outbound notifications to Azure Event Grid topics.
EMAIL: For email notifications.
WEBHOOK: For webhook notifications.
category
Category of the integration. For notification integrations, this is always NOTIFICATION.
enabled
Indicates whether or not the notification integration is enabled:
If true, the notification integration is enabled.
If false, the notification integration is disabled.
comment
Comment for the notification integration.
created_on
Date and time when the notification integration was created.
direction
Indicates whether the integration supports sending or receiving notifications. The value can be one of the following:
OUTBOUND: Snowflake uses the integration to send notifications to a third-party messaging service.
This value appears for notification integrations with any of the following properties:
TYPE=QUEUE and DIRECTION=OUTBOUND
TYPE=EMAIL
TYPE=WEBHOOK
INBOUND: Snowflake uses the integration to receive notifications from a third-party messaging service.
This value appears for notification integrations that do not specify DIRECTION=OUTBOUND.
A role used to execute this SQL command must have at least one of the following privileges at a minimum:
Privilege
Object
Notes
USAGE
Integration
OWNERSHIP
Integration
OWNERSHIP is a special privilege on an object that is automatically granted to the role that created the object, but can also be transferred using the GRANT OWNERSHIP command to a different role by the owning role (or any role with the MANAGE GRANTS privilege).
For instructions on creating a custom role with a specified set of privileges, see Creating custom roles.
For general information about roles and privilege grants for performing SQL actions on securable objects, see Overview of Access Control.
Usage notes¶The command does not require a running warehouse to execute.
To post-process the output of this command, you can use the pipe operator (->>) or the RESULT_SCAN function. Both constructs treat the output as a result set that you can query.
The output column names for this command are generated in lowercase. If you consume a result set from this command with the pipe operator or the RESULT_SCAN function, use double-quoted identifiers for the column names in the query to ensure that they match the column names in the output that was scanned. For example, if the name of an output column is type, then specify "type" for the identifier.
Show all notification integrations:
SHOW NOTIFICATION INTEGRATIONS;
Copy
+-----------------------------+-----------------------------+--------------+---------+---------+-------------------------------+-----------+ | name | type | category | enabled | comment | created_on | direction | |-----------------------------+-----------------------------+--------------+---------+---------+-------------------------------+-----------| | MY_AZURE_INBOUND_QUEUE_INT | QUEUE - AZURE_STORAGE_QUEUE | NOTIFICATION | true | NULL | 2025-03-08 11:34:55.861 -0800 | INBOUND | | MY_GCP_INBOUND_QUEUE_INT | QUEUE - GCP_PUBSUB | NOTIFICATION | true | NULL | 2025-03-08 11:35:35.163 -0800 | INBOUND | | MY_GCP_OUTBOUND_QUEUE_INT | QUEUE - GCP_PUBSUB | NOTIFICATION | true | NULL | 2025-03-08 11:37:06.487 -0800 | OUTBOUND | | MY_AWS_OUTBOUND_QUEUE_INT | QUEUE - AWS_SNS | NOTIFICATION | true | NULL | 2025-03-08 11:36:13.072 -0800 | OUTBOUND | | MY_EMAIL_INT | EMAIL | NOTIFICATION | true | NULL | 2025-03-08 11:38:55.866 -0800 | OUTBOUND | | MY_AZURE_OUTBOUND_QUEUE_INT | QUEUE - AZURE_EVENT_GRID | NOTIFICATION | true | NULL | 2025-03-08 11:36:40.822 -0800 | OUTBOUND | | MY_WEBHOOK_INT | WEBHOOK | NOTIFICATION | true | NULL | 2025-03-08 11:40:17.336 -0800 | OUTBOUND | +-----------------------------+-----------------------------+--------------+---------+---------+-------------------------------+-----------+
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4