Integration: Microsoft Flow

[Steve Giller]

Are there any plans in the pipeline to connect the iBridge to Microsoft Flow?

Some of the other departments are looking into using this and a direct integration would be more efficient than triggering their Flows with an email.

[TrevorKillick]

@DeadMeatGF

No current plans, but had a quick look shouldn't be too difficult to integrate with, it looks possible to use the integration node, Utilities -> Experimental -> HTTP Request to trigger a http Post to  Microsoft Flow endpoint and pass in the required data. 

https://flow.microsoft.com/en-us/blog/call-flow-restapi/

Kind Regards

Trevor Killick 

[Steve Giller]

This is probably just me not understanding proper usage, but whether I use HTTP Request or HTTP Request - Basic Auth I just get the Flow returning a 401:unauthorised.

[TrevorKillick]

@DeadMeatGF

Have you got Content Type set to application/json ?

You should only need to use HTTP Request as MS Flow doesn't support basic Auth they apparently attach and auth token to the URL that is exposed, also make sure the method is set to POST.



Kind Regards

Trevor Killick

[Steve Giller]

They're the settings I have - it's my first Flow, though, so I'll check I've not made mistakes at either (or both) ends.

 

[Steve Giller]

OK, so the Flow is working in Postman, but I'm still getting the same "unauthorised" return from Service Manager.

Any suggestions? I'm still assuming I'm doing something wrong somewhere

 

P.S. There's a typo in the node: Status Cose instead of Status Code.

[TrevorKillick]

@DeadMeatGF

I am looking into this now the error thats returned is this:

"data": {
  "error": {
    "code": "DirectApiAuthorizationRequired",
    "message": "The request must be authenticated only by Shared Access scheme."
  }
}

I am still trying to work out the different between a request in PostMaster and one form the iBridge. 

Kind Regards

Trevor Killick

[TrevorKillick]

@DeadMeatGF

Just to keep you updated i found the issue was the iBridge HTTP Request implementation is always trying to set HTTP Basic auth even if you do not want that, a fix is coming but i can't give any dates as yet. As soon as i know when the iBridge fix is going out i will let you know.

I will create a Integration method for Microsoft Flow to handle the error and success responses which should be more user friendly in the short term. 

In the long term it looks like we might want to directly integrate with MS Flow in the same way we have direct integration with MS Orchestrator, but thats not going to be in the next 90 days.

Kind Regards

Trevor Killick

[Steve Giller]

Thanks @TrevorKillick, excellent news.

 

[Steve Giller]

Using the new Node I was getting this error:

When I  realised I had "continue on error" turned on and toggled it to off I got:

[TrevorKillick]

@DeadMeatGF

Sorry the new operation is available but we still have not released the underlying fix in the iBridge service. 

I probably shouldn't have released this operation until the iBridge update was released my apologies.

Kind Regards

Trevor Killick

[Steve Giller]

Ah - no problem, just me jumping the gun

[TrevorKillick]

@DeadMeatGF

Sorry i probably should have posted that the fix for this has gone out.

Kind Regards

Trevor Killick

[Keith]

@TrevorKillick Any news on further Flow integration?

I'm also looking for a way to create a request from Flow. Is this possible or likely to be in the future?

 

Regards

 

Keith

 

[TrevorKillick]

@Keith

So @Steve Goldthorpe has done some investigation into this, the ability to integrate into Microsoft Flow and trigger still has not changed the custom HTTP action is the only way at the moment. Also at this point in time, it's not possible for us to publish a connector to MS Flow for easy to use integrations back into hornbill due to some technical constraints on what a connector can do, it might be possible to integrate into hornbill using custom HTTP actions in MS Flow not sure this is something Steve can provide an example of or not. 

Cleaner integration with MS Flow is still on the horizon but requires some pretty large changes our end so not something we are going to be able to solve in the short term.

Kind Regards

Trevor Killick

[Keith]

OK, Thanks for the info @TrevorKillick would be good to get an example @Steve Goldthorpe if possible. 

Are there any other methods of creating Requests in Hornbill other than an email with associated routing rules etc?

 

Thanks!

 

Keith

 

[Steve G]

Hi @Keith,

Sorry, I must've missed this post. Getting Flow to fire API calls off to Hornbill is fairly trivial (albeit not very elegant) with the HTTP action. Following this up with a Parse JSON action containing the relevant schema means that you can read/use the API response too. It's not pretty, but it works...

Here's an example that will log an Incident in Service Manager, and how the HTTP and Parse JSON actions should be configured (with the instance name and API key hidden). This will make available the requestId, summary and warnings API output params available to the rest of your flow.

The XML for the XMLMC call needs to be manually added to the body of the POST action, with details (summary and description) being populated using inputs to the flow:

The JSON schema to parse the output of logIncident, as an example, is: 

{
    "type": "object",
    "properties": {
        "@@status": {
            "type": "boolean"
        },
        "params": {
            "type": "object",
            "properties": {
                "requestId": {
                    "type": "string"
                },
                "summary": {
                    "type": "string"
                },
                "warnings": {
                    "type": "string"
                }
            }
        },
        "flowCodeDebugState": {
            "type": "object",
            "properties": {
                "step": {
                    "type": "string"
                },
                "executionId": {
                    "type": "string"
                }
            }
        }
    }
}

Hope this helps,

Steve

[Keith]

Thanks @Steve G I'll try and make use of this.