Microsoft Flow


Microsoft Flow allows you to connect your OneBlink form with hundreds of different pre-built systems and activities.


You can implement multi-stage workflows where different logic or integrations are applied, depending on your form data. For example, you may want to pass some of your form data to Sharepoint or Salesforce, or save data to your database, or even send image data to Azure Blob store.


Microsoft Flow also offers the ability to add approvals into your submission flow.


To get started, simply select the OneBlink connector from within MS Flow, and get creating! Or if you’d like a little more detail, we’ll dig deeper below.


Getting Started


To use the OneBlink connector, you’ll need a premium Microsoft Flow account - you may find you already have a licence with your Office 365 account, or if not you can sign up for a trial or paid account from their site:


https://flow.microsoft.com/


Once you have your account, you’ll be able to find the OneBlink connector in the MS Flow connector list.


To use the connector, you’ll need your API key from the OneBlink Console.



Getting Your API Key

Your API Key is available from within your OneBlink Console:


https://console.oneblink.io/


In the Advanced section, select Developer Keys. This page shows you all the API keys you have available to you.


If you don’t yet have a Forms API key, simply add a new one by selecting the Plus button in the bottom right of the screen. When creating a new key, give it a name that makes sense to you, and then select the Forms privilege.


You should now see a card with your Forms API keys listed including your Microsoft Flow API Key. You’ll need this when you first set up your OneBlink connector in Flow.





Creating a OneBlink Flow

If you haven’t used Microsoft Flow before, the best place to get started is to login to your Flow account, and select Learn from the side menu. Microsoft have create a lot of great tutorials from beginners to advanced.


Once you’re familiar with MS Flow, there are a couple of pointers below that will help you get up and running as quickly as possible:


Create a trigger

Select the trigger that runs when a form is submitted "Triggers when a OneBlink Form submission occurs". This is the trigger that will start your flow.


The first time you select the OneBlink connector you’ll be asked to enter the name of your connection (this can be anything), as well as enter the API Key from the OneBlink Console.


Add an Action

The trigger doesn’t contain all of your form data. To get the data your user has submitted, you can use the “Retrieve OneBlink Form Submission Data” action.


Note. There are dynamic values for both Form ID and Submission ID available to you.


This action will bring back an object containing both the form definition and the submission data, allowing you to build out your flow from there.



Next Steps

The next stage of the flow is completely up to you, however in most cases you will probably want to use the Parse JSON connector to take your data and turn them into dynamic values you can use in further flows.


In order to parse the JSON value you will need access to the form JSON Schema. 


The easiest way to get the JSON schema is to navigate to the forms menu and select the side menu of the form. This will give you the option to "View Schema".


From here you can copy the schema to your clipboard and paste it in the Parse JSON MS flow connector. See below: 


The Content for the Parse JSON connector will need to be 'Submission Data'.



Approvals

Microsoft have released an Approvals connector that will allow you to add an approval step to your submission.


This means when a user submits a form, an approval must happen before your flow completes.


Approvals can be handled both via email, as well as via the MS Flow app, depending on what best suits your needs.


This is a feature offered directly from Microsoft, and may solve a lot of your approval needs without having to use a more complex workflow solution.