Connect Mailparser to BC Ferries

Both apps 4Mailparser 2BC Ferries 2

• 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
  List capacity route sailings

  returns all major (capacity-tracked) BC Ferries routes with their current sailings, each sailing's time/arrivalTime, sailingStatus (past/current/future), fill/carFill/oversizeFill percentages, vessel name, and vessel status. No auth, no path/query params.

• Action
  List non-capacity route sailings

  returns all minor (non-capacity-tracked) BC Ferries routes with their scheduled sailings, each sailing's time/arrivalTime, vessel name, and vessel status (no fill/capacity data since these routes don't report loading). No auth, no path/query params.

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