Integration
Connect Mailparser to Jumpseller
When something happens in Mailparser, your agent does the next thing in Jumpseller. 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 Jumpseller 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 Jumpseller
Triggers and actions 8 triggers · 17 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
Customer CreatedTriggers when a new customer registers into the store.
Trigger
Customer UpdatedTriggers when a customer is updated.
Trigger
Order PaidTriggers when a new order is paid.
Trigger
Order UpdatedTriggers when an order status is updated (from an initial "pending payment" to either a "paid", "canceled" or "abandoned" status).
Trigger
Product CreatedTriggers when a new product is created.
Trigger
Product UpdatedTriggers when a product is updated.
Action
Add CategoryCreate a new Category. POST /categories.json
Action
Add CustomerAdds a new customer to your Jumpseller store.
Action
Create ProductCreates a Product
Action
Create Product VariantCreates a new Product Variant
Action
Delete CustomerDelete an existing Customer. DELETE /customers/{id}.json
Action
Delete ProductDelete an existing Product. DELETE /products/{id}.json
Action
Find Customer From EmailFinds a customer in your Jumpseller store by their email address.
Action
Find ProductFinds a Jumpseller Product, returning the full product details (including its variants)
Action
Find Product From SKUFinds a product given a SKU, ID or Barcode
Action
Get CustomerRetrieve a single Customer by id. GET /customers/{id}.json
Action
Get ProductRetrieve a single Product by id. GET /products/{id}.json
Action
List CategoriesRetrieve all Categories. GET /categories.json
Action
List CustomersRetrieve all Customers. GET /customers.json
Action
List ProductsRetrieve all Products in the store. GET /products.json (supports category/status filters and pagination).
Action
Update CustomerUpdates an existing customer in your Jumpseller store.
Action
Update ProductUpdates a Product
Action
Update Product by SKUUpdates a product given a SKU
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.