Integration
Connect Pumble to Byteplant Phone Validator
When something happens in Pumble, 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.
Build it
What do you want Pumble 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 CodeEverything your agent can do with Pumble and Byteplant Phone Validator
Triggers and actions 1 trigger ยท 11 actions
Trigger
New MentionTriggers when a username is mentioned in a public channel.
Action
Create ChannelCreates a channel in the Workspace
Action
Find Channel by IDFind a channel by its ID.
Action
Find Channel by NameFind a channel by its Name.
Action
Find User by EmailFind a user by their Email.
Action
Find User by IDFind a user by their ID.
Action
Find User by NameFind user by their name.
Action
Send Channel MessageSend a message in a Pumble channel.
Action
Send Direct MessageSend a direct message to a user or yourself.
Action
Send Private Channel MessageSend a new message to a private channel or multi dm.
Action
Bulk Validate Phone NumbersUpload 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 NumberValidate a phone number.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.