Skip to main content
All CollectionsExporting data
Send extracted data to Microsoft Power Automate (Flow)
Send extracted data to Microsoft Power Automate (Flow)

How to create flows to send parsed data to Microsoft applications in real time with Power Automate

Updated over 2 months ago

In this article, we will describe how to send data extracted by Parseur to Microsoft applications and others using Power Automate (formally known as Microsoft Flow).

What is Microsoft Power Automate?

Power Automate is a service that integrates cloud-based apps and services together so they interact with each other seamlessly. In particular, Power Automate makes it easy to send, process or receive data from Microsoft applications such as Outlook, Excel, SharePoint, Dynamics CRM, Dynamics NAV, SQL Server, Azure etc. It can also connect to hundreds of third party services like Twitter, Salesforce, Pipedrive, Gmail and many more

Use case example

For the purpose of this article we'll use a common use case: extract text from emails and create a new item in a SharePoint list.

Let's say we run a Movie Star Concierge Service. Movie stars can request services via a form online.

When a movie star hits the send button, we receive the request by email:

Our service is very successful and our support team is growing. We want to log all requests in a SharePoint list so that our team can pick them up.

In order to do that, we set up the following workflow: 

  • every time it receives an email, Parseur parses it and extracts the relevant text pieces.

  • then, parsed data is sent to Power Auomate which creates a new item in a connected SharePoint list.

Click on the picture above to see it in full screen.

Let's see how to set up this workflow.

Step 1: Set up your Parseur mailbox

This article assumes you already have created and configured your Parseur mailbox. Check out this page to get started if that is not the case.

Create a template to parse all incoming documents:

Step 2: Set up your Flow

Now connect to your Power Automate account (or create one if you don't have one already), Then go to My Flows > New > Create from blank

Then type "Parseur" in the search box and choose "New document processed" (or "Table processed" if you're dealing with table fields).

Then, Parseur will ask you to name your connection and enter the API Key:

  • Use anything you'd like for the connection name.

  • Your API Key is in your Parseur account (Click on "Account settings" on the left menu while on the home page).

Enter a connection name and your API Key:

Now, select the mailbox you want to use from the drop down list.

Then, click the New step and choose which application you want to send your Parseur data to. In this example, we'll choose SharePoint.

Enter the specifics of your application (for us, SharePoint address and list name) and create a data mapping between the fields sent by Parseur and the ones expected by your application.

That's it!

Step 3: Test your Flow

Now it is time to test that your Flow is set up properly. Click on the Test button at the upper right corner of the screen and choose "I'll perform the trigger action".

Back in Parseur, click the reprocess icon to send the parsed email data to Power Automate

If everything went correctly, you should now see a success message in Power Automate and your data in SharePoint!

Frequently Asked Questions (FAQ)

I get an Export Failed with ResponseSwaggerSchemaValidationFailure in the Logs. What should I do?

If you see an error message like:

The API operation ‘NewDocumentExpanded’ requires the property ‘Field_ABCD’ to be of type ‘String’ but is of type ‘Float’.

This usually indicates that the format of one of your fields has changed in Parseur. When you modify a field’s format, you need to update your flow and re-map the data fields. This allows Power Automate to recognize the new data structure and prevent validation errors.

Steps to resolve:

  1. Open your flow in Power Automate.

  2. Update the data mapping to reflect the new field formats.

  3. Save and test the flow to ensure the changes are applied correctly.

Did this answer your question?