Snowflake event destination

Merge mapped Nimriz events into a customer-owned Snowflake table through the SQL API.

Availability: Snowflake is in beta. You must successfully test your own account, role, warehouse, and table configuration before enabling the destination.

Requirements

• An Enterprise plan.
• A Snowflake service user with an RSA key pair and an unencrypted PKCS#8 private key.
• USAGE on the warehouse, database, and schema plus SELECT and INSERT on the target table.

CREATE TABLE NIMRIZ_EVENTS (
  DELIVERY_ID VARCHAR NOT NULL,
  EVENT_ID VARCHAR NOT NULL,
  EVENT_TYPE VARCHAR NOT NULL,
  OCCURRED_AT TIMESTAMP_TZ NOT NULL,
  PAYLOAD VARIANT NOT NULL,
  INGESTED_AT TIMESTAMP_TZ DEFAULT CURRENT_TIMESTAMP()
);

Connect Snowflake

1. Choose Snowflake and enter the account, login name, key fingerprint/private key, warehouse, role, database, schema, and table.
2. Save and send a test. The test merges a real sample row.
3. Enable the destination after authentication and table access pass.

Nimriz sends one bound MERGE per batch and keys rows by delivery ID. Stable SQL API request IDs and the table merge make retries idempotent. Identifiers must use letters, numbers, and underscores; payload values are always bound separately.