Integration
Connect Customer.guru to Apimetro
When something happens in Customer.guru, 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 Customer.guru 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 Customer.guru and Apimetro
Triggers and actions 1 trigger · 10 actions
Trigger
New RatingTriggered when a customer submits a new rating on one of your Customer.guru surveys, giving you their score, their comment and how they engaged with the survey email.
Action
Find CustomerLooks up a customer in your Customer.guru account by email address and returns that customer's record — their id, when they were added, their most recent survey score and comment, and whether they have unsubscribed.
Action
Schedule SurveySends a Customer.guru NPS survey to one or more customers, either straight away or scheduled for a later date, and reports how many went out.
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.