Markup AI and Parseur Integration

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

Keep Markup AI and Parseur matched by integrating their events and actions. When ai events happen in Markup AI, update the Parseur 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 Markup AI and Parseur

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

  • Markup AI

    • AI
    • 1 trigger
    • 42 searches
    • 42 actions

    Content checks that keep writing on brand, on style and on terminology.[5]

  • Parseur

    • AI
    • 2 triggers
    • 10 searches
    • 16 actions

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

How to connect Markup AI to Parseur

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

How does the integration between Markup AI and Parseur work in WEXTL?

WEXTL exposes actions and triggers for Markup AI and Parseur 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.

Markup AI triggersParseur actions

Markup AI modules

  • Watch New Agent Runs Checks for agent runs at a set interval and runs once per new run. Use Limit to set how many of the newest runs from the last day the first check takes.
  • Add a Term Comment Comments on a terminology term. The result is the new history event with its type, text, user and date.
  • Add Files to a Style Check Batch Uploads up to 20 documents into a style check batch that already exists. Use Items to attach metadata for each file and Defaults to set per-batch style guide settings.
  • Add Items to a Style Check Batch Appends up to 20 text documents per call to a batch that already exists. Pass Defaults to apply settings such as the style guide to the batch.
  • Cancel an Agent Run Stops a running agent workflow and reports the Cancelled At time.
  • Contribute a Terminology Term Proposes a new term for the terminology in a given language and under chosen categories. Add a Comment or Custom Field Values to explain the suggestion.
  • Create a Brand Domain Adds a brand domain that groups term sets, with an optional Description. The result includes its Term Set Count.
  • Create a Brand Term Adds a Term of a chosen Type to a brand term set. Turn on Case Sensitive to match capitalization exactly.
  • Create a Brand Term Set Creates a term set from a Context that decides when its terms are flagged and what the replacement should be. Add starter Terms, a Term Type and a Context Polarity here.
  • Create a Style Check Batch Starts a batch of up to 20 documents for style checking. Set Webhook URL to get notified when the batch ends.
  • Create a Style Check Batch from Files Starts a style check batch from up to 20 uploaded Files. Use Items to add metadata for each file in order, and Webhook URL to get a notice when the batch ends.
  • Create a Terminology Category Adds a category of a given Category Type under a unique Name. Use Parent Category ID to nest it and Priority to set its sort position among siblings.
  • Create a Terminology Category Type Defines a type of category with a unique Name and a Display Name. Turn on Hierarchical to allow nesting, or Closed to block new top-level categories.
  • Create a Terminology Custom Field Defines a custom field for terminology records, with a Name, a Display Name and a Type. Turn on Multiline or Nullable to adjust the kind of value it takes.
  • Create a Terminology Term Adds a term to the terminology with its surface text in one language and a status. Give a Masterterm ID to attach it as a variant of an existing head term.
  • Create or Replace Terminology Entries Loads up to 500 entries from an ACTIF 1.0 document, creating new ones and replacing any that already exist.
  • Delete a Brand Domain Deletes a brand domain and confirms with its ID and a Deleted flag.
  • Delete a Brand Term Removes one brand term out of the term set it belongs to. A Deleted flag in the result confirms it.
  • Delete a Brand Term Set Deletes a whole brand term set and returns the ID of the set that was removed.
  • Delete a Terminology Category Deletes a category from the glossary and reports a Deleted flag.
  • Delete a Terminology Category Type Removes a category type. Built-in system types cannot be deleted.
  • Delete a Terminology Custom Field Removes a custom field definition. The result is the field ID plus a Deleted flag.
  • Delete a Terminology Term Deletes a single term and returns a Deleted flag with its ID.
  • Delete Terminology Entries Removes several terminology entries together, matched on their Entry IDs.
  • Download a Term Image Downloads an image stored with a term as a file, along with its File Name, Size (Bytes) and Content Type.
  • Export Brand Terms as ACTIF Downloads every brand term as an ACTIF file and returns its File Name.
  • Export Brand Terms as CSV Saves every brand term as a CSV file that opens in a spreadsheet. The Content Type of the file is returned as well.
  • Export the Terminology as ACTIF Produces the complete terminology as an ACTIF file and tells you the File Name it was given.
  • Export the Terminology as an XML Dump Generates an XML dump of the terminology that Import the Terminology XML Dump can load again. The Size (Bytes) of the dump is returned too.
  • Get a Brand Domain Reads one brand domain with its Name, Description and Term Set Count, plus who created and last updated it.
  • Get a Brand Term Fetches one term from a brand term set, showing its Type and whether it is Case Sensitive.
  • Get a Brand Term Set Looks up a term set with its Context, Term Type and Context Polarity. The Terms and Domains it holds come with it.
  • Get a Brand Voice Profile Pulls the definition of one brand voice profile, with its Identity, Bright Lines, Fingerprints and Exemplars.
  • Get a Persona Returns one reader persona with its Title, Seniority, Industry and Technical Level.
  • Get a Style Check Batch Shows a batch with its Status, Sealed state and Counts. Use Item Limit and Item Offset to page through the Items of a big batch.
  • Get a Style Check Result Gets the Result of a style check run with its Status and Check Type, to act on the findings.
  • Get a Style Guide Returns a style guide with its Language, Language Variant and Goals, and whether it is Enabled.
  • Get a Term History Lists the events recorded for a term, such as comments. Use Event Type to keep only some kinds of event.
  • Get a Terminology Concept Finds the concept a term belongs to and lists all Terms that share it.
  • Get a Terminology Job Tracks a terminology job from its Job ID, showing its Status, Stage, Term Count and any Error.
  • Get a Terminology Term Reads a single term with its Surface, Language, Status and Categories.
  • Get an Agent Fetches an agent along with its Description, Input Schema, Output Schema and Cadence. Check the Input Schema before calling Run an Agent.
  • Get an Agent Run Pulls one agent run showing its Status, Result and Check Type, and when it started and finished.
  • Get Terminology Entries Fetches up to 100 entries by Entry IDs and returns them as ACTIF XML.
  • Get the Current Terminology Job Checks whether a terminology job is running right now. The result has an Active flag and the Job itself.
  • Get the Style Agent Settings Reads the Style Agent configuration of your organization, including Style Agent Numeric Scoring and Allow User Tracking.
  • Get the Terminology Publish State Shows whether the terminology has drifted from what was last published, with the Last Published At, Last Changed At and Active Job.
  • Get the Terminology Schema Retrieves the schema that describes how the terminology is structured, delivered as ACTIF XML.
  • Get the Variant Rules Returns the Rules that control how term variants are generated.
  • Import Brand Terms Loads brand terms from a CSV or ACTIF XML File. Turn on Delete Existing Terms to wipe the current brand terms first, and the result counts the Term Sets Created.

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.

Explore alternative integrations

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

Automate Markup AI and Parseur on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Markup AI and Parseur.

How do I connect Markup AI and Parseur?

Connect your Markup AI and Parseur 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 Markup AI and Parseur?

Example: when the "Watch New Agent Runs" trigger in Markup AI fires, WEXTL can "Copy a Document to a Mailbox" in Parseur. Markup AI has 1 trigger (including Watch New Agent Runs). Parseur has 26 actions (including Copy a Document to a Mailbox, Copy a Mailbox, and Copy a Template). Add filters and transforms between steps when you need them.[1]

Can Markup AI trigger actions in Parseur, and Parseur in Markup AI?

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 Markup AI and Parseur?

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

Does Markup AI integrate with Parseur in real time?

Yes. Trigger-based automations start the moment Markup AI (or Parseur) 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 Markup AI + Parseur 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 Markup AI with Parseur?

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

References

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

  1. Markup AI and Parseur integration source code, module specs and credentials implementation.
  2. Our Markup AI and Parseur integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Markup AI and Parseur, 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. Markup AI integration information
  6. Parseur integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

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

Explore Markup AI and Parseur, or get started