// snowflake native app · coming soon
Enrich your tables without leaving Snowflake
Find, verify and enrich emails, phones and companies for the rows of your tables, from SQL or from the app in Snowsight. Billed on your Snowflake invoice, with no Tomba account.
$0.0098 per Tomba credit · billed by Snowflake
// 01 · in snowsight
The app, next to your data
A Streamlit app comes with the Native App: look up one contact, enrich a whole table, build company lists and follow every run. Each page calls the same procedures you can call from SQL.
Every row, one run
Point a tool at a table or a view, match its columns, and see the most the run can cost before it starts. Results go to a new table in the app, and large runs carry on in the background.
Company lists from filters
Choose countries, industries, keywords, size and more. Only the filters you choose are sent to Tomba, with no free-text query and no AI, and the companies land in a new table.
Results next to your data
Every result table keeps your input values, so it joins back to your rows. Export the first 10,000 rows as a CSV file, or copy the table into your own database.
Runs you can follow and resume
Follow the runs going now, cancel one, or resume a run that stopped: the rows already done are kept and aren't charged again. Auto-resume tries again the next day.
Tables kept enriched
A schedule runs a tool on a table at the times you set and looks up only the rows added since its last run. Only app_admin can create or change one.
Usage and credits at a glance
The Overview shows the install's state, the three ways to start and the last 30 days: rows looked up, search and verification credits apart, and what Snowflake charged.
// 02 · in sql
Every tool is a procedure you call
Call Tomba from a worksheet, a notebook, a task or dbt. One value comes back at once; a whole table runs in chunks and writes a result table inside the app.
-- one value: the answer comes back at once
CALL TOMBA.core.email_finder('piedpiper.com', 'Richard', 'Hendricks');-- every row of a table: results go to TOMBA.RESULTS.LEADS_FOUND
CALL TOMBA.core.find_emails(
'CRM.PUBLIC.LEADS',
'COMPANY_DOMAIN', 'FIRST_NAME', 'LAST_NAME',
'LEADS_FOUND',
1000
);-- any tool, with its options
CALL TOMBA.core.run_tool(
'domain_search',
'CRM.PUBLIC.ACCOUNTS',
{'domain': 'WEBSITE'},
'SALES_EMAILS',
100,
{'emails_per_domain': 20, 'department': 'sales'}
);-- a large table in the background, with a credit limit
CALL TOMBA.core.run_tool_async(
'email_finder',
'CRM.PUBLIC.LEADS',
{'domain': 'COMPANY_DOMAIN', 'first_name': 'FIRST_NAME', 'last_name': 'LAST_NAME'},
'LEADS_FOUND',
500000,
{'max_credits': 20000}
);
-- new rows every morning at 06:00 UTC
CALL TOMBA.core.create_schedule(
'DAILY_LEADS', 'email_finder', 'CRM.PUBLIC.LEADS',
{'domain': 'COMPANY_DOMAIN', 'full_name': 'NAME'},
'LEADS_ENRICHED', '0 6 * * *',
{'max_credits': 1000}
);-- read the results, then keep a copy in your own database
SELECT INPUT_FIRST_NAME, INPUT_LAST_NAME, EMAIL, SCORE, VERIFICATION_STATUS
FROM TOMBA.RESULTS.LEADS_FOUND
WHERE LOOKUP_STATUS = 'found';
CREATE TABLE crm.public.leads_found AS
SELECT * FROM TOMBA.RESULTS.LEADS_FOUND;Results · 3
| # | INPUT_FIRST_NAME | INPUT_LAST_NAME | SCORE | LOOKUP_STATUS | CREDITS | |
|---|---|---|---|---|---|---|
| 1 | Richard | Hendricks | richard@piedpiper.com | 100 | found | 1 |
| 2 | Dinesh | Chugtai | dinesh@piedpiper.com | 99 | found | 1 |
| 3 | Bertram | Gilfoyle | gilfoyle@piedpiper.com | 97 | found | 1 |
A result table starts with your input values, so it joins back to your rows; each row says whether Tomba found it and what it cost.
// 03 · the procedures
13 tools, for one value or a whole table
Each tool has a procedure for a whole table and one for a single value, and costs what its Tomba endpoint costs. The run_tool and lookup procedures take any tool by name, with its options.
Email Finder1 search credit
core.find_emails(input_table, domain_column, first_name_column, last_name_column, output_table)
core.email_finder(domain, first_name, last_name)
Email Verifier1 verification credit
core.verify_emails(input_table, email_column, output_table)
core.email_verifier(email)
Domain Search1 search credit per 10 emails requested
core.search_domains(input_table, domain_column, output_table)
core.domain_search(domain)
Email Enrichment1 search credit
core.enrich_emails(input_table, email_column, output_table)
core.email_enrichment(email)
Person Enrichment1 search credit
core.enrich_people(input_table, email_column, output_table)
core.person_enrichment(email)
All 13 tools
Company Enrichment1 search credit
core.enrich_companies(input_table, domain_column, output_table)
core.company_enrichment(domain)
Combined Enrichment2 search credits
core.enrich_combined(input_table, email_column, output_table)
core.combined_enrichment(email)
LinkedIn Finder1 search credit
core.find_emails_from_linkedin(input_table, url_column, output_table)
core.linkedin_finder(url)
Author Finder1 search credit
core.find_authors(input_table, url_column, output_table)
core.author_finder(url)
Phone Finder5 search credits
core.find_phones(input_table, email_column, output_table)
core.phone_finder(email)
Phone Validator1 search credit
core.validate_phones(input_table, phone_column, output_table)
core.phone_validator(phone)
Similar Domains1 search credit
core.find_similar_domains(input_table, domain_column, output_table)
core.similar_finder(domain)
Companies Search1 search credit per 50 companies
core.search_companies(filters, output_table, max_results)
core.lookup('companies_search', {…})
| Tool | Whole table | One value | Cost |
|---|---|---|---|
Email FinderGET /email-finder | core.find_emails(input_table, domain_column, first_name_column, last_name_column, output_table) | core.email_finder(domain, first_name, last_name) | 1 search credit |
Email VerifierGET /email-verifier | core.verify_emails(input_table, email_column, output_table) | core.email_verifier(email) | 1 verification credit |
Domain SearchGET /domain-search | core.search_domains(input_table, domain_column, output_table) | core.domain_search(domain) | 1 search credit per 10 emails requested |
Email EnrichmentGET /enrich | core.enrich_emails(input_table, email_column, output_table) | core.email_enrichment(email) | 1 search credit |
Person EnrichmentGET /people/find | core.enrich_people(input_table, email_column, output_table) | core.person_enrichment(email) | 1 search credit |
Company EnrichmentGET /companies/find | core.enrich_companies(input_table, domain_column, output_table) | core.company_enrichment(domain) | 1 search credit |
Combined EnrichmentGET /combined/find | core.enrich_combined(input_table, email_column, output_table) | core.combined_enrichment(email) | 2 search credits |
LinkedIn FinderGET /linkedin | core.find_emails_from_linkedin(input_table, url_column, output_table) | core.linkedin_finder(url) | 1 search credit |
Author FinderGET /author-finder | core.find_authors(input_table, url_column, output_table) | core.author_finder(url) | 1 search credit |
Phone FinderGET /phone-finder | core.find_phones(input_table, email_column, output_table) | core.phone_finder(email) | 5 search credits |
Phone ValidatorGET /phone-validator | core.validate_phones(input_table, phone_column, output_table) | core.phone_validator(phone) | 1 search credit |
Similar DomainsGET /similar | core.find_similar_domains(input_table, domain_column, output_table) | core.similar_finder(domain) | 1 search credit |
Companies SearchPOST /reveal/search | core.search_companies(filters, output_table, max_results) | core.lookup('companies_search', {…}) | 1 search credit per 50 companies |
In every result table
First your input values, as INPUT_ columns, then the tool's own columns, then these:
- LOOKUP_STATUS
- CREDITS
- CREDIT_TYPE
- DATA
- ERROR
- LOOKED_UP_AT
- SOURCE
// 04 · set up
From the Marketplace to your first run
The app creates its own connection to api.tomba.io; you approve it and choose the tables it may read. There's no network rule, secret or API key to set up.
- 01
Get the app
Find Tomba in Snowsight under Data Products › Marketplace, name the app and pick a warehouse. X-Small is enough.
- 02
Approve the connection
On the app's Security tab, approve the Tomba API connection. It reaches only api.tomba.io.
- 03
Share your tables
Choose a table or a view in the app, or grant SELECT on it from SQL.
- 04
Run a tool
Look up a contact or enrich a table in the app, or call a procedure from any worksheet.
// 05 · pricing
Pay per credit, on your Snowflake invoice
No Tomba plan and no Tomba account: Snowflake bills each Tomba credit the app uses, at one price for search and verification credits.
// per tomba credit
$0.0098
For each search or verification credit, billed by Snowflake. Each tool costs what it costs on tomba.io.
Examples, rounded to the cent
- 1 → $0.01
- 3 → $0.03
- 51 → $0.50
- 1,000 → $9.80
What isn't charged
Lookups that find nothing, invalid input, errors, answers from the cache, repeats of the same lookup in the month and duplicate rows. Phone Validator is charged for each check.
A ceiling for every run
Set a credit limit on a run and a monthly credit budget for the whole app. Runs are sized for the worst case, so they never go over.
New installs start capped
200 lookups a UTC day until the install is confirmed in Snowflake's records, usually within a few hours.
Listing trials
During a Marketplace listing trial, each call processes up to 100 rows and nothing is charged.
Snowflake compute
Background runs and schedules use serverless tasks, billed to your account like any serverless task.
No charge twice
A run that stopped resumes where it left off: the rows already done are kept and aren't charged again.
// 06 · your data
Your tables stay in Snowflake
The app reads only the tables you share, writes its results inside itself, and sends Tomba only the values each lookup needs.
What leaves your account
- One host, approved by you
- The app can reach only
api.tomba.io:443, through the external access connection you approve. - Only what each lookup needs
- The values you pass, such as domains, names, emails, URLs and phone numbers, and usage counts for billing. Never your tables.
What stays in Snowflake
- Results in the app
- Result tables live in
TOMBA.RESULTS, in your account. Copy them into your own database to keep and share them. - Credentials no role can read
- The app keeps its credentials in a private schema. There's no API key for you to store.
- Two app roles
app_publicruns the tools and reads results and history;app_adminalso changes settings and schedules.- Read-only access
- The tables and views you share are read with
SELECTonly.
Share a table and give people access
-- let the app read a table (or use Choose a table in the app)
GRANT USAGE ON DATABASE crm TO APPLICATION TOMBA;
GRANT USAGE ON SCHEMA crm.public TO APPLICATION TOMBA;
GRANT SELECT ON TABLE crm.public.leads TO APPLICATION TOMBA;
-- who runs the tools, and who changes the settings
GRANT APPLICATION ROLE TOMBA.app_public TO ROLE analyst;
GRANT APPLICATION ROLE TOMBA.app_admin TO ROLE sysadmin;Snowflake is a trademark of Snowflake Inc.
// tomba for snowflake
Coming soon to the Snowflake Marketplace
Read how the app works, procedure by procedure, or write to us about your Snowflake account.