Tomba
Sales IntelligenceFind and verify emails and enrich B2B records with the Tomba API, covering domain search, person and LinkedIn finders, and deliverability checks. Agents build a verified list before the first send.
What This Integration Enables
Every connector in this category can find an address. Tomba is the one that can tell you where it came from. Get Email Sources returns the public web pages a given address was found on, with the URL, the date it was extracted, the date it was last seen and whether it is still present on that page. That is provenance, and it changes what a record means. An address with three live sources on a company site is a business contact publishing a way to reach them. An address whose only source vanished eighteen months ago is an inference wearing the same clothes. Both look identical in a CRM field, and only one of them gives you something to say when a recipient asks where you got it.
Around that sits the widest surface in this batch. Domain Search lists the addresses Tomba holds for a company along with the organisation profile, location, social links and the detected email pattern, and each contact carries name, position, seniority and department. Email Finder resolves a specific person, LinkedIn Finder converts a profile URL into a verified address, and Author Finder resolves the byline on an article or blog post, which is the operation that makes content outreach and digital PR practical rather than manual. Email Verifier runs SMTP, MX, disposable domain, webmail, gibberish and catch-all checks and returns the individual results alongside the overall status, so a flow can filter as strictly as the campaign requires rather than accepting the vendor's threshold. Domain intelligence covers status, suggestions, similar domains, technologies and location, which turns account qualification into a query. Enrichment runs in both directions, from an address to a person or a company or both at once. Bulk jobs, leads and lead lists give the whole thing a workspace, with one caveat worth knowing before you design around it: creating a bulk job needs a multipart CSV upload that this connector does not expose, so jobs are created in the Tomba app and then launched, polled and downloaded from a flow.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Qualifying accounts on the stack they already run
An outbound team sells a replacement for a widely deployed tool. Rather than filtering on headcount and hoping, the agent runs Get Domain Technologies across the account list and keeps only the domains where the competing product is detected. Get Similar Domains then expands the list outward from the best-fit accounts, and Get Domain Location supplies the country and city for territory routing. Domain Search names the people at each surviving account. The campaign targets companies with a concrete reason to switch, and the qualification criterion is a fact about the account rather than a proxy for one.
Content outreach that starts from the article
A marketing team wants to reach the people who write about their category. The agent takes a list of article URLs, calls Author Finder on each to resolve the byline and the matching professional address, verifies the result with Email Verifier, and pulls Get Email Sources so the outreach draft can reference where the contact was found. Qualifying contacts are pushed into Tomba as a segment with Create Lead List, and the same list is mirrored into Google Sheets for the writer to work from. The pitch is grounded in the specific piece the person published, which is the only version of this outreach that deserves a reply.
Handling an erasure request end to end
A recipient asks to be removed. The agent finds the saved lead, reads it with Get Lead, checks which lead lists it belongs to with List Lead Lists, and assembles the picture before touching anything. Delete Lead permanently removes the record from the Tomba workspace and cannot be undone, and the same person may also exist in the CRM and in an active sequence, so the agent reports the full footprint and executes deletion across every system only once the scope is confirmed. The connector makes the removal possible. The flow makes it complete, which is the part that usually goes wrong.
Human-in-Loop Highlight
Get Email Sources reports whether an address is still present on the page it was extracted from, and that flag is the sharpest signal on this connector. When it comes back negative, Tomba is telling you the only public evidence for this address has been taken down. The person may have left, the page may have been rewritten, or they may have removed their contact details deliberately, and the connector cannot distinguish between those. Sending anyway is not a technical error, since the address may well still deliver. It is a judgement about whether a contact who is no longer publishing a way to reach them should be mailed on the strength of a record of when they used to. The agent brings the evidence and stops: "[N] contacts verified for [Account]. [N] of them have no live source: [address] was last seen on [URL] on [date] and is no longer present. Verification status is [status]. Include these in the sequence, hold them, or drop them from the list?" The rep answers. Everything with live provenance and a clean verification proceeds without anyone being asked. This is human-in-the-loop at the point where the data stops being a fact and starts being a history, and it is the reason to run a connector like this inside an orchestration layer rather than as a lookup in a browser extension.
Agent Capabilities
40 actionsFinding Contacts
4- Domain Search Lists the professional addresses Tomba holds for a company domain, together with the organisation profile, location, social links and the detected email pattern. Each contact includes name, position, seniority, department and verification state.
- Email Finder Finds the professional address of a specific person at a company from their name and the company domain or name. Returns the address with a confidence score, verification status, position, LinkedIn and Twitter handles and the public sources behind it.
- LinkedIn Finder Converts a LinkedIn profile URL into the verified professional address behind it, along with the person's name, company and position. Enable Full Profile to return the complete enriched record. Used for turning scraped or exported profile lists into contactable records.
- Author Finder Finds the address of the author of a given article or blog post URL by parsing the page for bylines and resolving the matching professional address. Used for content outreach, guest post pitching and digital PR.
Verification
2- Email Verifier Checks whether a single address is deliverable, running SMTP, MX, disposable domain, webmail, gibberish and catch-all checks. Returns an overall status plus the individual check results, so a flow can filter as strictly as the campaign requires.
- Get Email Sources Returns the public web pages where an address was found, with the source URL, the date it was extracted, the date it was last seen and whether it is still present on the page. Used to evidence how a contact was sourced.
Domain Intelligence
7- Get Email Count Returns how many addresses Tomba holds for a domain, broken down by personal versus generic and by department and seniority. A cheap way to size a domain before spending on a full Domain Search.
- Get Email Format Returns the naming patterns detected for a domain, such as {first} or {first}.{last}, each with a confidence score. Use the dominant pattern to construct likely addresses for people you cannot find directly, then verify them.
- Get Domain Status Reports whether a domain is a free webmail provider or a disposable or temporary email service. Used to filter consumer and throwaway domains out before contacts reach a B2B sequence or CRM.
- Get Domain Suggestions Suggests company domains matching a free-text company name query. Used to resolve a messy company name from a CRM or a form submission into a canonical domain.
- Get Similar Domains Returns companies similar to a given domain based on industry, size and business model. Used to expand an ideal customer profile from a handful of known accounts into a wider target list.
- Get Domain Technologies Returns the technology stack detected on a domain, such as CRM, analytics, ecommerce and hosting platforms. Used to qualify accounts by the tools they already run.
- Get Domain Location Returns the physical location associated with a company domain, including country, state, city, street address and postal code. Used for territory routing, regional segmentation and data residency checks.
Phone
2- Find Phone Number Finds phone numbers associated with a contact, identified by email address, company domain or LinkedIn profile URL. Enable Full Details for the complete record including line type and carrier. At least one identifier must be supplied.
- Validate Phone Number Validates a phone number and returns its normalised local and international formats, country, line type and carrier. Used to clean phone data captured from forms or imported lists before dialling.
Enrichment
5- Enrich Email Performs a reverse lookup on an address, returning name, position, company, country, gender, social profiles, confidence score and verification status. Used to fill in a contact record that arrived with only an address.
- Enrich Person Returns a person profile for an address, including full name, role, location, employment history and social profiles. The person-only counterpart of Enrich Combined, and cheaper when company firmographics are not needed.
- Enrich Company Returns a firmographic profile for a company domain, including legal name, description, industry, employee count, revenue range, founding year, location and social profiles.
- Enrich Combined Returns both the person profile and the full company firmographics for a single address in one call. Used when creating a new CRM contact and account together.
- Search Companies Searches the company database using a free-text query plus include and exclude filters across company name, country, city, state, industry, size, type, keywords, founding year, technologies, similar companies, revenue, SIC and NAICS codes.
Bulk Operations
8- List Bulk Operations Lists bulk jobs of a chosen type, such as Email Finder or Email Verifier batches, with their names, status and item counts. Paginated, sortable newest or oldest first, and filterable to archived jobs or to all jobs.
- Get Bulk Operation Retrieves the full record of a single bulk job, including its name, configuration, item counts and current status.
- Get Bulk Operation Progress Returns the completion percentage and processed item count for a running job. Poll until progress reaches 100 before downloading results.
- Launch Bulk Operation Starts processing a job that has been created but not yet run. Jobs remain queued until launched, so call this once the input list is in place.
- Download Bulk Results Downloads the results of a completed job. Choose Full Results for every row, Valid Only for rows with deliverable addresses, or Not Found Only to review the misses.
- Rename Bulk Operation Changes the display name of an existing job, between 3 and 200 characters. Used to keep long-running batches identifiable by campaign or import date.
- Archive Bulk Operation Archives a job so it no longer appears in the default list while its results remain retrievable. Archived jobs can still be listed by setting the Filter parameter.
- Delete Bulk Operation Permanently deletes a job and its results. This cannot be undone, so use Archive Bulk Operation when the intent is only to hide a finished job.
Leads
5- List Leads Lists saved leads in the workspace, optionally restricted to a single company domain, paginated. Used to sync leads captured by bulk jobs into a downstream CRM or spreadsheet.
- Get Lead Retrieves a single saved lead by identifier, including email, name, company, job title and any custom attributes defined on the workspace.
- Update Lead Updates the stored details of a saved lead, changing only the fields supplied. Used to keep Tomba leads in sync when a record is corrected in the CRM.
- Delete Lead Permanently removes a saved lead from the workspace. Used to honour deletion requests or to prune rejected records. The operation cannot be undone.
- List Lead Attributes Lists the custom lead attributes defined on the workspace with their identifiers and names. Used to discover which custom fields exist before mapping leads onto a CRM schema.
Lead Lists
5- List Lead Lists Lists the lead lists in the workspace with their identifiers, names and descriptions. Lead lists group saved leads for a campaign or segment.
- Create Lead List Creates a new lead list, optionally pre-populated with leads carrying email, name, company, job title and custom attributes. Used to push a segmented prospect list from a flow into Tomba.
- Get Lead List Retrieves a single lead list by identifier, including its name, description and the leads it contains. Used to read back a segment before exporting it.
- Update Lead List Updates the name or description of an existing list, changing only the fields supplied. Used to relabel a segment as a campaign evolves without losing its leads.
- Delete Lead List Permanently deletes a lead list from the workspace. The operation cannot be undone, so confirm the list ID with Get Lead List first.
Account
2- Get Account Returns the authenticated account profile together with the active pricing plan and the remaining search, verification and enrichment allowances. Used to check quota before a large job.
- Get API Usage Returns the number of API requests made in the current rate-limit window, the maximum allowed, and when the window resets. Used to back off gracefully in high-volume flows before hitting a 429.
Frequently Asked Questions
What can FlowRunner do with Tomba?
FlowRunner agents can run Domain Search, Email Finder, and Email Verifier in Tomba, plus 37 more actions.
Does connecting Tomba to FlowRunner require OAuth?
No. Tomba connects to FlowRunner with an API key, no OAuth flow required.
Can Tomba trigger a FlowRunner workflow automatically?
Tomba doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Tomba
$100 in credits. No card required. Connect in minutes.