Connect Mailparser to Dwolla

Both apps 21Mailparser 2Dwolla 19

• 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 beneficial owner

  Adds a beneficial owner (an individual owning 25% or more) to a verified business customer, identified by SSN for US owners or by passport for non-US owners.

• Action
  Add customer

  Creates a Dwolla customer — receive-only, unverified, verified personal, or verified business.

• Action
  Add document

  Uploads an identity verification document (passport, license, ID card) for a Dwolla customer.

• Action
  Add funding source

  Creates a bank account, virtual account number or debit card funding source for a Dwolla customer.

• Action
  Add mass payment

  Creates a mass payment that sends up to 5,000 individual payments from one Dwolla funding source in a single batch.

• Action
  Add transfer

  Initiates a Dwolla transfer of money from one funding source to another, returning the new transfer's id and link.

• Action
  Cancel transfer

  Cancels a pending Dwolla transfer and returns the updated transfer.

• Action
  Delete funding source

  Removes a bank or debit card funding source in Dwolla. The funding source is soft deleted and stays readable, marked as removed.

• Action
  Find customers

  Searches Dwolla customers by name, business name or email, optionally filtered by verification status.

• Action
  Get customer

  Returns a Dwolla customer's details, including name, email, type and verification status.

• Action
  Get funding source

  Returns a Dwolla funding source (bank account or balance) by its ID, including its type, status and bank details.

• Action
  Get funding source balance

  Returns the current balance of a Dwolla funding source — balance and total for a Dwolla balance, available and closing for a bank account, available for a settlement account.

• Action
  Get mass payment

  Returns a Dwolla mass payment by its ID, including its processing status (pending, processing or complete), creation date, totals and metadata.

• Action
  List beneficial owners

  Returns all beneficial owners associated with a business verified Dwolla customer.

• Action
  List documents

  Returns all identity verification documents submitted for a Dwolla customer, including their type, review status and verification result.

• Action
  List events

  Returns the recent events (state changes to customers, transfers, funding sources and more) in your Dwolla application, newest first.

• Action
  List funding sources

  Returns all funding sources for a Dwolla customer, including bank accounts, debit cards and the Dwolla balance, with their verification status.

• Action
  List transfers

  Returns the transfers for a Dwolla customer, optionally filtered by amount range, date range, status, correlation ID or a name/email search.

• Action
  Update customer

  Updates a Dwolla customer's information, upgrades or retries verification, or suspends, deactivates or reactivates the customer.

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