Integration
Connect Airbrake to Urgences Québec
When something happens in Airbrake, your agent does the next thing in Urgences Québec. 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 Urgences Québec 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 Urgences Québec
Triggers and actions 1 trigger · 19 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
Get hospital historyHourly occupancy history for one hospital. GET /api/facility/{id}/history?days=7 — id is the MSSS permit number from List hospitals/List emergency departments; days ranges 1-56 (default 7). Returns rows of { ts, occ_pct, waiting, present }. No auth.
Action
Get surgery wait listsProvincial surgery wait lists by procedure and hospital. GET /api/chirurgies — returns { snap: { fetchedAt, latestPeriod, periods, regions, latest, trend, trend12, hospitals, hospPeriod }, centroids }. No auth, no params.
Action
List emergency departmentsCurrent occupancy reading for all 120 Quebec emergency departments. GET /api/now — returns updatedAt/fetchedAt plus rows of id (MSSS permit number), name, establishment, region, civFonct/civOcc (stretcher capacity/occupied), occPct, p24h/p48h, present, waiting, dmsCiviereMin/dmsAmbMin, ts. No auth, no params.
Action
List hospitalsStatic directory of the same 120 Quebec hospitals covered by /api/now. GET /api/facilities — returns id (MSSS permit number), name, establishment, region_code, region_name, address, lat, lng, phone, slug. No auth, no params.
Action
List walk-in clinicsWalk-in clinic snapshot across Quebec regions. GET /api/cliniques — returns { snap: { fetchedAt, from, to, regions, clinics }, centroids }; each clinic row carries rts/rtsName/rls, name, total, med, inf, ev, days, blocks, dow. No auth, no params.
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