Integration
Connect Colorado Information Marketplace to Updown.io
When something happens in Colorado Information Marketplace, your agent does the next thing in Updown.io. 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 Updown.io 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 Updown.io
Triggers and actions 1 trigger ยท 14 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).
Action
Create CheckCreates a new uptime check in updown.io for a URL you want monitored, and returns the created check including its token.
Action
Create RecipientAdds a new alert recipient (email, SMS, webhook, Slack-compatible or Microsoft Teams) to your updown.io account and returns the created recipient.
Action
Delete CheckDeletes an uptime check from updown.io by its token.
Action
Delete RecipientRemoves an alert recipient from your updown.io account by its id.
Action
Get CheckReturns a single updown.io uptime check by its token, including its current status, uptime and settings.
Action
Get Check MetricsReturns performance metrics for an updown.io check over a period โ uptime, apdex, request counts and average timings, optionally grouped by time or monitoring location.
Action
List ChecksReturns every uptime check on your updown.io account with its current status and settings.
Action
List DowntimesReturns the recorded outages for an updown.io check, newest first, with the reason, start and end times and duration of each.
Action
List RecipientsReturns every alert recipient on your updown.io account โ email addresses, phone numbers, webhooks and chat integrations.
Action
Update CheckUpdates the settings of an existing updown.io uptime check โ its URL, name, interval, threshold, alert muting and more. Anything left blank keeps its current value.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.