Integration
Connect systeme.io to openSenseMap
When something happens in systeme.io, your agent does the next thing in openSenseMap. 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 openSenseMap 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 openSenseMap
Triggers and actions 1 trigger ยท 18 actions
Trigger
New Tag Added to ContactTriggers when a tag is added to contact.
- Add digital product
Create a new payment Digital Product resource. POST /api/payment/digital-products
- Add tag to contact
Assign an existing Tag to a Contact by id (distinct from create-or-update-with-tags). POST /api/contacts/{id}/tags
- Create or Update a Contact, Including Adding Tags
Creates a contact in systeme.io, or updates the existing contact with that email address, and applies any tags you list.
- Delete contact
Remove a Contact resource by id. DELETE /api/contacts/{id}
- Find contacts by email
Search Contact resources filtered by email address. GET /api/contacts?email=
- Get contact
Retrieve a single Contact resource by id. GET /api/contacts/{id}
- List contacts
Retrieve the collection of Contact resources, paginated. GET /api/contacts
- List digital products
Retrieve the collection of payment Digital Product resources. GET /api/payment/digital-products
- List tags
Retrieve the collection of Tag resources. GET /api/tags
- Remove Tag
Removes tag from a contact
Action
Find measurements by phenomenonFetch the latest measurements for all sensors measuring a given phenomenon/grouptag, as JSON or CSV. GET /statistics/idw or /boxes/data (phenomenon-scoped query)
- Find senseBoxes near location
Search senseBoxes near a given coordinate/bounding box and phenomenon. GET /boxes with near/bbox query params
- Get 10000 latest measurements for sensor
Fetch up to the 10000 latest raw measurements for one sensor, with optional from-date/to-date filters. GET /boxes/:senseBoxId/data/:sensorId
- Get database statistics
Fetch overview statistics about the openSenseMap database (box count, sensor count, measurement count). GET /stats
- Get latest measurements of senseBox
Fetch the latest measurements of all sensors for a given senseBox. GET /boxes/:senseBoxId/sensors
- Get latest measurements of sensor
Fetch the latest measurement value for one specific sensor of a senseBox. GET /boxes/:senseBoxId/sensors/:sensorId
- Get senseBox
Fetch details for one senseBox station by its ID. GET /boxes/:senseBoxId
- List senseBoxes
List all senseBox stations, optionally filtered by bounding box/phenomenon/exposure. GET /boxes
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews