Integration
Connect Vouchsafe to Urgences Québec
When something happens in Vouchsafe, 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 Vouchsafe 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 Vouchsafe and Urgences Québec
Triggers and actions 2 triggers · 13 actions
Trigger
User Needs ReviewTriggers when a user could not be automatically verified, and needs your review.
Trigger
User VerifiedTriggers when a verification is automatically completed.
Action
Find addresses by postcodeSearch for addresses matching a given postcode. GET /api/v1/postcode-search (SearchPostcode).
Action
Get account detailRetrieve details for a specific monitored account (subject of an alert). GET /api/v1/accounts/{id} (GetAccountDetail).
Action
Get teamRetrieve details for a Vouchsafe team/workspace by ID. GET /api/v1/teams/{id} (GetTeam).
Action
Get verificationRetrieve a verification case's status and check results by ID. GET /api/v1/verifications/{id}.
Action
List verificationsList verification cases for the team. GET /api/v1/verifications.
Action
Perform smart lookupLook up and enrich identity details (e.g. email/phone) via Vouchsafe's smart lookup service. POST /api/v1/smart-lookups (PerformSmartLookup).
Action
Request VerificationStarts a verification session for an applicant, new user or customer.
Action
Toggle alertsEnable or disable proactive alert monitoring for an account. POST /api/v1/accounts/{id}/toggle-alerts (ToggleAlerts).
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