AWS Comprehend and Parsio Integration

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

Connect AWS Comprehend and Parsio to automate ai workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.

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

Learn about AWS Comprehend and Parsio

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

  • AWS Comprehend

    • AI
    • 50 searches
    • 36 actions

    Amazon natural language processing service for finding insights in text.[5]

  • Parsio

    • AI
    • 1 trigger
    • 11 searches
    • 17 actions

    Document parsing service that turns emails, PDFs and images into structured data.[6]

How to connect AWS Comprehend to Parsio

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

How does the integration between AWS Comprehend and Parsio work in WEXTL?

WEXTL exposes actions and triggers for AWS Comprehend and Parsio 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.

Parsio triggersAWS Comprehend actions

Parsio modules

  • Clone Templates Copies parsing templates into another mailbox. Use Target Mailbox to choose which mailbox receives the copies, so extraction rules built once serve a second mailbox.
  • Create a Mailbox Opens a new Parsio mailbox under a Name. Use Preset to choose the parser type, and ML Model to select the OCR or AI engine. Set Keep Raw Data to store the raw data of each document.
  • Create a Webhook Registers a URL that Parsio calls for the chosen Event in a mailbox. Pick a Table when the event is tied to one, and turn off Enabled to hold deliveries back.
  • Delete a Mailbox Deletes a Parsio mailbox you no longer need for incoming documents.
  • Delete Templates Removes several parsing templates in one request.
  • Delete Webhooks Clears out several webhooks in a single request.
  • Disable Templates Turns off parsing templates in bulk, so a whole set of extraction rules stops being enabled in one call.
  • Enable Templates Enables a set of parsing templates in bulk, listing each template ID under Templates.
  • Get a Document Fetches one parsed document by its Document ID, with its Status, Content Type and Processed At date.
  • Get a Mailbox Shows one mailbox with its Email Prefix, Preset and Process Attachments setting.
  • Get a Template Gets one parsing template with its Name, Enabled state and Created At. Use Mailbox to narrow the Template list to a single mailbox.
  • Get a Webhook Gets one webhook with its URL, Event and Enabled setting. Use Mailbox to shorten the Webhook list to one mailbox.
  • Get Parsed Data Pulls the extracted JSON of processed documents in a mailbox. Narrow it with From and To dates, and use Page to move through results and Limit to read fewer.
  • List Collected Emails Returns the addresses a mailbox has collected, each as Email and Name. Use Page to step through them and Limit to cap the total read.
  • List Documents Searches the documents inside a mailbox. Filter on Search text in the name, Statuses for the parsing outcome, and From and To for a date range.
  • List Mailboxes Retrieves every mailbox in the account, each with Name, Email Prefix and Preset. Use Limit to stop after a set number.
  • List Table Fields Shows the table fields defined for a mailbox, each with an ID and Name. Use Limit to read only part of the list.
  • List Templates Finds the parsing templates in a mailbox, with Name, Enabled flag and Created At. Page moves through longer lists.
  • List Webhooks Gathers the webhooks set up for a mailbox. Each carries a URL and Event. Use Limit to trim the output.
  • Make an API Call Runs a free-form request against the Parsio REST API using your saved credential.
  • Parse a Document Again Runs extraction again on a document already in Parsio. This may use parsing quota.
  • Parse a File (Wait for Result) Sends a File to a mailbox and waits until parsing is complete, then returns Status and Processed At for the finished document.
  • Parse Text or HTML (Wait for Result) Parses content in a mailbox and holds the step until parsing ends. The finished document arrives with its Status and Processed At. Send it as HTML or Text.
  • Send Text or HTML for Parsing Queues email-style content for extraction in a Parsio mailbox and returns the Doc ID before parsing finishes. Provide HTML or Text, with optional From, To and Name. Use Meta to attach a JSON object to the parsed data.
  • Skip Documents Marks documents of a mailbox as skipped, taking each document ID from Documents.
  • Update a Mailbox Edits mailbox settings such as Name, Email Prefix and Preset. Use Alert Frequency (Hours) for alert emails and Receive Email to toggle inbound mail.
  • Update a Webhook Changes the Name, URL or Event of a webhook, or turns delivery on or off with Enabled. Use Table when the new event applies to one table.
  • Upload a File for Parsing Uploads a file under a File Name into a mailbox, then returns the Doc ID before parsing finishes. Use Meta to add a JSON object to the parsed data.
  • Watch Events Fires the workflow instantly when Parsio posts a document event to its webhook. Each event brings the document Status and Content Type.

