Connect Mailparser to Fibery

Both apps 12Mailparser 2Fibery 10

• 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
  Entity Updated (Or Created)

  Triggered when an entity in the chosen database is created or updated.

• Trigger
  New Entity

  Triggers when a new Entity (Task, Document, etc.) is created.

• Trigger
  New Type

  Triggers when a new type is created.

• Action
  Add comment

  Add a comment to an entity.

• Action
  Add Entity

  Creates a new Entity (Task, Document, etc.).

• Action
  Delete Entity

  Delete an entity by id.

• Action
  Find Entity

  Finds an Entity with matching field values.

• Action
  Get Document

  Returns the content of a Fibery rich-text document (e.g. a comment body or rich-text field) by its document secret.

• Action
  Get Entity

  Retrieve one entity by id with selected fields.

• Action
  Update Entity

  Updates existing Entity (Task, Document, etc.).

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