Connect Mailparser to Handwrytten

Both apps 10Mailparser 2Handwrytten 8

• 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
  Address List

  Triggers when Recipient Addresses are needed.

• Action
  Add Order to Basket

  Adds an order to a basket. If sending multiple cards at once, use this for each order, then check-out with Send Basket

• Action
  Create Contact

  Creates a new address book entry for the Handwrytten address book. (Note: other zaps don't really use the address book, but the rest of Handwrytten does.).

• Action
  Create Custom Card

  Creates a new custom 5x7 card with full bleed cover, using specified images, fonts, and logos.

• Action
  Empty Basket

  Clears your basket.

• Action
  Find Contact

  Finds a contact in your address book.

• Action
  Update Contact

  Updates an entry in the Handwrytten address book.

• Action
  Upload Custom Image

  Adds an image to Handwrytten for use in custom card designs.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.