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

Automation

Turn these on in Tomba Setup › Automation:

OptionWhen it runs
Enrich new Leads / ContactsA Lead or Contact is created
Enrich new AccountsAn Account is created, or its website changes
Verify emails when added or changedA Lead or Contact gets a new email
Find emails for records without oneA Lead or Contact is created without an email
Re-verify emails older than N daysHourly, for emails last verified more than N days ago
Re-verify emails that bounceSalesforce marks the email as bounced (needs bounce management). If the email is bad, Tomba looks for a replacement and stores it in Tomba Suggested Email — the Tomba Insights panel offers Use this email

Records are marked Tomba Sync Status = Queued when they are saved and processed in the background a few minutes later. Records created by users without Tomba access (web-to-lead, integrations) are processed by the hourly job, which runs as the admin who saved the settings.

Monthly credit budget caps the credits automation may use per month. When it is reached, records stay Queued until the next month or until you raise the budget. Record actions and bulk jobs don't count toward it.

To keep a data load out of automation, give the loading user the Tomba: Bypass Automation custom permission.

In a sandbox, automation is off unless you allow it — see Sandboxes. Automation also pauses after a low-credit alert when you choose so — see Usage, limits and alerts.

Last modified on October 7, 2026
List views and bulk runsFlow actions