AWS Comprehend modules

  • Attach a Resource Policy to a Model Attaches a JSON Policy to a custom classifier or recognizer version so another AWS account can import it. Use Policy Revision ID when replacing an existing policy, so a concurrent change is not overwritten. Output is the new Policy Revision ID.
  • Batch Detect Dominant Language Finds the dominant language in each of 25 texts at most, in one request. A text needs 20 characters minimum and 5 KB maximum. Results keep the order you sent.
  • Batch Detect Entities Scans up to 25 texts written in the same Language for entities. Output includes the Result List, plus an Error List for texts that failed.
  • Batch Detect Key Phrases Pulls the key phrases out of several texts in one call, all sharing a single Language. Add up to 25 Texts of 5 KB each, then read Result List in the original order.
  • Batch Detect Sentiment Rates the sentiment of every text in a list sharing one Language, 25 texts at most. Check the Error List for texts that could not be scored.
  • Batch Detect Syntax Tags the words of several texts with their parts of speech. Syntax analysis covers English, Spanish, French, German, Italian and Portuguese, which are the choices for Language.
  • Batch Detect Targeted Sentiment Judges the sentiment toward each named entity inside up to 25 texts. Targeted sentiment currently supports English only, so the Language is always English.
  • Check Whether a Text Contains PII Entities Checks up to 100 KB of Text for personal information and reports which kinds appear as Labels. PII labeling supports English and Spanish, selected with Language.
  • Classify a Document Sends text or a document to a trained classifier Endpoint and returns the Classes or Labels it assigns. Use either Text or Document Bytes, and Document Reader Settings to control how PDF and image content is read.
  • Create a Dataset Adds a training or testing dataset to a flywheel. Use Dataset Name and Input Data to give the labeled files, and Dataset Type to say whether it trains or tests. You get the Dataset ARN.
  • Create a Document Classifier Starts a custom classifier on labeled Training Data, read through the Data Access Role ARN. Use Mode to allow one class or several labels per document. You receive the Document Classifier ARN.
  • Create a Flywheel Sets up a flywheel that keeps a model improving from new data. It stores datasets and statistics at the Data Lake S3 URI. Use Active Model ARN for an existing model, or Model Type and Task Settings for a new one.
  • Create an Endpoint Provisions capacity for a trained model. Use Inference Units to size it, at 100 characters per second each and billed while it runs, and Model ARN or Flywheel to say what it serves.
  • Create an Entity Recognizer Begins training a recognizer for your own entity types from Training Data, read with the Data Access Role ARN. Use Version Name to label this version. Output includes the Entity Recognizer ARN.
  • Delete a Document Classifier Deletes a custom classifier. Only classifiers in the Trained or In Error state qualify, and not while an endpoint uses them.
  • Delete a Flywheel Removes a flywheel. It cannot be deleted while an iteration is running or an endpoint relies on it.
  • Delete a Resource Policy Deletes the policy attached to a custom model version, found by its Model ARN. Use Policy Revision ID to delete only when the policy is still at that revision.
  • Delete an Endpoint Removes a model endpoint. A model can only be deleted after all of its endpoints are gone.
  • Delete an Entity Recognizer Deletes a custom recognizer that is Trained or In Error, provided no endpoint is serving it.
  • Describe a Dataset Looks up a single dataset of a flywheel and shows its Dataset Properties.
  • Describe a Document Classification Job Reports how an asynchronous classification job is progressing, as Job Properties.
  • Describe a Document Classifier Reads one custom classifier version and its training state from the Classifier Properties.
  • Describe a Dominant Language Detection Job Looks up a language detection job that is running or finished, giving back its Job Properties.
  • Describe a Flywheel Reads the configuration and status of a flywheel, summarized as Flywheel Properties.
  • Describe a Flywheel Iteration Fetches the Iteration Properties of one training iteration of a flywheel, found with Flywheel and Iteration.
  • Describe a Key Phrases Detection Job Pulls the Job Properties of a key phrase extraction job, whether it is still going or done.
  • Describe a PII Entities Detection Job Returns Job Properties for a personal information scan, covering its progress.
  • Describe a Resource Policy Reads the policy of a custom model version, found by its Model ARN. Output includes the Policy text and its Policy Revision ID.
  • Describe a Sentiment Detection Job Checks on a sentiment analysis job and fetches its Job Properties.
  • Describe a Targeted Sentiment Detection Job Checks on a job that scores sentiment toward named entities, giving its Job Properties.
  • Describe a Topics Detection Job Gets the Job Properties of a topic modeling job that is running or finished.
  • Describe an Endpoint Fetches the current state of a model endpoint, returned as Endpoint Properties.
  • Describe an Entities Detection Job Retrieves the Job Properties for an entity detection run, which tell you whether it has finished.
  • Describe an Entity Recognizer Returns the Recognizer Properties of one custom recognizer version.
  • Describe an Events Detection Job Shows where an events detection job stands, with the Job Properties of the run.
  • Detect Dominant Language Identifies the language of a text of at least 20 characters, up to 100 KB. Output lists each candidate under Languages.
  • Detect Entities Finds entities in a piece of Text or in a document sent as Document Bytes. Use Language with the built-in model, or Custom Endpoint to find your own entity types.
  • Detect Key Phrases Extracts the main phrases from a single text under 100 KB, written in the chosen Language. Output is a list of Key Phrases.
  • Detect PII Entities Locates personal information in up to 100 KB of Text, with Language limited to English or Spanish. Output is a list of Entities.
  • Detect Sentiment Scores one text of up to 5 KB, such as a message body, review or comment from an earlier step. Output includes the Sentiment and its Sentiment Score.
  • Detect Syntax Tags each word of a text with its part of speech, within a 5 KB limit. Supported languages are English, Spanish, French, German, Italian and Portuguese. Syntax Tokens list the words.
  • Detect Targeted Sentiment Judges sentiment toward each entity in one English text, such as a product review naming several items, with a 5 KB ceiling. Entities carry their own sentiment.
  • Detect Toxic Content Scores up to 10 Text Segments for toxicity, each up to 1 KB and 10 KB in all. Toxicity detection currently works for English only, and results follow the order sent.
  • Import a Model Brings a classifier or recognizer version from another account into yours, once that account has allowed it with a resource policy. Use Model Name and Version Name to label the copy, and Model KMS Key to encrypt it. Output is the Model ARN.
  • List Datasets Lists the datasets of your flywheels, each as its own result with a Dataset Name, Dataset Type and Number of Documents. Use Filter to limit by status, type or creation date, and Flywheel to see one flywheel only.
  • List Document Classification Jobs Shows the classification jobs you have run, naming the classifier or flywheel behind each. Use Filter on the Job Name, Job Status or submit time, one at a time.
  • List Document Classifier Summaries Gives one summary per classifier name instead of per version, showing the Number of Versions and the Latest Version Status. Use Limit to cap the results of a run.
  • List Document Classifiers Returns every trained or training classifier version with its Version Name, Language Code, Status and Mode. Filter by Classifier Name, Status or when it was submitted to find one.
  • List Dominant Language Detection Jobs Retrieves your language detection jobs. Use Filter on Job Name or Job Status to find a particular run, and Limit to return fewer results.
  • List Endpoints Lists model endpoints with their Status, Current Inference Units and Model ARN. Use Filter to show only those attached to one model, in one state, or created in a date range.

