Integration
Connect Mobile Text Alerts to Apimetro
When something happens in Mobile Text Alerts, your agent does the next thing in Apimetro. 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 Apimetro 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 Apimetro
Triggers and actions 3 triggers ยท 13 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
Get line ridership analyticsGet monthly ridership (afluencia) statistics per transport line. Endpoint: GET /analitico/afluencia-linea.
Action
Get polygon map dataGet GeoJSON geometry for administrative polygons. Endpoint: GET /mapas/geojsonPoligono.
Action
Get station map dataGet GeoJSON geometry for stations. Endpoint: GET /mapas/geojsonEstacion.
Action
Get station ridership analyticsGet monthly ridership (afluencia) statistics per station. Endpoint: GET /analitico/afluencia-estacion.
Action
Get urban AGEB boundariesGet GeoJSON boundaries for urban AGEBs (statistical geographic areas). Endpoint: GET /analitico/agebs.
Action
List line descriptionsList the descriptive metadata records for lines on a given transport system. Endpoint: GET /{sistema}/descripcion-linea.
Action
List linesList the transport lines on a given transport system, with their stations. Endpoint: GET /{sistema}/linea.
Action
List stationsList the stations on a given transport system, with their coordinates. Endpoint: GET /{sistema}/estacion.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.