Integration
Connect BotMape to Urgences Québec
When something happens in BotMape, 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 BotMape 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 BotMape and Urgences Québec
Triggers and actions 1 trigger · 13 actions
Trigger
New Lead CapturedTriggers when a new lead is captured — either from a chat conversation or added manually.
Action
Add agentCreate a new AI agent with custom configuration and personality. POST /api/chatbots
Action
Add knowledge base entryAdd training content (FAQ, documentation, policies) to an AI agent; auto-embedded. POST /api/chatbots/:chatbotId/knowledge
Action
Create LeadCreates a new lead in your CRM. Use this to push leads from other tools into your CRM automatically.
Action
Delete knowledge base entryRemove a specific knowledge entry from an AI agent's training data. DELETE /api/chatbots/:chatbotId/knowledge/:knowledgeId
Action
Get agentRetrieve detailed information about a specific AI agent by ID. GET /api/chatbots/:id
Action
List agentsGet all AI agents owned by the authenticated user with their configurations. GET /api/chatbots
Action
List knowledge base entriesRetrieve all knowledge base entries that train an AI agent's responses. GET /api/chatbots/:chatbotId/knowledge
Action
Update agentUpdate an existing AI agent's configuration, personality, or appearance. PUT /api/chatbots/:id
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.