Integration
Connect Mailparser to Langfuse
When something happens in Mailparser, your agent does the next thing in Langfuse. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Mailparser and Langfuse 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 Mailparser and Langfuse
Triggers and actions 3 triggers · 13 actions
Trigger
New Email Parsed (One Request Per Email)Triggered instantly when Mailparser finishes parsing an inbound email, with all of that email's parsed data delivered in a single request. In Mailparser, open your inbox and add a Generic Webhook under Integrations/Downstream Webhooks, paste the minted URL, and set Repeating Data Behaviour to "One request per Email". Parsed fields bind as {{ trigger.body.* }}. Use the One Request Per Row trigger instead when you are parsing tabular data and want each row handled as its own run.
Trigger
New Email Parsed (One Request Per Row)Triggered instantly for EACH parsed table row when Mailparser finishes parsing an inbound email — one run per row, for tabular data such as invoice line items or price lists. In Mailparser, open your inbox and add a Generic Webhook under Integrations/Downstream Webhooks, paste the minted URL, and set Repeating Data Behaviour to "One request per row". That row's fields bind as {{ trigger.body.* }}. Use the One Request Per Email trigger instead when you want the whole email's parsed data in a single run.
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
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