TombaTomba
Start free
  • Documentation
  • API reference
  • SDKs & CLI
  • AI & MCP
  • Integrations
  • Enterprise
  • Migration guides

Find, verify and enrich B2B contacts from public sources, in the app, your spreadsheet or through the API.

GDPR & CCPA

// docs

  • API changelog
  • Support options
  • Security

// platform

  • Dashboard
  • Pricing
  • API status

// resources

  • Help center
  • Product updates
  • TombaBot crawler

// company

  • Website
  • Contact us
  • Edit or remove your data

© 2021–2026 Tomba.io

  • Terms of service
  • Privacy policy
  • Cookie policy
  • Security policy
  • GDPR
  • CCPA
Overview
Salesforce (coming soon)
    Getting Started
    Guides
      Record actionsList views and bulk runsAutomationFlow actionsAgentforceTomba SearchAccount matchingBuying committeeReports, dashboard and record panelUsage, limits and alertsThe Tomba API tabSingle sign-onSandboxesField mappingData healthClean dataPrevent bad dataKeep Your Salesforce Contact Data DeliverableSecurity and Data ProtectionFAQ and troubleshooting
Snowflake (coming soon)
Guides

Flow actions

Tomba adds two actions to Flow Builder, in the Tomba category.

Tomba: Run on Record

Calls Tomba right away and returns the result.

InputDescription
Record IDA Lead, Contact or Account
OperationLeads/Contacts: enrich, find, verify, phone, validate_phone, bounce, match; Accounts: enrich, technology, index_domains
Save results to the recordDefault on. Off returns the values without changing the record

Outputs: Status (Done, Not Found, Skipped, Error), Message, Fields updated, Email, Email status, Email score, Phone, Position, LinkedIn, Company domain, Credits used.

Because it calls Tomba, use it in screen flows, scheduled paths, the Run Asynchronously path of record-triggered flows, or autolaunched flows. One flow interview handles up to about 90 records; use the queue action or a bulk run for more.

Example: a screen flow on the Lead page that verifies the email and shows "Email is invalid" when Email status is invalid.

Tomba: Queue for Enrichment

Flags records Queued so Tomba processes them in the background (within minutes, or at the next hourly run). It makes no callout, so it works anywhere, including the immediate path of record-triggered flows.

InputDescription
Record IDA Lead, Contact or Account
Operationenrich (default), or any operation listed above

Example: when a Lead is converted, queue the new Contact for verify. Queued records count toward the automation budget.

Last modified on October 7, 2026
AutomationAgentforce
On this page
  • Tomba: Run on Record
  • Tomba: Queue for Enrichment