Connect Mailparser to Granola

Both apps 8Mailparser 2Granola 6

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

  Triggers when a new note is created in Granola, optionally limited to one folder or space.

• Action
  Get note

  Returns a single Granola meeting note with its title, owner, attendees, calendar event, folders, summary and, optionally, its transcript.

• Action
  Get transcript

  Returns the full meeting transcript of a Granola note, one item per spoken segment with speaker, text and start/end times. Works even for very long transcripts that Get note cannot include.

• Action
  List folders

  Returns every folder in the Granola workspace, with each folder's name, parent folder and space.

• Action
  List notes

  Returns the Granola meeting notes you have access to, optionally limited to a folder or space or to a created/updated date range.

• Action
  List spaces

  Returns all the spaces in your Granola workspace, with each space's id and name.

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