Integration
Connect Pushbullet to Urgences Québec
When something happens in Pushbullet, 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 Pushbullet 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 Pushbullet and Urgences Québec
Triggers and actions 1 trigger · 26 actions
Trigger
New PushPolling trigger: fires for each new push received, ordered by modified time.
Action
Create DeviceCreate a new device on your Pushbullet account.
Action
Create Pushsend a push (note, link, or file)
Action
Create SubscriptionSubscribe to a channel by its channel tag.
Action
Delete All Pushesdelete all pushes
Action
Delete ChatDelete a chat by iden.
Action
Delete DeviceDelete a device by iden.
Action
Delete PushDelete a push by iden.
Action
Delete SubscriptionUnsubscribe from a channel by subscription iden.
Action
Get Channel InfoGet information about a channel by its tag.
Action
Get Current UserGet information about the authenticated Pushbullet user.
Action
List ChatsList the chats (people you've pushed to) on your account.
Action
List DevicesList the devices on your Pushbullet account.
Action
List PushesList pushes, optionally only active and modified after a timestamp.
Action
List SubscriptionsList the channels you are subscribed to.
Action
Request File Uploadrequest authorization to upload a file
Action
Send a LinkPush a link (title + body + url) to a device, email, channel, or all your devices.
Action
Send a NotePush a note (title + body) to a device, email, channel, or all your devices.
Action
Update Chatupdate a chat (mute)
Action
Update Deviceupdate a device
Action
Update PushMark a push as dismissed.
Action
Update Subscriptionupdate a subscription (mute)
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.