Newbies first question - IDN/ISC Event Trigger to initiate Power Automate Web Hook

I’ve successfully subscribed to a couple of Event Triggers in IDN/ISC and caught them at https://webhooks.io, and I’ve called the APIs in Postman, and Powershell and am hoping that these will translate directly over to MS Power Automate -but- I just can’t figure out how to create a Web Hook in Power Automate that an IDN/ISC Event Trigger can call.

I go to https://make.powerautomate.com > + Create > Automated Cloudflow > " Build an automated cloud flow" > Skip > Add a Trigger > Search: “http” / Runtime: “Built-in”

Here I am given choices of HTTP / HTTP Webhook / HTTP + Swagger and an “In App” / “Trigger” option for each, and I just have no idea how to proceed from here…

For any of those options, I get to select Subscribe Method ( which I guess will be POST), Subscribe URI (no idea what to use), Subscribe Body (presumably this will be the JSON payload) and Unsubscribe Body (again, no idea) with Advanced Parameters for Subscribe/Unsubscribe Authentication/Headers/Method/URI etc

I think I’m fairly close, but am a out of my depth in terms of coding experience of modern cloud systems, and would appreciate any guidance the community can offer…

Hi @nigelwale,

In your case in Powerautomate you must use trigger : “When an HTTP request is received”

After select and that saved your configuration, an url will be generated and you must add this url for your event trigger subscrition in IDN/ISC in same way that you configure on the webhook.

1 Like

@nigelwale is that work for you ?

Hi, well - we’re inching forwards, but I’m getting a message that the “flow was saved, but could not be enabled because it conflicts with the company data loss prevention policies” - so we’re investigating where that conflict in the DLP stems from… feels like we’re very close now, though…

Thanks for the pointer

1 Like

Hi, so I’ve got comms going both ways between Sailpoint from the Event Trigger and to Power Automate and from Power Automate back out via HTTP (got stuck with the AUTH0 authentication back into our IDN/ISC sandbox tenant, but I can do a HTTP to my webhook.site URL).

Essentially, the process for creating a simple Event Trigger into Power Automate is (neither simple or obvious to me anyway), and there may be much better ways of doing this:

  1. I get a (unique) Webhook,site URL for testing

  2. In IDN/ISC I subscribe to an Event Trigger - Account Aggregation Completed is about the easiest one to work with to get used to this (convoluted) process - I use the webhook.site URL in the Integration URL with subscription type “HTTP” and no authentication.

  3. Trigger the event in IDN/ISC by manually initiating an Aggregation in any of my sources.
    Once the aggregation has completed, go to the webhook site URL - find a POST request and copy the JSON “Raw Content” and copy the webhook

  4. In Power Automate:

A) Create a destination Webhook for your trigger event:
i) New Flow > Automated Cloud Flow > [ Skip ] ( I can never find the trigger I need using the long scroll list, even when searching for “http”)

ii) **[ Add a trigger ] > ** search for:?When an http request is received?
Who can Trigger this Flow? => Any user in my tenant / Anyone / Specific users in my tenant

iii) You can’t specify a URL until you complete the Workflow with an action - return to this bit later

iv) In the Request Body JSON Schema, click the link to “Use Sample payload to generate schema” and paste the raw JSON content you copied in (3) and select [ Done ]

B) Create an Action
i) Click on the (+) under the WebHook box in your Power Automate workflow and “Add an Action”
ii) search for “Send an email (v2)” and enter a recipient email address
-or-
ii) search for HTTP and choose the HTTP / HTTP + Swagger / HTTP Webhook green icon. You can use the same webhook.site URL you created in (1) and specify Method=GET

C) Save your Power Automate Workflow
i) Select the top box in the workflow (your HTTP Webhook created in (4A) and you should now have a system generated Web Hook URL that you can use to create a new Event Trigger as per (2) above

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.