For the complete documentation index, see llms.txt. This page is also available as Markdown.

Snowflake Native Application

Introduction

MadConnect enables secure, in‑warehouse orchestration and activation directly inside your Snowflake account using Snowpark. This guide consolidates the latest setup flow (v1.55+) with clear, step‑by‑step instructions and visual placeholders.

Audience: Snowflake administrators and MadConnect users

Goal: Install, activate, validate, and (if needed) uninstall the MadConnect Snowflake Native Application using client‑managed resources and minimal required privileges.

Key characteristics:

  • Installed from Snowflake Marketplace.

  • Runs inside your Snowflake environment; no data extraction or replication.

  • Uses client‑managed compute (compute pools, warehouses) and minimal app privileges.


Prerequisites

Role Requirement

  • Log in with the ACCOUNTADMIN role.

  • Ensure no existing warehouse named MAD_CONNECT_WH (or mad_connect_wh) exists

  • Confirm your network policies allow creation of external access integrations as needed by your organization

Required privileges at a glance

  • Application: BIND SERVICE ENDPOINT, EXECUTE TASK (remain granted)

  • Client‑managed resources: Compute Pools, Warehouses, Network Rules, External Access Integrations

Why BIND SERVICE ENDPOINT is required: Enables the app to expose its service URL (web UI/API) while all compute remains client‑managed (see Privilege Rationale section).

Last updated