Integration
Connect Langfuse to Urgences Québec
When something happens in Langfuse, 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 Langfuse 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 Langfuse and Urgences Québec
Triggers and actions 1 trigger · 18 actions
Trigger
New TracePolling trigger: fires for newly created traces (dedup by trace id / timestamp). GET /api/public/traces
Action
Add CommentAdd a comment to a trace/observation/session/prompt object. POST /api/public/comments
Action
Add DatasetCreate a new dataset. POST /api/public/v2/datasets
Action
Add Dataset ItemCreate an item (input/expected_output/metadata) in a dataset. POST /api/public/dataset-items
Action
Add PromptCreate a new prompt version (text or chat). POST /api/public/v2/prompts
Action
Add ScoreCreate a score attached to a trace/observation/session (numeric, categorical, or boolean). POST /api/public/scores
Action
Delete TraceDelete a trace by id. DELETE /api/public/traces/{traceId}
Action
Get ProjectReads the Langfuse project that the connection's project-scoped API key belongs to.
Action
Get PromptGet a prompt by name (and optional version/label). GET /api/public/v2/prompts/{promptName}
Action
Get TraceGet a single trace by id, including nested observations/scores. GET /api/public/traces/{traceId}
Action
List Dataset ItemsList items in a dataset. GET /api/public/dataset-items
Action
List DatasetsList all datasets in the project. GET /api/public/v2/datasets
Action
List PromptsList all prompts in the project. GET /api/public/v2/prompts
Action
List ScoresList scores with optional filters. GET /api/public/v2/scores
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