Snowflake
Register Snowflake as an export destination, validate the connection once, and let DualEntry data land in your own warehouse.
Overview
Snowflake is an export destination rather than a ledger sync. DualEntry does not pull records from Snowflake or push journal entries into it; it registers and tests your warehouse credentials, then stores them so the export infrastructure can write data into your warehouse.
You supply the account locator, warehouse, database, username and password, and optionally a role. DualEntry saves the destination as Pending, validates it in the background, and moves it through Testing to Validated. On success the credentials transfer to AWS Secrets Manager and the integration shows Connected.
Only non-sensitive metadata — account, warehouse, database — is kept in DualEntry's own database. Passwords never persist there.
Export destination credentials
Connection validation status
Data synced
The integration syncs the following data types:
Key Features
- Validated before it is trusted
A new destination moves from Pending through Testing to Validated, so a bad credential is caught at setup rather than at export time.
- Credentials held in AWS Secrets Manager
Username and password live exclusively in Secrets Manager and are never returned by DualEntry's APIs after creation.
- Minimal metadata retained
Only account, warehouse and database are stored in DualEntry's database. Passwords never persist there.
- Optional role support
Supply a Snowflake role and it is passed through to the connector; leave it out and the default applies.
- Safe disconnection
Disconnection is blocked while export jobs are running, so a warehouse is never pulled out from under an in-flight job.
- One destination per organization
A single active Snowflake export integration per organization keeps the pipeline unambiguous.
.avif)