Connect Mailparser to Cisco Webex Meetings

Both apps 8Mailparser 2Cisco Webex Meetings 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.

• Action
  Add meeting

  Schedules a new Webex meeting with a title, start and end time, and optional settings such as agenda, password, recurrence and invitees. Returns the created meeting, including its join link.

• Action
  Add meeting invitee

  Invites a person to a scheduled Webex meeting by email address, optionally as a cohost or panelist.

• Action
  Delete meeting

  Deletes a scheduled Webex meeting or meeting series, optionally emailing a cancellation to the host and invitees.

• Action
  Get meeting

  Returns the details of a Webex meeting by its ID.

• Action
  List meeting invitees

  Returns the people invited to a Webex meeting, with each invitee's email, display name and role.

• Action
  Update meeting

  Updates the title, agenda, password and start/end time of an existing Webex meeting and returns the updated meeting.

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