Connect Mailparser to ilert

Both apps 15Mailparser 2ilert 13

• 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 or Updated Incident

  Triggers when an incident (alert) on the chosen ilert alert source is created or changes: assigned, escalated, accepted, raised, commented on, resolved, or a responder is added or removed.

• Action
  Accept Incident

  Accepts a pending ilert alert (formerly called an incident) on behalf of the connected user, stopping its escalation, and returns the updated alert.

• Action
  Add Alert

  Creates an alert in ilert on the chosen alert source, which then escalates according to the source's escalation policy (or a policy or responders you specify).

• Action
  Add maintenance window

  Creates a maintenance window in ilert that suppresses alerts for the chosen alert sources and services between a start and end time.

• Action
  Create Incident

  Creates a new incident in ilert, optionally marking affected services and adding responders. Depending on the affected services, subscribers may be notified.

• Action
  Find User on Call

  Finds the user currently on call for an on-call schedule, along with the start and end of their current shift. Returns found=false when nobody is on call.

• Action
  Get alert

  Returns a single ilert alert by its id, including its summary, status, priority, alert source, escalation policy and responders.

• Action
  Get incident

  Returns a single ilert incident by its id, including its status, severity, affected services and responders.

• Action
  Get maintenance window

  Fetches a maintenance window by ID. An error occurs if the maintenance window is not found.

• Action
  List Alert Sources

  Returns all alert sources in your ilert account, including each source's integration type, integration key, status and escalation policy.

• Action
  List incidents

  Returns the incidents in your ilert account, optionally filtered by status, affected service, severity and declaration date.

• Action
  List users

  Returns the users in your ilert account, with their name, email, role and contact settings.

• Action
  Resolve Incident

  Resolves an ilert alert (formerly called an incident), closing it and stopping further escalation.

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