Snowflake · Arazzo Workflow

Snowflake Create and Execute an Alert

Version 1.0.0

Create an alert with a condition and action, describe it, then execute it on demand.

1 workflow 1 source API 1 provider
View Spec View on GitHub DataData WarehouseData LakehouseCloud Data PlatformAnalyticsArtificial IntelligenceData EngineeringData GovernanceSQLApache IcebergModel Context ProtocolT1ArazzoWorkflows

Provider

snowflake

Workflows

create-and-execute-alert
Create an alert, fetch it to confirm, then execute it on demand.
Chains createAlert, fetchAlert, and executeAlert so an alert is provisioned with a condition and action, verified, and run once on demand, all scoped to the same database and schema.
3 steps inputs: action, alertName, authToken, comment, condition, databaseName, schedule, schemaName, tokenType, warehouse outputs: alertState, createStatus, executeStatus
1
createAlert
Create the alert with its condition, action, warehouse, and schedule.
2
fetchAlert
Describe the alert to confirm it was created.
3
executeAlert
Execute the alert immediately rather than waiting for its schedule.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Snowflake Create and Execute an Alert
  summary: Create an alert with a condition and action, describe it, then execute it on demand.
  description: >-
    Alerting flow for Snowflake. The workflow creates an alert that runs a
    condition query on a schedule and performs an action when the condition is
    met, describes the alert to confirm creation, and then executes the alert
    immediately rather than waiting for its schedule. Each step inlines its
    Authorization bearer token and the X-Snowflake-Authorization-Token-Type
    header, its create-mode query parameter, and its JSON request body where
    applicable so the chain can be read and executed without opening the
    underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: alertApi
  url: ../openapi/snowflake-alert-api-openapi.yml
  type: openapi
workflows:
- workflowId: create-and-execute-alert
  summary: Create an alert, fetch it to confirm, then execute it on demand.
  description: >-
    Chains createAlert, fetchAlert, and executeAlert so an alert is provisioned
    with a condition and action, verified, and run once on demand, all scoped to
    the same database and schema.
  inputs:
    type: object
    required:
    - authToken
    - databaseName
    - schemaName
    - alertName
    - warehouse
    - condition
    - action
    properties:
      authToken:
        type: string
        description: Bearer token (KEYPAIR_JWT, OAUTH, or programmatic access token).
      tokenType:
        type: string
        description: Value for the X-Snowflake-Authorization-Token-Type header.
        default: OAUTH
      databaseName:
        type: string
        description: Database that holds the schema and alert.
      schemaName:
        type: string
        description: Schema that holds the alert.
      alertName:
        type: string
        description: Name of the alert to create.
      warehouse:
        type: string
        description: Warehouse used to evaluate the alert condition and action.
      condition:
        type: string
        description: The SQL condition that triggers the alert.
      action:
        type: string
        description: The SQL action performed when the condition is met.
      schedule:
        type: object
        description: The schedule object controlling how often the alert is evaluated.
      comment:
        type: string
        description: Optional comment applied to the alert.
  steps:
  - stepId: createAlert
    description: Create the alert with its condition, action, warehouse, and schedule.
    operationId: createAlert
    parameters:
    - name: database
      in: path
      value: $inputs.databaseName
    - name: schema
      in: path
      value: $inputs.schemaName
    - name: createMode
      in: query
      value: errorIfExists
    - name: Authorization
      in: header
      value: Bearer $inputs.authToken
    - name: X-Snowflake-Authorization-Token-Type
      in: header
      value: $inputs.tokenType
    requestBody:
      contentType: application/json
      payload:
        name: $inputs.alertName
        warehouse: $inputs.warehouse
        condition: $inputs.condition
        action: $inputs.action
        schedule: $inputs.schedule
        comment: $inputs.comment
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      status: $response.body#/status
  - stepId: fetchAlert
    description: Describe the alert to confirm it was created.
    operationId: fetchAlert
    parameters:
    - name: database
      in: path
      value: $inputs.databaseName
    - name: schema
      in: path
      value: $inputs.schemaName
    - name: name
      in: path
      value: $inputs.alertName
    - name: Authorization
      in: header
      value: Bearer $inputs.authToken
    - name: X-Snowflake-Authorization-Token-Type
      in: header
      value: $inputs.tokenType
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      alertName: $response.body#/name
      state: $response.body#/state
  - stepId: executeAlert
    description: Execute the alert immediately rather than waiting for its schedule.
    operationId: executeAlert
    parameters:
    - name: database
      in: path
      value: $inputs.databaseName
    - name: schema
      in: path
      value: $inputs.schemaName
    - name: name
      in: path
      value: $inputs.alertName
    - name: Authorization
      in: header
      value: Bearer $inputs.authToken
    - name: X-Snowflake-Authorization-Token-Type
      in: header
      value: $inputs.tokenType
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      status: $response.body#/status
  outputs:
    createStatus: $steps.createAlert.outputs.status
    alertState: $steps.fetchAlert.outputs.state
    executeStatus: $steps.executeAlert.outputs.status

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/snowflake-create-and-execute-alert-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.