Quickstart
From signup to your first row of API data in Snowflake. Pipelines are live in minutes, not hours.
This walkthrough takes you from a blank Ingest account to a queryable Iceberg table in Snowflake. You will need an account in Ingest, an API token for the source you want to sync (we'll point at the right place to get one), and either Snowflake credentials or an S3 bucket to receive the data.
Sign in to Ingest
Open the Ingest dashboard and sign in. New accounts can be created via the contact form.
Pick a connector
Open Connectors and choose a source. Asana, HubSpot, Salesforce, or any of the supported integrations.
Paste your credentials
Each connector page lists exactly what to paste, usually a single API token. Credentials are stored encrypted in AWS Secrets Manager.
Pick the endpoints to sync
Tick the endpoints you want. You can change this later. Most teams start with the 4–6 endpoints that drive their reporting.
Pick a destination
Snowflake (managed by Ingest) or your own S3 bucket. Both land data as Iceberg tables.
Deploy
Hit deploy. Ingest provisions the pipeline and starts the first sync. Most pipelines are live in minutes.
Query your data
Open Snowflake (or your query engine of choice) and select from the Iceberg table. Each endpoint becomes its own table, query, join, build dashboards.
What you get on the other side
- One Iceberg table per endpoint, with primary keys and a
_synced_atcolumn. - Continuous incremental syncs on the schedule you configured.
- Run history, row counts, and error visibility in the dashboard.
- Automatic retries and rate-limit backoff. You don't have to handle 429s, pagination, or auth refresh.
Next steps
- Browse the connector catalog to add more sources.
- Read why Ingest uses Iceberg if you're evaluating storage options.
- See how Ingest works for the conceptual model.