Integration
Connect Colorado Information Marketplace to Open Science Framework
When something happens in Colorado Information Marketplace, your agent does the next thing in Open Science Framework. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Colorado Information Marketplace and Open Science Framework 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 Colorado Information Marketplace and Open Science Framework
Triggers and actions 4 triggers · 23 actions
Trigger
New recordPolling trigger: fires when a new row appears in a specified Colorado Information Marketplace (Socrata SODA API) dataset. GET https://data.colorado.gov/resource/{dataset_id}.json ordered by a rowid/created/updated system field ($order=:id DESC or an updated_at column) with $limit, dedup by the row's system id (:id) or an updated_at watermark since datasets vary in whether they expose a stable update timestamp column.
Action
Find datasetsSearch the Colorado Information Marketplace open-data catalog for datasets by keyword/category. GET https://data.colorado.gov/api/catalog/v1?q={query}&limit=... (Socrata Discovery API) returning dataset id, name, description, category, and update timestamps. Used to locate the dataset identifier that other ops (List/Get/Find records) require as input.
Action
Find records by criteriaQuery a Colorado Information Marketplace (Socrata SODA API) dataset with a SoQL $where/$select/$order filter. GET https://data.colorado.gov/api/v3/views/{dataset_id}/query.json (or resource/{dataset_id}.json on older SODA2 endpoints) with SoQL query params ($where, $select, $order, $limit, $offset). Requires the dataset identifier (8-char alphanumeric, e.g. ydr8-5enu) as input plus the SoQL clauses.
Action
Get recordGet a single row from a Colorado Information Marketplace (Socrata SODA API) dataset by its row identifier. GET https://data.colorado.gov/resource/{dataset_id}/{row_id}.json (or a $where=:id='{row_id}' query when the dataset has no explicit row identifier). Requires dataset_id and row_id.
Action
List recordsList all rows in a Colorado Information Marketplace (Socrata SODA API) dataset, paginated. GET https://data.colorado.gov/resource/{dataset_id}.json with $limit/$offset params. Requires the dataset identifier (8-char alphanumeric, e.g. ydr8-5enu).
Trigger
New commentPolling trigger that fires when a new comment is added to an OSF project.
Trigger
New preprintPolling trigger that fires when a new OSF preprint is created.
Trigger
New registrationPolling trigger that fires when a new OSF registration is created.
Action
Get collectionRetrieve a single OSF collection.
Action
Get contributorRetrieve a single contributor on an OSF project.
Action
Get fileRetrieve metadata for a single OSF file.
Action
Get preprintRetrieve a single OSF preprint.
Action
Get projectRetrieve a single OSF project by id.
Action
Get registrationRetrieve a single OSF registration.
Action
Get resourceRetrieve a single OSF outcome resource.
Action
Get userRetrieve a single OSF user.
Action
Get wiki pageRetrieve a single OSF wiki page.
Action
List collectionsList OSF collections.
Action
List commentsList comments on an OSF project.
Action
List contributorsList the contributors on an OSF project.
Action
List preprintsList OSF preprints.
Action
List project filesList the files stored in an OSF project.
Action
List projectsList OSF projects (nodes) visible to the user.
Action
List registrationsList OSF registrations.
Action
List resourcesList OSF outcome resources.
Action
List usersList OSF users.
Action
List wiki pagesList the wiki pages on an OSF project.
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