Integration
Connect PostHog to openSenseMap
When something happens in PostHog, 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 PostHog 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 PostHog and openSenseMap
Triggers and actions 1 trigger ยท 18 actions
Trigger
Action PerformedTriggers when an action is performed by a user.
- Add annotation
Create a new annotation on the project timeline (content, date_marker, scope). POST /api/projects/:project_id/annotations/
- Capture Event
Captures an event.
- Evaluate feature flags
Evaluate all feature flag values for a given distinct_id/person, returning flag states for use in automation branching. Public POST /flags endpoint (project token auth).
- Get person
Retrieve a single person by ID. GET /api/projects/:project_id/persons/:id/
- List annotations
List annotations in the project. GET /api/projects/:project_id/annotations/
- List cohorts
List cohorts defined in the project. GET /api/projects/:project_id/cohorts/
- List feature flags
List feature flags defined in the project. GET /api/projects/:project_id/feature_flags/
- List insights
List saved insights (charts/graphs) in the project. GET /api/projects/:project_id/insights/
- List persons
List/search persons in the project, optionally filtered by distinct_id or properties. GET /api/projects/:project_id/persons/
- Update person
Update a person's properties by ID. PATCH /api/projects/:project_id/persons/:id/
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.