Integration
Connect Mobile Text Alerts to Browser Use
When something happens in Mobile Text Alerts, your agent does the next thing in Browser Use. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Mobile Text Alerts and Browser Use 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 Mobile Text Alerts and Browser Use
Triggers and actions 3 triggers ยท 12 actions
Trigger
Delivery StatusTriggers when the delivery status of a message is updated.
Trigger
Message ReplyTriggers when a new message reply is received.
Trigger
Message SentTriggers when a new message is sent.
Action
Add SubscriberAdds a subscriber.
Action
Add Subscriber to GroupPuts a phone number that has been previously added to a group.
Action
Delete All Scheduled MessagesThis will delete all scheduled messages for a number.
Action
Remove Subscriber From GroupRemoves a subscriber from a group.
Action
Send MessageSends a message.
Action
Delete profileDelete a browser profile.
Action
Delete workspaceDelete a workspace.
Action
Get profileGet the details of a specific browser profile.
Action
Get workspaceGet the details of a specific workspace.
Action
List workspace filesList files stored in a workspace.
Action
Update profileUpdate a browser profile.
Action
Upload workspace filesUpload files into a workspace.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.