SHOW NOTIFICATION INTEGRATIONS¶
Lists the notification integrations in your account.
The output includes metadata and properties of each notification integration.
- See also:
CREATE NOTIFICATION INTEGRATION , ALTER NOTIFICATION INTEGRATION , DESCRIBE NOTIFICATION INTEGRATION, DROP INTEGRATION
Syntax¶
SHOW NOTIFICATION INTEGRATIONS [ LIKE '<pattern>' ]
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).
Output¶
The output of the command includes the following columns, which describe the properties and metadata of the object:
Column |
Description |
---|---|
|
Name of the notification integration. |
|
Type of the notification integration. The value can be one of the following:
|
|
Category of the integration. For notification integrations, this is always |
|
Indicates whether or not the notification integration is enabled:
|
|
Comment for the notification integration. |
|
Date and time when the notification integration was created. |
|
Indicates whether the integration supports sending or receiving notifications. The value can be one of the following:
|
Access control requirements¶
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 RESULT_SCAN function, which treats the output as a table that can be queried.
Examples¶
Show all notification integrations:
SHOW NOTIFICATION INTEGRATIONS;
+-----------------------------+-----------------------------+--------------+---------+---------+-------------------------------+-----------+
| 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 |
+-----------------------------+-----------------------------+--------------+---------+---------+-------------------------------+-----------+