Connect Mailparser to AFrame

Both apps 22Mailparser 2AFrame 20

• 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 contact note

  Adds a note to an existing contact in AFrame and returns the created note.

• Action
  Add event

  Creates a new event (date or appointment) on an AFrame transaction, with a fixed date or a date calculated from another transaction date.

• Action
  Add task

  Creates a new Task in AFrame, assigned to a team member and optionally linked to a transaction or contact.

• Action
  Add transaction attachment

  Creates a new attachment entry (a file placeholder or a web link) on an AFrame transaction.

• Action
  Add transaction note

  Adds a note (or showing / price-change activity) to an existing AFrame transaction.

• Action
  Add transaction participant

  Adds a participant to an AFrame transaction in a given role, either linking an existing contact, creating a new contact inline, or holding the role as a placeholder.

• Action
  Create Contact

  Creates a new Contact in your AFrame team, with name, company, emails, phones, addresses and categories.

• Action
  Create Transaction

  Creates a new Transaction in AFrame for a property address, with optional prices, key dates, assigned team members and custom field values.

• Action
  Find contacts

  Searches AFrame contacts by name, company, team, email, categories, or created/edited date range and returns the matching contacts (up to 100).

• Action
  Find tasks

  Returns tasks matching the given status, due/completion dates, transaction, contact or assignee filters (up to 100).

• Action
  Find team members

  Finds team members in your AFrame team by name, email, role, type or active status.

• Action
  Find transactions

  Searches transactions by ID, stage, property address, or created/edited date range and returns the matching transactions (up to 100).

• Action
  Get contact

  Returns a contact's details, including name, emails, phones, addresses, owners and categories.

• Action
  Get contact note

  Returns a single contact note by its ID, including its content, type, date and any attached file details.

• Action
  Get Event

  Returns one event (a date or appointment such as a closing date) on a transaction.

• Action
  Get transaction

  Returns a single AFrame transaction by its ID, including its status, property details, participants and custom field values.

• Action
  Get Transaction Note

  Returns a transaction note by its ID, including its content, activity date, contact details and visibility settings.

• Action
  Update contact

  Updates an existing AFrame contact, changing only the fields you fill in.

• Action
  Update task

  Updates an existing AFrame task, changing only the fields you fill in, and returns the updated task.

• Action
  Update transaction

  Updates an existing AFrame transaction's property address, status, assigned team members, prices, dates and commission. Only the fields you fill in are changed.

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