Confirm Snowflake session context after production deploys
A release can involve multiple environments and warehouse configurations. After GitHub marks a production deployment successful, Notis can run a small read-only query and report the Snowflake session context for a quick follow-up.
Trigger
New Deployment Status Created
Triggers when a new deployment status is created for a specific deployment. Fires an event for each newly created deployment status on the monitored deployment. Deployment statuses represent state transitions such as pending, in_progress, success, failure, error, inactive, and queued. The payload includes the status state, creator, environment, description, timestamps, and relevant URLs.
Action
Execute SQL
Tool to execute a sql statement and return the resulting data. use when you need to query data from snowflake.
Why this helps
It is easy to lose track of which Snowflake context a connected session is using when switching between a release and analytics work.
- See the connected session's current database, schema, and warehouse after a release.
- Keep the context check attached to a successful production deployment report.
- Use a read-only query without assuming a project-specific table exists.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Snowflake to Notis once in the portal.
- 2Create an automation in the portal and describe the read-only session-context query and report you want in one plain-language prompt.
- 3Choose the GitHub deployment-status trigger, select where run reports should go, and ask Notis to run only for successful production deployments.
- 4Test with one successful production deployment and confirm the query result is reported.
Questions about this workflow
Does this verify the deployed product's data or application health?
No. It runs a read-only query for Snowflake session context. It does not test application behavior, inspect project tables, or prove that production data is correct.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Snowflake. A trigger fires from one place; an action lands in another.
GitHub triggers
Snowflake actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Cancel Statement Execution
Cancels the execution of a running sql statement. use this action to stop a long-running query.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Execute SQL
Tool to execute a sql statement and return the resulting data. use when you need to query data from snowflake.
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Fetch Catalog Integration
Fetches details of a specific catalog integration.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Get Active Scheduled Maintenances
Retrieves a list of any active scheduled maintenances currently in the in progress or verifying state.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get All Scheduled Maintenances
Retrieves a list of the 50 most recent scheduled maintenances, including those in the completed state.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Get Component Status
Retrieves the status of individual components, each listed with its current status.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Get Status Rollup
Retrieves the status rollup for the entire page, including indicators and human-readable descriptions of the blended component status.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Get Status Summary
Retrieves a summary of the status page, including status indicators, component statuses, unresolved incidents, and upcoming or in-progress scheduled maintenances.
Connect any two apps with Notis in the middle.
GitHub and Snowflake, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Snowflake.