Connect Mailparser to Wizard World

Both apps 13Mailparser 2Wizard World 11

• 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 Feedback

  Submit user feedback about the Wizard World API.

• Action
  Get Elixir

  Retrieve a single elixir by its id.

• Action
  Get House

  Retrieve a single Hogwarts house by its id.

• Action
  Get Ingredient

  Retrieve a single ingredient by its id.

• Action
  Get Spell

  Retrieve a single spell by its id.

• Action
  Get Wizard

  Retrieve a single wizard by its id.

• Action
  List Elixirs

  List all elixirs in the Wizard World catalog, optionally filtered by name/difficulty/ingredient.

• Action
  List Houses

  List all Hogwarts houses with their traits, heads, and founders.

• Action
  List Ingredients

  List all potion/spell ingredients, optionally filtered by name.

• Action
  List Spells

  List spells, optionally filtered by name, type or incantation.

• Action
  List Wizards

  List all wizards with their first/last names and elixirs invented, optionally filtered by name.

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