Skip to main content

Connecting OpCon to Snowflake Using the Web Services Connector

  • June 12, 2026
  • 0 replies
  • 3 views

AndreaDowning
Forum|alt.badge.img

OpCon does not include a native Snowflake integration out of the box. However, because Snowflake exposes a widely supported SQL API, you can build an automated connection using the OpCon Web Services Connector. This article walks you through the prerequisites and steps needed to get your environment set up and executing SQL statements against Snowflake as OpCon jobs.

Prerequisites

Before getting started, make sure the following are in place:

  • OpCon version 18.3 or higher
  • Web Services Connector version 20.1 or higher (recommended)
  • Access to the Snowflake SQL API (documentation available at https://docs.snowflake.com/en/developer-guide/sql-api/index)
  • A Snowflake authorization token, stored as an encrypted global property in OpCon
  • A base URL for your Snowflake environment, stored as a standard global property

If you have not yet installed the Web Services Connector, contact support to receive the install files and assistance with the installation process. The connector documentation is available here: https://help.smatechnologies.com/opcon/connectors/webservices

How It Works

Once the Web Services Connector is installed, a new job subtype becomes available in OpCon called Web Services. This subtype allows you to configure multi-step API calls as a single OpCon job, which is the key to automating Snowflake SQL execution.

Continuous has published a ready-to-use Snowflake SQL Web Services template on GitHub to make this process faster. The template is available here:

https://github.com/smatechnologies/snowflakesql-webservicestemplate/blob/master/README.md

Setting Up the Integration

Step 1: Prepare Your Local Properties

Before importing the template, set up the following global properties in OpCon:

  • @snowflakesqltoken - Your Snowflake SQL API authorization token. This value is sensitive and must be stored as an encrypted global property.
  • @baseURL - The base URL used to communicate with the Snowflake SQL API, stored as a standard global property.
  • @uuid - A unique identifier for each API call. A common approach is to use the built-in OpCon expression [[$TIME HHMMSS]] to generate a time-based value automatically.

Step 2: Install the Web Services Connector

Download the template from the GitHub repository linked above and import it into a new Web Services Connector job in OpCon. The template includes three pre-configured steps:

  1. Submits a SQL statement to Snowflake for execution.
  2. Checks the execution status of that statement and returns the result set.
  3. Cancels the execution of the statement if needed.

These three steps cover the full lifecycle of a Snowflake SQL call and can be used as a foundation for building more complex automation workflows around your Snowflake data.

Notes and Limitations

This template is provided as a starting point. Continuous does not provide formal support or warranty for the GitHub template itself, though the Web Services Connector and OpCon platform are fully supported products. For questions about customizing the template for your specific use case, contact customer support.

Additional Resources