Connect Mailparser to Orshot

Both apps 8Mailparser 2Orshot 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 brand image

  Uploads an image to your Orshot workspace's brand assets from a URL or base64 data.

• Action
  Get render job

  Get one async render job by its ID, including its status and, once finished, its result or error.

• Action
  List brand images

  Lists the brand images in your Orshot workspace, optionally filtered by tags or scoped to one embed user.

• Action
  List render jobs

  Returns all async render jobs in the workspace, newest first, optionally filtered by status.

• Action
  Render From Template

  Renders an image or PDF from an Orshot utility (library) template such as Website Screenshot or Tweet Image.

• Action
  Start async render

  Starts rendering a Studio template in the background (image, PDF or video) and returns a render job immediately. Collect the finished file by checking the job or via a webhook.

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