cancel
Showing results for 
Search instead for 
Did you mean: 

Provide Flow details when creating a webhook on a remote service

I reworked the title on this a few times, but I'm not sure I got it right.

 

I'm developing custom and certified connectors for Power Automate. When someone creates a flow using one of our triggers, we want to be able to provide some accounting/auditing within our service so that visitors can see what flows have been triggered.

 

In other words, lets say I handle a system that provides widgets and I publish a custom connector with a trigger of "When a widget is foobarred".

 

Then when the widget is foobarred, the flow runs. Cool. That's awesome.

 

But Mr. ManagerGuy is having some trouble. A customer has called and is claiming he foobarred a widget, but nothing happened. Mr. ManagerGuy can easily navigate to the widget on our service and see "hmm, yep this widget was definitely foobarred. Looks like it was foobarred real good."

 

Because we're nice developers, we track when we send events to the Power Automate webhook that has been established. Our nice log shows Mr. ManagerGuy that this widget was foobarred and that 4 Power Automate webhooks were sent out. But Mr. ManagerGuy has absolutely no idea what those 4 webhooks are, which flows they're associated with, which environment is running them, or anything. All he knows is the time that they were created, and when we pushed data to them.

 

The customer is angry. He worked hard to foobar the widget good, and now he's gonna have to foobar it all up again, but in a totally new way of course.

 

SOLUTION:

Send me some data when you're creating a webhook. Stuff like "Environment" and a URL that I can link users back to the specific flow to edit. Anything that you can provide so that we can make our audit logs useful.

 

If we can't prove to Mr. ManagerGuy what happens when the widgets are foobarred, are they really foobar?

Status: New