Builder Guide
Snowflake analytics sync (tenant-operated)
Export selected organization log metadata to your own Snowflake account after connection verification and explicit enablement.
Snowflake export copies selected log metadata from a tenant organization into a Snowflake account it controls. It is an analytics destination, not a complete backup of the application's records, files or logging history. See Connect organization logs to Snowflake for the current datasets, setup steps and supported API routes.
Who manages the connection?
The organization's active owner manages the destination in Admin → Snowflake. Builder support can use a Builder-managed live API credential only with explicit Snowflake scopes and a binding to that organization's active owner. A delegated tenant-user credential may use the same routes. The server verifies the app, organization and principal; entering an organization ID does not grant access.
Verify and enable export
- Save the destination and have a Snowflake administrator review and apply its setup SQL in the intended account. Saving a destination does not start export.
- Run Test connection and require a successful connection result. HTTP 200 alone does not prove that Snowflake accepted the operation.
- Explicitly enable the verified destination. Use Export next batch for a manual run.
- For automatic export, first confirm that the scheduled host is available, then choose a cadence and explicitly enable the schedule. Enabling the destination does not enable its schedule.
Scheduling requires a configured worker with a recent heartbeat. When it is unavailable, the API reports schedulingAvailable: false and rejects new schedule-enable requests. Each run handles a bounded batch; one completed run does not mean the destination has caught up with all eligible source rows.
Check delivery and recover failures
Review recent export history for each dataset's safe result, row count and correlation reference. Delivery checkpoints advance from Snowflake's confirmed offsets. An empty dataset may complete with zero rows. On a timeout or failure, refresh the status and follow the recovery guidance; do not reset or recreate a pipe or channel while a checkpoint exists without a reviewed recovery plan.
Prior integration checks exercised manual and scheduled export against an approved account. Those checks do not guarantee that a worker is running now or that every future batch will succeed. The current availability, destination verification and operation result remain the checks to use.
What the copy contains
The export covers selected AI usage, login, page-view, record-change, field-access/change, file-access and automation-job metadata. It excludes passwords, session tokens, prompts, responses, record/file contents and raw diagnostic payloads. The setup guide lists the eight datasets and their exact exclusions.
The tenant controls Snowflake access and retention after delivery. Export does not extend source-log retention, replace backups or transfer source integrity guarantees to the analytics copy. Consult the tenant logging guide for source-log integrity checks.
Capability review: 2026-09-14. See current features and setup requirements, the generated API Map and first-class module inventory.