Integration
Connect Mobile Text Alerts to SLF
When something happens in Mobile Text Alerts, your agent does the next thing in SLF. 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 SLF 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 SLF
Triggers and actions 3 triggers · 6 actions
Trigger
Delivery StatusTriggers when the delivery status of a message is updated.
- Message Reply
Triggers when a new message reply is received.
- Message Sent
Triggers when a new message is sent.
- Add Subscriber
Adds a subscriber.
- Add Subscriber to Group
Puts a phone number that has been previously added to a group.
- Delete All Scheduled Messages
This will delete all scheduled messages for a number.
- Remove Subscriber From Group
Removes a subscriber from a group.
- Send Message
Sends a message.
Action
Get Stadt-Land-Fluss dataFetch the full German Stadt-Land-Fluss (city/country/river word-game) reference dataset via GET https://slftool.github.io/data.json. Static, unauthenticated, single-request JSON blob keyed by letter, each letter holding arrays for stadt (city), land (country), fluss (river), name, beruf (profession), tier (animal), and marke (brand). No query parameters — the vendor exposes no filtering or search; the whole dataset is returned every call and any per-letter/per-category lookup must be done client-side on the response.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.