Can Lyro find or verify an email address through Tomba?

Not with this toolkit. Its actions cover the lead database, lead lists, API keys, and usage statistics, and the only deliverability check available is Domain Status, which reports whether a domain is webmail or disposable. Email discovery and per-address verification stay in Tomba itself.

How does Lyro know which fields our leads are supposed to carry?

List Lead Attributes returns every custom attribute defined on your Tomba account with its name, identifier, and type. Lyro reads that before creating a lead, so it populates the fields your team actually configured rather than only first_name and email, which are the two Create Lead requires.

Whose Tomba quota do these calls consume?

Your account's. Every action runs against the Tomba credentials you connect, so lead creation and domain checks draw down that plan. Get Usage Statistics reports where usage stands, which is how Lyro can flag a limit before it is reached rather than after a call fails.

Should Lyro be able to revoke Tomba API keys?

That is a deliberate choice to make when you connect it. Delete API Key by ID permanently revokes a key before its expiration and needs the numeric ID from List API Keys first, which makes it the most destructive action here and one worth keeping to internal workflows rather than customer-facing chat.

Tomba MCP integration

Creates leads from the details a conversation surfaces, flags webmail and disposable domains, tidies lead lists, and reports remaining API quota.

Connect Tomba See all integrations

10actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Create lead
Lyro adds a new lead to Tomba's database with all key details in one action. Sales teams eliminate manual data entry on web form submissions.
Update leads list
Lyro renames a leads list by its ID to stay organized as campaigns evolve. Teams keep segment names aligned with current outreach without confusion.
Domain status
Lyro checks whether a domain is webmail or disposable to validate email quality. Sales avoids wasting outreach on unreachable or throwaway addresses.

See all 10 actions

How businesses use Tomba + Lyro

Each card is one request a support team gets, and the Tomba actions Lyro runs to close it.

Capture a lead the moment a conversation qualifies one
Lyro creates the Tomba lead with the first name and email it has confirmed, fills in whichever custom attributes your account defines, and returns the new lead ID for whatever picks it up next.
Create LeadList Lead AttributesList Leads
Screen an address before it enters the database
Before a lead is stored, Lyro checks whether its domain is webmail or disposable, so a personal or throwaway address is flagged at capture rather than discovered later by a bounced campaign.
Domain StatusCreate LeadList Leads
Keep lead lists named and pruned
Lyro pages through the lead lists on the account, renames the one that no longer matches the campaign it was built for, and permanently removes a list once its ID has been confirmed.
List Lead ListsUpdate Leads ListDelete Leads List by ID
Audit API keys and usage against the plan
Lyro lists the API keys issued on the account, revokes one by its numeric ID ahead of expiry when it should no longer work, and reports current usage so a limit is not hit mid-campaign.
List API KeysDelete API Key by IDGet Usage Statistics

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Tomba actions it has and picks the ones a request needs.

01
Connect Tomba
Authorize the Tomba account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Tomba actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Tomba · Lyro

Everything else about Tomba

Setup, permissions, and the limits of what Lyro can do inside Tomba.

Not with this toolkit. Its actions cover the lead database, lead lists, API keys, and usage statistics, and the only deliverability check available is Domain Status, which reports whether a domain is webmail or disposable. Email discovery and per-address verification stay in Tomba itself.

Every action available in Tomba

All 10 actions your agent can call on Tomba, straight from the live MCP connection.

List lead attributes
Retrieves all custom lead attributes defined in your Tomba account.
Domain status
Check if a domain is webmail or disposable.
Delete API key by ID
Delete an API key by its numeric ID.
List API keys
List all API keys.
Create lead
Create a new lead in Tomba's lead database.
List leads
List all leads.
Delete leads list by ID
Delete a leads list by ID.
List lead lists
List all lead lists.
Update leads list
Update a leads list's name by ID.
Get usage statistics
Get API usage statistics.