For some time now, customers and partners have been asking me how they can use Scribe Online with Microsoft Flow and Logic Apps for their enterprise integration needs.
Flow is a great tool for power users who want to build data workflows without IT help. Logic Apps comes in for more complex problems, but it usually requires IT involvement. Scribe Online empowers citizen integrators to build powerful integrations without writing code or setting up Microsoft Azure. Wouldn’t it be great if users could marry the power of Scribe Online with the simplicity of Flow? Well, now you can.
Scribe’s most recent update to our platform now includes an OpenAPI Specification (OAS), a universally accepted set of guidelines to describe REST APIs. This allows you to publish an API for a Scribe Online map that you can call as a step in Flow.
So what is OAS?
• OpenAPI Specification (OAS) is a universally accepted set of guidelines to describe REST APIs
• Previously known as Swagger Specification
• Basically, a blueprint working with a REST API
• Contains items such as:
• Host and Paths (Endpoints)
• HTTP Verbs (Operations)
• Request schema
• Response schema
What can you do with it?
• Import into 3rd party tool like Azure Logic Apps and Flow
• Verify structure of Requests and Responses
• Generate a Server or Client using Swagger Editor
How does it work in Scribe?
• 3 New APIs to retrieve OAS for a single Request Reply map, a whole solution, or an entire Org
• Returned in JSON
• OAS Version 2.0 supported
• Designed to work with any Request Reply map
• Existing maps require a apply\save
Here is a simple use case in which a user has created a workflow project that is designed to run when a new record is added to a Dynamics 365 Sales custom form. When the record is saved, it would trigger an email notification.
Now we want to include this data from our Flow project to be integrated into a MariaDB database table targeted for executive reporting. But the MariaDB endpoint we want the Flow project to push data to is not supported by existing connections in Flow.
Flow can’t connect with MariaDB, but Scribe can so I took advantage of Scribes OAS and built a custom Flow connector to pass data to Scribe that would trigger the integration map linking our Flow project with our Scribe enterprise integrations.
Now here is how you can use both Azure Logic Apps and Flow in concert with Scribe Request-Reply Event maps enabled by the latest OAS specification update.
From Scribe Online:
• Create an Event based solution
• Create a Request Reply map in the solution
• In your Request Block add the Request Criteria
• From the MariaDB connection build your conditional map logic to look for existing records so you can create new records and update existing ones
• Create a Flow project with a Dynamics CRM Trigger for when a new Record is entered on your Contact entity.
• Then create a custom connector from the Open API endpoint URL with the addition of “api-doc” to the URL.
• (This connection will take the values entered into the CRM from CRM Flow object to your connector which will then make a JSON call to Scribe Online to trigger the Request Reply map to execute the integration based on the request criteria that was passed.)
• Then add your Outlook 365 Send an Email to alert you once the integration has completed.
This entire use case took at total of 10 minutes to put together showing how with the power and flexibility of the Scribe platform tacking advantage of the OpenAPI updates that you can easily link your Flow project with Scribe so that can work with your Enterprise Integration strategy.
If you are interest in seeing a detailed how I built my Solution please go to my KB article and if you want to learn more about Scribe please go to Scribesoft.com.
Share your experiences with us:
How did it work out? Share your thoughts on this how – to blog with us in our success community here. Not a member yet? Easily set up your account here.