Integration
Connect Airbrake to District of Columbia Open Data
When something happens in Airbrake, your agent does the next thing in District of Columbia Open Data. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Airbrake and District of Columbia Open Data 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 Airbrake and District of Columbia Open Data
Triggers and actions 1 trigger · 17 actions
Trigger
New errorTriggered when any new error is reported.
Action
Create noticeSubmit a new error notice to Airbrake — report an error from an automation.
Action
Delete error groupDelete/resolve an Airbrake error group by id.
Action
Get error groupFetch details for a single error group.
Action
Get projectFetch details for a single project by ID.
Action
List activitiesList the audit-log activities for an Airbrake project — deploys, mutes, resolves, etc.
Action
List deploysList recorded deploys for an Airbrake project.
Action
List error groupsList error groups (aggregated errors) for a project.
Action
List noticesList individual notices (occurrences) for an error group.
Action
List projectsList all projects accessible to the authenticated user key.
Action
List source mapsList the uploaded source maps for an Airbrake project.
Action
Mute error groupMute an error group so it no longer triggers notifications.
Action
Record deployRecord a new deployment for a project (environment, revision, version, etc.).
Action
Show deployRetrieve a single Airbrake deploy by id.
Action
Unmute error groupUnmute a previously muted error group to re-enable notifications.
Action
Find datasetsSearch the DC Open Data catalog for datasets by keyword, category, or tag, returning matching dataset ids, titles, and descriptions.
Action
Find recordsQuery a dataset's features/records with attribute filters, spatial filters, sorting, and paging, returning JSON or GeoJSON results.
Action
Get datasetGet a dataset's metadata and field/schema definitions by dataset or layer id, so callers know what attributes can be filtered or returned.
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