Integration
Connect Mailparser to Reepay
When something happens in Mailparser, your agent does the next thing in Reepay. 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 Reepay 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 Reepay
Triggers and actions 2 triggers · 20 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.
Action
Add couponCreate a new coupon. POST /v1/coupon
Action
Add creditCreate a credit note/credit for a customer. POST /v1/credit
Action
Add customerCreate a new customer. POST /v1/customer
Action
Add invoiceCreate an invoice for a customer. POST /v1/customer/{handle}/invoice
Action
Add planCreate a new subscription plan. POST /v1/plan
Action
Add subscriptionCreate a new subscription for a customer. POST /v1/subscription
Action
Cancel subscriptionCancel a subscription by handle. POST /v1/subscription/{handle}/cancel
Action
Delete customerDelete a customer by handle. DELETE /v1/customer/{handle}
Action
Get chargeRetrieve a charge by handle. GET /v1/charge/{handle}
Action
Get couponRetrieve a coupon by handle. GET /v1/coupon/{handle}
Action
Get customerRetrieve a customer by handle. GET /v1/customer/{handle}
Action
Get invoiceRetrieve an invoice by id. GET /v1/invoice/{id}
Action
Get planRetrieve the current version of a plan by handle. GET /v1/plan/{handle}/current
Action
Get subscriptionRetrieve a subscription by handle. GET /v1/subscription/{handle}
Action
List customersList all customers. GET /v1/list/customer
Action
List invoicesList all invoices. GET /v1/list/invoice
Action
List plansList all plans. GET /v1/list/plan
Action
List subscriptionsList all subscriptions. GET /v1/list/subscription
Action
Update customerUpdate an existing customer by handle. PUT /v1/customer/{handle}
Action
Update subscriptionChange/update an existing subscription by handle. PUT /v1/subscription/{handle}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.