Integration

Connect lemlist to Byteplant Phone Validator

When something happens in lemlist, your agent does the next thing in Byteplant Phone Validator. Describe it in plain language and the automation is built, tested on every branch and kept running.

lemlist1 triggerlemlist8 actionsByteplant Phone Validator2 actions

Browse all apps

Build it

What do you want lemlist and Byteplant Phone Validator to do together?

Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Or work from Claude Code

Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.

Connect Claude Code

Everything your agent can do with lemlist and Byteplant Phone Validator

Triggers and actions 1 trigger · 10 actions

Trigger
New Activity
Triggers when an activity has ocurred. It can be an email has been sent, replied to, bounced, or unsubscribed from or v3 new activity like a LinkedIn profile have been visited or a phone call just ended.
Action
Add Recipient to Unsubscribe List
Add a recipient to the unsubscribe list.
Action
Mark a Lead From All Campaigns as Interested
Mark a Lead From All Campaigns as Interested.
Action
Mark a Lead From One Campaign as Interested
Mark a Lead From One Campaign as Interested.
Action
Remove Lead From Campaign
Remove a Lead from a campaign.
Action
Remove Lead From Unsubscribe
Remove a Lead from unsubscribe.
Action
Resume Lead From All or Specific Campaigns
Resume Lead From All or Specific Campaigns.
Action
Search Lead
Search a lead.
Action
Update Lead From Campaign
Update Lead From Campaign.
Action
Bulk Validate Phone Numbers
Upload a CSV file (up to 100K phone numbers) for asynchronous bulk validation. POST https://api.phone-validator.net/api/v2/bulk-verify with Content-Type: text/csv and the CSV as the raw request body. Params: APIKey (required), TaskName, CountryCode, Locale, Mode (express|extensive), NotifyEmail, NotifyURL (optional). Response: {status: SUCC|FAIL, info: <task id if SUCC>}. Completion is announced via email and/or an HTTP GET to NotifyURL with a taskid query param; the vendor docs do not expose a separate poll/result-fetch endpoint.
Action
Validate Phone Number
Validate a phone number.

Each app on its own

The other way round: Byteplant Phone Validator to lemlist