Integration
Connect Mailparser to PostHog
When something happens in Mailparser, your agent does the next thing in PostHog. 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 PostHog 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 PostHog
Triggers and actions 3 triggers · 10 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.
- 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
Action PerformedTriggers when an action is performed by a user.
- Add annotation
Create a new annotation on the project timeline (content, date_marker, scope). POST /api/projects/:project_id/annotations/
- Capture Event
Captures an event.
- Evaluate feature flags
Evaluate all feature flag values for a given distinct_id/person, returning flag states for use in automation branching. Public POST /flags endpoint (project token auth).
- Get person
Retrieve a single person by ID. GET /api/projects/:project_id/persons/:id/
- List annotations
List annotations in the project. GET /api/projects/:project_id/annotations/
- List cohorts
List cohorts defined in the project. GET /api/projects/:project_id/cohorts/
- List feature flags
List feature flags defined in the project. GET /api/projects/:project_id/feature_flags/
- List insights
List saved insights (charts/graphs) in the project. GET /api/projects/:project_id/insights/
- List persons
List/search persons in the project, optionally filtered by distinct_id or properties. GET /api/projects/:project_id/persons/
- Update person
Update a person's properties by ID. PATCH /api/projects/:project_id/persons/:id/
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.