Integration
Connect Mailparser to Shippo
When something happens in Mailparser, your agent does the next thing in Shippo. 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 Shippo 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 Shippo
Triggers and actions 4 triggers · 18 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 OrderTriggers when a new order is created
Trigger
New Shipping LabelTriggers when a new shipping label is created
Action
Add addressCreate a new address record. Endpoint: POST /addresses.
Action
Add customs declarationCreate a new customs declaration for international shipments. Endpoint: POST /customs/declarations.
Action
Add customs itemCreate a new customs item line for use in a customs declaration. Endpoint: POST /customs/items.
Action
Add parcelCreate a new parcel record (dimensions/weight). Endpoint: POST /parcels.
Action
Add refundRequest a refund for a shipping label/transaction. Endpoint: POST /refunds.
Action
Add shipmentCreate a new shipment to generate rate quotes. Endpoint: POST /shipments.
Action
Add shipping labelPurchase/create a shipping label (transaction) from a rate. Endpoint: POST /transactions.
Action
Create OrderCreates an order.
Action
Find an OrderSearch for an order by ID.
Action
Find a Shipping LabelSearch for a shipping label by ID.
Action
Get addressRetrieve a single address by id. Endpoint: GET /addresses/{AddressId}.
Action
Get shipmentRetrieve a single shipment by id. Endpoint: GET /shipments/{ShipmentId}.
Action
Get tracking statusLook up the current tracking status for a shipment by carrier + tracking number. Endpoint: GET /tracks/{Carrier}/{TrackingNumber}.
Action
List addressesList all addresses. Endpoint: GET /addresses.
Action
List parcelsList all parcels. Endpoint: GET /parcels.
Action
List rates for shipmentRetrieve the available carrier rates for a shipment. Endpoint: GET /shipments/{ShipmentId}/rates.
Action
List shipmentsList all shipments. Endpoint: GET /shipments.
Action
Validate addressValidate an existing address by id. Endpoint: GET /addresses/{AddressId}/validate.
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