Copy page

Tools

Steampipe

The Tomba plugin for Steampipe exposes six Tomba endpoints as SQL tables. Tomba builds and maintains it; the source is at github.com/tomba-io/steampipe-plugin-tomba and the listing at hub.steampipe.io/plugins/tomba-io/tomba.

Every query that reads a Tomba table sends API requests: one for each value you give a table's required column, including each value in an in (...) list and each row a join supplies. Those requests are charged and throttled like direct API calls; see Credit costs and Rate limits.

Prerequisites

• Steampipe installed.
• A Tomba API key and secret. See Get your key and secret.

Install and connect

1. Install the plugin:

   Code
   steampipe plugin install tomba-io/tomba

2. Put your credentials in ~/.steampipe/config/tomba.spc:

   Code
   connection "tomba" {
     plugin = "tomba-io/tomba"
   
     key    = "ta_xxxx"
     secret = "ts_xxxx"
   }

   If key or secret is absent from the file, the plugin reads the TOMBA_KEY and TOMBA_SECRET environment variables. Values in the file take precedence.

Tables

Each table requires the column listed, with an = or in condition, except tomba_account.

sources, department, and seniority are JSON columns. secret_token holds your account's API secret, so restrict access to tomba_account when you share a Steampipe instance.

Steampipe caches query results for 300 seconds by default, so repeating a query within that time doesn't call Tomba again.

Example

Verify a list of addresses and keep the deliverable ones. The join sends one verification request per row of leads:

Code
with leads (email) as (
  values
    ('jane.doe@stripe.com'),
    ('john.smith@stripe.com')
)
select
  v.email,
  v.result,
  v.score,
  v.accept_all
from
  leads
  join tomba_verifier as v on v.email = leads.email
where
  v.result = 'deliverable';

result is one of the result values. Filter on result rather than status: status can be valid or Valid.

Troubleshooting