Intelligent Document Processing - IDP by Workato
We are extremely excited to announce the latest in our slew of AI features, Intelligent Document Processing (IDP).
With the advent of our LLM connectors, it has become easy to use Gen AI to process unstructured data/text into a structured manner within our workflows. With native support for IDP, we aim to bridge this gap by allowing anyone to process receipts, invoices, or any document into datapills to map to any downstream actions.
With the advent of our LLM connectors, it has become easy to use Gen AI to process unstructured data/text into a structured manner within our workflows. With native support for IDP, we aim to bridge this gap by allowing anyone to process receipts, invoices, or any document into datapills to map to any downstream actions.
A brief overview of the capabilities of our solution:
- Pre-configured schemas for Invoices, Receipts
- Ability to configure free-form schemas and process any documents
- Ability to process handwritten text
- Ability to process multilingual documents
- Easy to setup and use → No fine tuning or sample documents required
- Auto mapping of recognised text from the documents
- AI understands the document and is able to easily map it to the fields the user requires
Use cases like Invoice and Receit processing, Medical certificate, Contracts, Purchase Orders, ID documents, Forms, Customer Onboardings, and many more, are now super easy to setup with Workato! Check this video for a quick demo.
Ask your CSM in case you are interested on it!
Native EDI Support
Electronic Data Interchange (EDI) is a broad set of standards and protocols for exchanging commercial documents in B2B space. While outdated compared to modern alternatives like RESTful APIs, it's still widely used in commercial trade and other applications.
We have released a first version of our EDI tools by Workato. It enables you to embed Workato in EDI workflows by generating and processing EDI documents.
EDI by Workato supports the following standards:
- EDIFACT
- HL7
- Generate EDI
- Parse EDI
EDI Tools by Workato is currently in Public Beta. Ask your CSM in case you are interested on it!
Platform Ops Update
We are happy to update you with some of the coolest releases in the OPS product area!
Improved assets search:
The new search enables users to find assets (recipes, connections, pages) by key words that appear in the following fields (in this hierarchy) :
- Names
- Description
- Apps used
- Actions used
The assets in the search result list will be ordered by relevance as default and the user can toggle between the order types. Also the user can apply our exiting filters to make the search more precise. Things like "I want to find all recipes that use "update record" action" or "find all recipes using "send email" to check the email we use in that address", etc, are now super easy! Check the documentation.
Deployments:
We have released several enhancements in the deployment flow lately. Today we have the last and most exciting of them all - "Deploying straight from the recipe page"!
When a user wants to deploy just one recipe out of a project, the flow sometimes is long (depending on the size of project and customisation step) from now on they can just click deploy from the recipe page, select the environment and the deployment is auto customised to this recipe only! (and its dependencies of course). Check the documentation.
When a user wants to deploy just one recipe out of a project, the flow sometimes is long (depending on the size of project and customisation step) from now on they can just click deploy from the recipe page, select the environment and the deployment is auto customised to this recipe only! (and its dependencies of course). Check the documentation.
Log Trigger Errors:
The last trigger error type is now automatically logged to the logging service - Webhook trigger errors!
As you may know, Logging service add on can use the logs to debug recipe trigger errors that up until now were invisible in the platform UI. The different trigger errors ( polling, webhook, condition) are automatically logged with the additional information (if exists) to help users debug and fix these type of errors. You can check the documentation.
As you may know, Logging service add on can use the logs to debug recipe trigger errors that up until now were invisible in the platform UI. The different trigger errors ( polling, webhook, condition) are automatically logged with the additional information (if exists) to help users debug and fix these type of errors. You can check the documentation.
Developer APIs:
New endpoints for users to update the recipe version comment via APIs!
In addition, users can now use our new GET APIs to get all recipe versions comments or a specific recipe version comment
- GET /api/recipes/:recipe_id/versions
- GET /api/recipes/:recipe_id/versions/:id
- POST /api/recipes/:recipe_id/versions/:id
Check the documentation.
