Skip to main content

Supaflow in Snowflake CoCo for Snowsight

Connect Supaflow to Snowflake CoCo (formerly Cortex Code) inside Snowsight to inspect connections, prepare pipelines, and manage your data workflows through conversation.

Snowsight uses an external MCP connector and uploaded skills. Installing the CLI plugin does not configure the Snowsight connector.

Before You Begin​

You need a Supaflow account and access to Snowflake CoCo in Snowsight. A Snowflake administrator configures the connector and grants access to the intended role. Each user then authorizes their own Supaflow account.

Configure source and destination credentials in the Supaflow dashboard before creating a pipeline. Never paste credentials into a conversation.

Administrator: Configure the Connector​

The SQL below creates a public OAuth client connection without a client secret. The client ID is public and comes from the published Supaflow plugin configuration. Supaflow maintains the production OAuth client and its Snowflake callback; customers do not create a Clerk application or register that callback.

Use an existing database and schema that your organization has selected for MCP objects. These statements create new objects; inspect existing objects before reusing a name.

  1. In Snowsight, open Projects → Workspaces and create a SQL file.
  2. Select ACCOUNTADMIN in the SQL editor's role selector. This walkthrough uses ACCOUNTADMIN for the one-time setup; users connect afterward with the role you grant access to.
  3. Paste the SQL below. Replace YOUR_DATABASE.YOUR_SCHEMA with your approved database and schema, and YOUR_COCO_ROLE with the intended user role.
  4. Open the arrow beside Run and choose Run all.
USE ROLE ACCOUNTADMIN;

CREATE API INTEGRATION SUPAFLOW_COCO_WEB_OAUTH
API_PROVIDER = EXTERNAL_MCP
API_ALLOWED_PREFIXES = ('https://app.supa-flow.io/mcp')
API_USER_AUTHENTICATION = (
TYPE = OAUTH2
OAUTH_CLIENT_ID = 'gKvMIcc4J3CBXwbl'
OAUTH_CLIENT_AUTH_METHOD = NONE
OAUTH_AUTHORIZATION_ENDPOINT = 'https://clerk.supa-flow.io/oauth/authorize'
OAUTH_TOKEN_ENDPOINT = 'https://clerk.supa-flow.io/oauth/token'
OAUTH_RESOURCE = 'https://app.supa-flow.io/mcp'
OAUTH_ALLOWED_SCOPES = (
'email', 'profile', 'offline_access', 'user:org:read',
'supaflow:read', 'supaflow:write'
)
OAUTH_REFRESH_TOKEN_VALIDITY = 86400
)
ENABLED = TRUE;

CREATE EXTERNAL MCP SERVER YOUR_DATABASE.YOUR_SCHEMA.SUPAFLOW_COCO_WEB
WITH DISPLAY_NAME = 'Supaflow'
URL = 'https://app.supa-flow.io/mcp'
API_INTEGRATION = SUPAFLOW_COCO_WEB_OAUTH;

GRANT USAGE ON DATABASE YOUR_DATABASE TO ROLE YOUR_COCO_ROLE;
GRANT USAGE ON SCHEMA YOUR_DATABASE.YOUR_SCHEMA TO ROLE YOUR_COCO_ROLE;
GRANT USAGE ON INTEGRATION SUPAFLOW_COCO_WEB_OAUTH TO ROLE YOUR_COCO_ROLE;
GRANT USAGE ON EXTERNAL MCP SERVER YOUR_DATABASE.YOUR_SCHEMA.SUPAFLOW_COCO_WEB
TO ROLE YOUR_COCO_ROLE;

SHOW EXTERNAL MCP SERVERS IN SCHEMA YOUR_DATABASE.YOUR_SCHEMA;

Verify that the final result lists SUPAFLOW_COCO_WEB with SUPAFLOW_COCO_WEB_OAUTH as its API integration. The intended role needs access to the database, schema, external MCP server and API integration. Creating these objects makes the connector available; each user must still complete the connection and Supaflow authorization steps below.

The one-day refresh validity sets a finite reauthorization interval. Users may need to reconnect daily. The requested scopes include Supaflow reads and writes; a user's Supaflow account permissions still apply. Creating a pipeline does not authorize running or scheduling it.

See Snowflake's MCP connector administrator instructions and custom OAuth connector configuration for role requirements and configuration details.

Allow Snowflake CoCo in Supaflow​

  1. Sign in to the Supaflow account you want CoCo to use.
  2. Open Settings → Admin → API Access.
  3. Enable API access and allow Snowflake Cortex Code, the current permission label for Snowflake CoCo.
  4. Click Save API Access Changes.
  5. Review the selected permissions, then click Save access settings to apply them.

An organization administrator or personal-account owner must perform this step. An API key is not required for the OAuth connection.

Connect Your Supaflow Account in Snowsight​

  1. In Snowsight's user menu, switch to the role your administrator granted connector access to. The role selected inside a SQL file controls that file's SQL session; it does not change the user-menu role used by Snowsight.
  2. Open Settings → Personal agent settings → MCP connectors.
  3. Find SUPAFLOW_COCO_WEB and click Connect.
  4. Complete Supaflow sign-in and consent in the browser, selecting the intended account.
  5. Return to Snowsight. The connector now offers Disconnect.

Switching the account in the Supaflow dashboard does not switch CoCo's OAuth connection. To change accounts, disconnect the connector and authorize it again with the intended account.

Upload the Supaflow Skills​

Download the Snowflake Labs repository. Under plugins/supaflow/skills, locate these folders:

  • setup — connect your account and choose a workspace.
  • using-supaflow — prepare, create, run, and monitor data workflows.
  • setup-supaflow-native-app — guide Native App setup using Snowflake SQL and browser authorization.

In a Snowsight workspace, open CoCo's Add context → Skills menu and choose Upload skill folder for each folder, including its SKILL.md. These are personal skills; uploading them does not publish them to other Snowflake users.

Try a Conversation​

Start with:

Am I connected to Supaflow?

Then ask:

What's set up in my Supaflow workspace?

Confirm the intended workspace if more than one is available. Once Salesforce and Snowflake connections are configured, ask:

Plan a Salesforce-to-Snowflake pipeline for Account records. Show me the source, destination, objects, and settings before creating anything.

Review the plan, then explicitly ask CoCo to create the pipeline. Keep creation, running a sync, and scheduling separate decisions.

Run Pipelines on Your Snowflake Compute​

The Supaflow Native App runs the Supaflow agent inside your Snowflake account using Snowpark Container Services. Install and authorize the Native App, approve its agent in the intended Supaflow account, and select your workspace before running pipelines. See Native App agent approval for the account connection step.

Troubleshooting​

  • Connector missing: check the active Snowflake role and its database, schema, and MCP-server access.
  • Authorization denied: check that the intended Supaflow account allows the Snowflake Cortex Code permission, then reconnect.
  • Unexpected or empty workspace: verify the OAuth account and selected workspace. An empty inventory does not mean authentication failed.
  • Skills missing: upload each skill folder and search for Supaflow in the Skills menu.

Support​

Contact support@supa-flow.io for help with the Supaflow connector.