Explore alternative integrations

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

Automate AWS Comprehend and Parsio on WEXTL®

Claim your 3-day trial to build AWS Comprehend with Parsio integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting AWS Comprehend and Parsio.

How do I connect AWS Comprehend and Parsio?

Connect your AWS Comprehend and Parsio 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 AWS Comprehend and Parsio?

Example: when the "Watch Events" trigger in Parsio fires, WEXTL can "Attach a Resource Policy to a Model" in AWS Comprehend. AWS Comprehend has 86 actions (including Attach a Resource Policy to a Model, Batch Detect Dominant Language, and Batch Detect Entities). Parsio has 28 actions (including Clone Templates, Create a Mailbox, and Create a Webhook). Add filters and transforms between steps when you need them.[1]

Can AWS Comprehend trigger actions in Parsio, and Parsio in AWS Comprehend?

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 AWS Comprehend and Parsio?

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

Does AWS Comprehend integrate with Parsio in real time?

Yes. Trigger-based automations start the moment AWS Comprehend (or Parsio) 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 AWS Comprehend + Parsio 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 AWS Comprehend with Parsio?

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

References

List of sources used to gather information about the AWS Comprehend and Parsio integration.

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

How we write our apps documentation

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

Explore AWS Comprehend and Parsio, or get started