Integration
Connect Langfuse to Represent by Open North
When something happens in Langfuse, your agent does the next thing in Represent by Open North. 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 Represent by Open North 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 Represent by Open North
Triggers and actions 1 trigger · 20 actions
Trigger
New TracePolling trigger: fires for newly created traces (dedup by trace id / timestamp). GET /api/public/traces
- Add Comment
Add a comment to a trace/observation/session/prompt object. POST /api/public/comments
- Add Dataset
Create a new dataset. POST /api/public/v2/datasets
- Add Dataset Item
Create an item (input/expected_output/metadata) in a dataset. POST /api/public/dataset-items
- Add Prompt
Create a new prompt version (text or chat). POST /api/public/v2/prompts
- Add Score
Create a score attached to a trace/observation/session (numeric, categorical, or boolean). POST /api/public/scores
- Delete Trace
Delete a trace by id. DELETE /api/public/traces/{traceId}
- Get Project
Reads the Langfuse project that the connection's project-scoped API key belongs to.
- Get Prompt
Get a prompt by name (and optional version/label). GET /api/public/v2/prompts/{promptName}
- Get Trace
Get a single trace by id, including nested observations/scores. GET /api/public/traces/{traceId}
- List Dataset Items
List items in a dataset. GET /api/public/dataset-items
- List Datasets
List all datasets in the project. GET /api/public/v2/datasets
- List Prompts
List all prompts in the project. GET /api/public/v2/prompts
- List Scores
List scores with optional filters. GET /api/public/v2/scores
Action
Find representatives by pointFind elected officials for a given latitude/longitude. GET /representatives/?point={lat},{lng} (optionally scoped to a representative set via /representatives/{set}/?point=...); supports filters like last_name, party_name, elected_office.
- Find representatives by postal code
Look up elected officials and boundaries covering a Canadian postal code. GET /postcodes/{postal_code}/ — returns boundaries_centroid, boundaries_concordance, representatives_centroid, representatives_concordance; optional sets query param restricts to a boundary set.
- List boundaries
Paginated list of electoral boundaries. GET /boundaries/ (optionally /boundaries/{boundary_set}/, or comma-separated multiple sets via ?sets=); filterable by name/external_id.
- List boundaries covering a point
Find electoral boundaries containing a given latitude/longitude. GET /boundaries/?contains={lat},{lng} (optionally scoped to a boundary set via /boundaries/{set}/?contains=...).
- List boundary sets
List available boundary sets (groups of electoral districts, e.g. federal-electoral-districts, toronto-wards). GET /boundary-sets/; filterable by name/domain. GET /boundary-sets/{slug}/ for a single set.
- List candidates
Paginated list of electoral candidates for tracked elections. GET /candidates/ — behaves like /representatives/, filterable by name, first_name, last_name, gender, district_name, party_name.
- List representatives
Paginated list of elected officials. GET /representatives/ (optionally /representatives/{representative_set}/); filterable by name, first_name, last_name, gender, district_name, elected_office, party_name.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.