Blob store (GCS / S3)
Sumble can exchange data with you as files in object storage — Google Cloud Storage or Amazon S3. This is the simplest integration option: no API connections, no database credentials. You send us your account list as a CSV, and we write enriched data back as Parquet files that you can process however you want.
Both directions are optional and independent. Use one, the other, or both.
What we deliver
Each pipeline run writes a set of Parquet files to your bucket:
Enriched organizations — your accounts with all configured enrichment columns
Alerts feed — intent signals generated for your accounts
Additional tables as configured for your account
Files are standard Apache Parquet, readable by any tool that supports it (BigQuery, Athena, Snowflake, Spark, pandas, DuckDB, ClickHouse, etc.). Each run replaces the previous set of files.
What you send us
To have Sumble enrich your accounts, put a CSV in the bucket at a fixed path and refresh it on your own schedule. We read the same path on every run.
One row per account, with a header row
Include a stable account identifier (your CRM's account id), the account name, and the company website — matching quality depends most on the website
Either plain
.csvor gzipped.csv.gz; we detect whichAny extra columns you include are preserved and available for filtering
You can send a people/contact list the same way.
Update cadence
Files are updated daily, after the Sumble data pipeline completes.
Setup
The blob store integration requires an enterprise plan.
Google Cloud Storage
Create a GCS bucket (or designate an existing one).
Grant Sumble's service account access to it — we'll give you the address.
Tell us the bucket name, and the path of your input CSV if you're sending one.
Amazon S3
Create an S3 bucket (or designate an existing one).
Grant Sumble's IAM principal access to it with a bucket policy — we'll give you the ARN to use. Read access is enough if you only send us data; add write access for us to deliver enriched files.
Tell us the bucket name, its region, and the
s3://URI of your input CSV if you're sending one.
If your security policy requires cross-account role assumption rather than a bucket policy, create an IAM role that trusts our principal, and give us the role ARN (and an external ID if you use one) instead.
Last updated