Is Survey123 limited to 1 Power Automate webhook per survey?

419
3
Jump to solution
06-02-2021 09:40 AM
erica_tefft
Occasional Contributor III

@IsmaelChivite 

I am wondering if there has been a change to webhooks from Power Automate with Survey123.

Previously, I was able to create multiple webhooks per survey in Power Automate. I'd created them in Power Automate and then see multiple webhooks listed in Survey123 > Settings > Webhooks. Now, when I create my second webhook it appears to 'overwrite' the original. This behavior occurs when working in the same tenant or when migrating webhooks between tenants (Dev to Prod, for example). 

Has anyone experienced this?

I had originally posted this question here in February 2021, but received no response other than from @MATTHEWMERCURIO  who says he is also experiencing this issue. 

Any help would be great.

Thanks!

Erica
0 Kudos
1 Solution

Accepted Solutions
erica_tefft
Occasional Contributor III

Hi @JamesTedrick 

I've been doing testing. I am unsure if this is because I am rusty, but I was able to figure this out. After creating my first flow, I opened Survey123 > Settings > Webhook and renamed the default "MS-FLOW" to "MS-FLOW-webhook1" and saved it. Then, I created a second webhook and saved it. When I refreshed Survey123 > Settings > Webhooks, a second flow named "MS-FLOW" was listed. 

So, it seems changing the name works. I don't remember doing this in the past, but maybe I am just out of practice!

Erica

View solution in original post

0 Kudos
3 Replies
JamesTedrick
Esri Esteemed Contributor

Hi @erica_tefft ,

Apologies for the delay in response.  I am able to successfully create multiple webhooks on a single survey using Power Automate.  Can you be more specific about the issue you are seeing?

0 Kudos
erica_tefft
Occasional Contributor III

Hi @JamesTedrick ,

Here are some more details on what I am experiencing:

1. Open Power Automate and create a new Flow for a survey. Build out the Flow's steps and save. 

2. Go to my survey and view it's Settings > Webhooks page. The webhook is there with the correct timestamp listed. It's name is just MS-FLOW. 

3. Test survey/webhook - it runs as expected. 

4. Go back to Power Automate and build a second Flow for the same survey; this Flow does something different. Save it. 

5. Go back to my survey, view it's Settings > Webhooks page (refresh it). There is still only one webhook listed, however the timestamp has updated to when I just saved my second flow in step 3. There is still only 1 Flow, with the name MS-FLOW. There is no second flow appearing in the list. 

6. Test survey/webhook - it performs the action of the second webhook (step 4) and not the action of the first webhook (step 1). 

This behavior started happening in February for me. I've been trying to figure out what has happened, but I haven't changed anything in my workflow for creating webhooks through Power Automate. There has been some behind-the-scenes stuff happening with Office 365 administration in my agency and I am no privy to what they are doing/how they are changing things. I am unsure if that could be part of the reason I am experiencing these problems. 

I am happy to do a screen share to show you exactly what I am experiencing. There was also someone else who said they were experiencing this too - I tagged him above in the original post. 

Erica 

Erica
0 Kudos
erica_tefft
Occasional Contributor III

Hi @JamesTedrick 

I've been doing testing. I am unsure if this is because I am rusty, but I was able to figure this out. After creating my first flow, I opened Survey123 > Settings > Webhook and renamed the default "MS-FLOW" to "MS-FLOW-webhook1" and saved it. Then, I created a second webhook and saved it. When I refreshed Survey123 > Settings > Webhooks, a second flow named "MS-FLOW" was listed. 

So, it seems changing the name works. I don't remember doing this in the past, but maybe I am just out of practice!

Erica

View solution in original post

0 Kudos