Parseur and Plaud Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Keep Parseur and Plaud matched by integrating their events and actions. When ai events happen in Parseur, update the Plaud automatically - without any line of code in visual workflow builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Parseur and Plaud

Detailed info you need to know about Parseur and Plaud integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Parseur

    • AI
    • 2 triggers
    • 10 searches
    • 16 actions

    Document processing that extracts data from emails and PDFs.[5]

  • Plaud

    • AI
    • 2 searches
    • 7 actions

    Developer API for linking Plaud recorders to your app, uploading audio, and transcribing it.[6]

How to connect Parseur to Plaud

Set up your Parseur and Plaud integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Parseur and Plaud work in WEXTL?

WEXTL exposes actions and triggers for Parseur and Plaud that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Parseur triggersPlaud actions

Parseur modules

  • Copy a Document to a Mailbox Duplicates a document so the Target Mailbox gets its own copy. Read the Document ID off List Documents.
  • Copy a Mailbox Makes a duplicate of an existing Parseur mailbox.
  • Copy a Template Copies a template to another mailbox. Use the Template ID shown by List Templates, and send the copy to the Target Mailbox.
  • Create a Custom Download Defines a named download for a mailbox that covers either the whole mailbox or one table field. Use Fields to choose what a Mailbox download contains, and Table Field for a Table Field download.
  • Create a Mailbox Creates a Parseur mailbox. Start from a ready-made Mailbox Type, choose an AI Engine, and use Retention Days to set how long Parseur holds documents. Skip Name and Parseur picks one.
  • Delete a Custom Download Removes a mailbox custom download. Parseur refuses when the download is still in use.
  • Delete a Document Deletes a document from Parseur. This cannot be undone.
  • Delete a Mailbox Deletes the selected mailbox from Parseur, and it cannot be recovered afterwards.
  • Delete a Template Removes one template from a mailbox. This cannot be undone.
  • Get a Document Fetches one document by Document ID, which Watch Documents also provides. The result shows the File Name, Status and Template ID. A hex ID from an upload may not be accepted.
  • Get a Mailbox Shows one mailbox with its AI Engine, Document Count and Documents Per Status.
  • Get a Mailbox Schema Lists the fields that a mailbox extracts, as Type and Fields.
  • Get a Template Looks up a template by the Template ID that List Templates shows, giving its Name, Engine, Status and Document Count.
  • Get the Bootstrap Config Reads the general settings of Parseur, including the Choices and Mappings it accepts, the Maximum Field Lengths and the Email Domain.
  • Get the Document Logs Reads the log entries of one document, with the Created time, Code and Template Name of each. Use Search to keep entries matching a text, and Limit for the number to read.
  • List Custom Downloads Lists mailbox custom downloads by Name and Type, plus the links to each CSV and XLS file. Use Limit to set how many are returned.
  • List Documents Lists documents in a mailbox by Status, Received After or Received Before. Use Search to match part of a document name, and Include Extracted Data to add the parsed data. Parseur serves them 100 at a time.
  • List Mailboxes Retrieves the mailboxes in your Parseur account. Use Search for a name, and Sort By to order by Document count or Template count.
  • List Templates Shows the templates in a mailbox with Template ID, Name, Engine, Status and Last Activity. Pick a Limit to restrict the list.
  • Make an API Call Calls the Parseur REST API directly with a free-form request under your saved credential.
  • Reprocess a Document Runs a document through Parseur again. Its webhooks are sent again with the same document ID.
  • Skip a Document Marks a document as skipped and returns the updated document.
  • Update a Custom Download Edits a custom download on a mailbox. Use Name to rename it, Fields and Type to change what it covers, and Clear Fields to empty values when moving from Table Field to Mailbox.
  • Update a Mailbox Edits a mailbox through its Name, AI Engine, Retention Days or Sender Allow List Mode, and others. Use Clear Fields to empty a setting, since a blank field leaves it unchanged. Mailbox fields cannot be changed here.
  • Upload a Document Submits a File and its File Name to a mailbox. Parseur processes the file after this call returns, and Custom Values attach extra data to the extracted result.
  • Upload an Email or Text Submits email content or plain text to a mailbox through its Mailbox Address, with a Subject and From. Use HTML Body or Plain Text Body for the content, and note the HTML Body takes priority when both are filled.
  • Watch Documents Checks a mailbox on a schedule for documents with the Status you watch, such as Processed or Process failed. Use Limit to cap how many the first check returns.
  • Watch Events (Instant) Receives Parseur webhook events as they happen, each with its Document ID and Sender Name.

Plaud modules

  • Bind a Device Binds a Plaud device to a user. Serial numbers that start with 881 are Note Pro and 882 are Note Pin S. Output includes whether the device Is Bound.
  • Complete an Upload Finishes a multipart audio upload using the File ID and Upload ID from Create an Upload URL. List each uploaded part with its Part Number and ETag. Use File MD5 to have Plaud check the whole file. Output includes the Download URL.
  • Create a Transcription Starts a transcription of an M4A, MP3 or WAV file at a public Audio Link. Turn on Identify Speakers to label who is speaking and add Hotwords for names or product terms. Output includes the Transcription ID to read the result later.
  • Create a User Token Issues an access token for a person in your system, identified by your own User ID. Use Expires In to set the token lifetime in seconds, such as 86400 for one day. Output includes the Access Token.
  • Create an Upload URL Prepares a multipart audio upload for a user. Plaud returns one upload link per 5 MB part. Output also includes the File ID and Upload ID to finish the upload with.
  • Get a Device Binding Checks whether a Plaud device is bound to a user. Output includes the Bind History.
  • Get a Transcription Reads a transcription by the Transcription ID you got when it was created. Output includes the Status and the transcript Data. Plaud keeps transcriptions for 7 days by default.
  • Make an API Call Runs a free-form request against the Plaud REST API using your saved credential.
  • Remove a Device Binding Unbinds a Plaud device from a user in the registry of Plaud only. Your mobile app should also unpair the device over Bluetooth. The result reports the Is Bound state.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Parseur and Plaud integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Parseur and Plaud on WEXTL®

Claim your 3-day trial to build Parseur with Plaud integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Parseur and Plaud.

How do I connect Parseur and Plaud?

Connect your Parseur and Plaud accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Parseur and Plaud?

Example: when the "Watch Documents" trigger in Parseur fires, WEXTL can "Bind a Device" in Plaud. Parseur has 2 triggers (including Watch Documents and Watch Events (Instant)). Plaud has 9 actions (including Bind a Device, Complete an Upload, and Create a Transcription). Add filters and transforms between steps when you need them.[1]

Can Parseur trigger actions in Plaud, and Plaud in Parseur?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Parseur and Plaud?

No. Parseur-to-Plaud automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Parseur integrate with Plaud in real time?

Yes. Trigger-based automations start the moment Parseur (or Plaud) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Parseur + Plaud integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Parseur with Plaud?

You can build your Parseur + Plaud automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Parseur and Plaud integration.

  1. Parseur and Plaud integration source code, module specs and credentials implementation.
  2. Our Parseur and Plaud integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Parseur and Plaud, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Parseur integration information
  6. Plaud integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Parseur and Plaud integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Parseur and Plaud, or get started