Connect Mailparser to Xitoring

Both apps 18Mailparser 2Xitoring 16

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

  Create a new uptime/website/server check. POST /api/v2/check

• Action
  Add group

  Store a new check/server group. POST /api/v2/groups

• Action
  Add heartbeat

  Create a new heartbeat check. POST /api/v2/heartbeat/add

• Action
  Add maintenance schedule

  Create a new maintenance window. POST /api/v2/maintenance-schedules/add

• Action
  Add ticket

  Create a new support ticket. POST /api/v2/tickets

• Action
  Delete check

  Delete a check. DELETE /api/v2/checks/{id}

• Action
  Delete server

  Remove a server from monitoring. DELETE /api/v2/servers/{id}

• Action
  Get check

  Retrieve a single check by id. GET /api/v2/check/{id}

• Action
  Get incident

  Get a single incident's data. GET /api/v2/incidents/{id}

• Action
  Get server

  Retrieve a single server by id. GET /api/v2/servers/{id}

• Action
  List checks

  List all checks. GET /api/v2/check/

• Action
  List groups

  List all groups. GET /api/v2/groups

• Action
  List maintenance schedules

  List maintenance schedules. GET /api/v2/maintenance-schedules

• Action
  List servers

  List all monitored servers. GET /api/v2/servers

• Action
  Resolve incident

  Resolve an open incident. POST /api/v2/incidents/{id}/resolve

• Action
  Update check

  Update an existing check. PUT /api/v2/check/{id}

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