Integration
Connect systeme.io to Apimetro
When something happens in systeme.io, 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 systeme.io 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 systeme.io and Apimetro
Triggers and actions 1 trigger ยท 18 actions
Trigger
New Tag Added to ContactTriggers when a tag is added to contact.
Action
Add digital productCreate a new payment Digital Product resource. POST /api/payment/digital-products
Action
Add tag to contactAssign an existing Tag to a Contact by id (distinct from create-or-update-with-tags). POST /api/contacts/{id}/tags
Action
Create or Update a Contact, Including Adding TagsCreates a contact in systeme.io, or updates the existing contact with that email address, and applies any tags you list.
Action
Delete contactRemove a Contact resource by id. DELETE /api/contacts/{id}
Action
Find contacts by emailSearch Contact resources filtered by email address. GET /api/contacts?email=
Action
Get contactRetrieve a single Contact resource by id. GET /api/contacts/{id}
Action
List contactsRetrieve the collection of Contact resources, paginated. GET /api/contacts
Action
List digital productsRetrieve the collection of payment Digital Product resources. GET /api/payment/digital-products
Action
List tagsRetrieve the collection of Tag resources. GET /api/tags
Action
Remove TagRemoves tag from a contact
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.