Tomba is an Email Finder for B2B sales and email marketing.
Tomba is an Email Finder for B2B sales and email marketing. On Nagent, Tomba is exposed as a fully-configurable sales & crm integration that any agent can call — 10 actions, and API key authentication. No code is required to wire Tomba into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Tomba to automate the kinds of tasks sales & crm teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Tomba into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Tomba, with input parameters and output schema. Drop these into any step of an agent built in Helix.
TOMBA_ATTRIBUTES_LISTRetrieves all custom lead attributes defined in your Tomba account. Use this action to discover the available attributes that can be used when creating or updating leads. Returns attribute metadata including name, identifier, type, and timestamps. No input parameters required.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TOMBA_DOMAIN_STATUSTool to check if a domain is webmail or disposable. Use when validating email deliverability constraints.
Input parameters
The domain name to check the status for (e.g., 'gmail.com')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TOMBA_KEYS_DELETETool to delete an API key by its numeric ID. Use when you need to permanently revoke an API key before its expiration. Note: You can get the numeric key ID from the TOMBA_KEYS_LIST action.
Input parameters
The numeric ID of the API key to delete. This is the 'id' field returned by the keys list endpoint, not the key string itself.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TOMBA_KEYS_LISTTool to list all API keys. Use when you want to retrieve information about your existing Tomba API keys.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TOMBA_LEADS_CREATECreate a new lead in Tomba's lead database. Use this to store contact information for a person you want to track. Returns the unique ID of the created lead. Required fields: first_name, email. All other fields are optional.
Input parameters
City where the lead is located
List of tags to categorize or label the lead for organization
Lead's email address (required). Must be a valid email format
Lead's phone number, including country code if international
State or province where the lead is located
Company or organization the lead works for
Two-letter ISO 3166-1 alpha-2 country code. Must use the code format, not full country name
Full Twitter/X profile URL
Lead's personal or company website URL
Full LinkedIn profile URL
Lead's job title or position
Lead's last name. If provided, must not be empty
Lead's first name (required)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TOMBA_LEADS_LISTTool to list all leads. Use when you need to retrieve and paginate your leads list.
Input parameters
Page number to retrieve (1-indexed). Defaults to 1 if not specified.
Number of leads per page (1-100). Defaults to 10 if not specified.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TOMBA_LISTS_DELETETool to delete a leads list by ID. Use when you need to permanently remove a list after confirming its ID.
Input parameters
The unique numeric identifier of the leads list to delete. Obtain this ID from the lists list action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TOMBA_LISTS_LISTTool to list all lead lists. Use when you need to retrieve and paginate your lead lists.
Input parameters
Page number for pagination, must be >= 1
Number of items per page, between 1 and 100
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TOMBA_LISTS_UPDATETool to update a leads list's name by ID. Use when renaming an existing list after obtaining its ID.
Input parameters
Numeric ID of the leads list to update (obtain from TOMBA_LISTS_LIST action)
New name for the leads list. Must be unique across all lists in the account.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TOMBA_USAGE_STATSTool to get API usage statistics. Use when you need to monitor account usage and avoid hitting limits.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 61 agents privately built on Nagent that already use Tomba.
Build on Nagent
Connect Tomba to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Tomba, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Tomba is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Tomba is connected, you configure its 10 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Tomba steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Tomba event fires, the agent kicks off automatically.
Every Tomba action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Tomba ships with 10 pre-built sales & crm actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Tomba together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Tomba-based workflows tailored to your business.