Integration
Connect DocuPipe to openSenseMap
When something happens in DocuPipe, 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 DocuPipe 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 DocuPipe and openSenseMap
Triggers and actions 1 trigger ยท 23 actions
Trigger
Document ProcessedTriggers when a document finishes parsing and OCR is complete.
Action
Add schemaCreates a new extraction schema in DocuPipe from a JSON schema you supply, and returns its schema ID.
Action
Analyze documentAsks DocuPipe a list of plain-language questions about one document and starts the analysis, returning the analysis ID to fetch the answers with.
Action
Classify DocumentSends one or more documents to DocuPipe to be sorted into your classes, and returns the job that is doing the work.
Action
Delete documentRemoves a document from your DocuPipe account.
Action
Delete schemaRemoves an extraction schema from your DocuPipe account.
Action
Extract Data From DocumentPulls structured data out of a document using one of your schemas, and returns the extraction to fetch the results with.
Action
Find documents by criteriaFinds documents in your DocuPipe account whose file name or document ID matches what you search for.
Action
Get DocumentReturns one document from your DocuPipe account, with its file details, processing status, parsed text and your own metadata.
Action
Get Extraction ResultReturns the data DocuPipe pulled out of a document, shaped by the schema that was used, along with per-field confidence details.
Action
Get schemaReturns one extraction schema from your DocuPipe account, including the JSON schema it applies and its guidelines.
Action
List documentsReturns the documents in your DocuPipe account, optionally narrowed to one dataset or a date range.
Action
List extractionsReturns the data extractions in your DocuPipe account, optionally narrowed to one schema, one document, or a specific set of extractions.
Action
List schemasReturns the extraction schemas in your DocuPipe account.
Action
Upload and Extract DataSends a file to DocuPipe and immediately starts pulling structured data out of it, returning both the new document and the extraction.
Action
Upload DocumentSends a file to DocuPipe to be read and turned into a document you can extract data from.
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)
Action
Find senseBoxes near locationSearch senseBoxes near a given coordinate/bounding box and phenomenon. GET /boxes with near/bbox query params
Action
Get 10000 latest measurements for sensorFetch up to the 10000 latest raw measurements for one sensor, with optional from-date/to-date filters. GET /boxes/:senseBoxId/data/:sensorId
Action
Get database statisticsFetch overview statistics about the openSenseMap database (box count, sensor count, measurement count). GET /stats
Action
Get latest measurements of senseBoxFetch the latest measurements of all sensors for a given senseBox. GET /boxes/:senseBoxId/sensors
Action
Get latest measurements of sensorFetch the latest measurement value for one specific sensor of a senseBox. GET /boxes/:senseBoxId/sensors/:sensorId
Action
Get senseBoxFetch details for one senseBox station by its ID. GET /boxes/:senseBoxId
Action
List senseBoxesList 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.