# Automation

Turn these on in **Tomba Setup › Automation**:

| Option                                   | When it runs                                              |
| ---------------------------------------- | --------------------------------------------------------- |
| Enrich new Leads / Contacts              | A Lead or Contact is created                              |
| Enrich new Accounts                      | An Account is created, or its website changes             |
| Verify emails when added or changed      | A Lead or Contact gets a new email                        |
| Find emails for records without one      | A Lead or Contact is created without an email             |
| Re-verify emails older than N days       | Hourly, for emails last verified more than N days ago     |
| Re-verify emails that bounce             | Salesforce 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](/salesforce/sandboxes). Automation also
pauses after a low-credit alert when you choose so — see [Usage, limits and alerts](/salesforce/usage-and-limits).