We're here to help.

v1.3's AI assist runs entirely on Snowflake Cortex — server-side inside your Snowflake account. Your prompt text and the inferred SQL never traverse a third-party server. The same boundary that protects your query results protects your AI prompt.

Requirements:

• Snowflake Cortex must be enabled on your account (paid Snowflake accounts; not most trial accounts)
• SnowExporter Pro or Trial — Free-tier users see an upgrade card in place of the AI input

On accounts without Cortex, the AI panel renders an explainer and the manual wizard continues to work normally — nothing breaks.

Both use incoming webhooks. Settings → 📣 Notifications → Slack or Teams sub-tab → + Add channel.

Slack: Create an incoming webhook URL at api.slack.com/apps for your workspace, paste it into SnowExporter, optionally fill in Description and Business Contact, click Test to verify, save.

Microsoft Teams: In the target Teams channel → Connectors → add "Incoming Webhook" → copy the URL → paste into SnowExporter, fill in metadata, Test, save.

Once added, the channel appears in the Create Data Export wizard's destination picker like any other delivery target. In-chat tables are capped at 10 rows; for larger results enable the file-attachment option.

The internal stage you're writing to needs to be created with Snowflake's server-side encryption explicitly set:

CREATE OR REPLACE STAGE my_stage
    ENCRYPTION = (TYPE = 'SNOWFLAKE_SSE');

Snowflake's default stage encryption returns raw encrypted bytes through presigned URLs, which manifests as files that look corrupted in a browser. v1.2 patched the in-app setup helper to generate CREATE STAGE SQL with the right ENCRYPTION clause by default — but if you created the stage manually or before v1.2, recreate it with the clause above (or run ALTER STAGE … SET ENCRYPTION = (TYPE = 'SNOWFLAKE_SSE')).

When you create a STORAGE INTEGRATION for AWS S3 / GCP GCS / Azure Blob, you must explicitly grant USAGE on it to the application:

GRANT USAGE ON INTEGRATION <your_integration_name> TO APPLICATION SNOWEXPORTER;

This is the most commonly-missed step. The app's Settings → 📤 Export destinations → + Add a destination → Show required setup SQL generates the exact SQL for each cloud, including this grant.

Most common causes, in order:

• The notification integration isn't created or isn't named exactly NATIVE_APP_EMAIL_INTEGRATION. Settings → ✉️ Notification has the exact SQL to run.
• The recipient is not a verified Snowflake user email on your account. The recipient picker only lists verified users, but if you typed an address directly somehow, it will silently fail to deliver.
• You're hitting Snowflake's email rate limits — bursty sends can be delayed several minutes.
• You're trying email-body delivery with more than 50 rows. The 50-row cap is Snowflake's SYSTEM$SEND_EMAIL constraint, not ours. Use download-link or file delivery for larger results.

No — Snowflake task metadata has a few-second propagation delay after ALTER TASK … RESUME. The Scheduled Exports page has a Refresh button right next to the status indicator. Click it after resuming and the state will catch up.

In v1.0, no — the policy is recorded and displayed in Settings → Users, but it is not enforced at runtime. Runtime enforcement is on the roadmap for a future release. In v1.0 the policy serves as documentation: it records which roles are intended to use each destination, surfaced in the UI for auditing and review.

This caveat is also called out on the product page and the v1.0 release notes so the limitation is visible up-front.

SnowExporter is a Snowflake Native App — it executes inside your Snowflake account. Your query runs against your data with the privileges you've granted to the application. Results are delivered via Snowflake's built-in SYSTEM$SEND_EMAIL or COPY INTO mechanisms.

Your data is never transmitted to SnowExporter.com LLC servers. The only thing that leaves Snowflake is the output you explicitly asked the app to deliver (an email or a file in your chosen cloud bucket).

Search "SnowExporter" on the Snowflake Marketplace and install it from there. Snowsight will open the app on its Home dashboard. From there:

1. Grant the requested references (warehouse + source tables) in the Snowsight reference prompt
2. Settings → ✉️ Notification: create the email integration with the SQL snippet shown
3. Settings → 📤 Export destinations: add your first destination
4. Click Create Data Export

The v1.0 release notes have the full account-level setup SQL.

From Snowsight, navigate to the SnowExporter app → ⋮ menu → Upgrade. The app's state (recipients, timezone, destinations, audit log, role policy) lives in the backend_schema and is preserved across upgrades, so you won't lose configuration.

The Logs page pulls per-query credits from ACCOUNT_USAGE.QUERY_ATTRIBUTION_HISTORY. Note that ACCOUNT_USAGE has a propagation latency of up to 45 minutes — the first few minutes after a run, the credits column may show as null. Refresh later and the actual cost will appear.