Welcome to Encatch Docs
Data syncBetaConnectorsAutomation

Power Automate

Start a Power Automate flow with each Encatch survey response through the HTTP request trigger

Beta. This connector is set up from Microsoft's documentation and is waiting for its first confirmation on a live Power Automate account. The steps below are a high-level guide: names in Power Automate may differ slightly. Use Test connection and the flow's run history to confirm your set-up, and tell us what you find.

Overview

The Power Automate connector sends each survey response to a Power Automate flow through the When an HTTP request is received trigger.

What it getsEach response starts a flow
EventsSurvey submitted, and Survey partially submitted when ticked
Anonymous respondentsSupported, with Include anonymous respondents on
StatusBeta

What You'll Need

Before you start, make sure you have:

  • A Power Automate Premium licence (or trial) — When an HTTP request is received is a premium trigger
  • About 10 minutes

Step 1: Create the flow in Power Automate

  1. In Power Automate, click Create → Instant cloud flow and pick the trigger When an HTTP request is received.
  2. Set Who can trigger the flow? to Anyone. The tenant-only options need a Microsoft Entra token, which Encatch doesn't send.

Step 2: Give the flow the fields

  1. In Encatch, open Data sync → Survey events, click Add connection and choose Power Automate.
  2. Open Sample payload and click Copy sample payload.
  3. Back in the trigger, click Use sample payload to generate schema, paste and click Done. The flow now knows every field.
  4. Add your actions and Save the flow.
  5. Copy the trigger's HTTP URL. It looks like https://….environment.api.powerplatform.com/powerautomate/automations/direct/workflows/…&sig=….

Step 3: Finish the connection in Encatch

  1. Enter a Name and paste the URL in Webhook URL.
  2. Pick the surveys, click Save, then press Test connection.
  3. Check the flow's run history in Power Automate.
  4. Press Start sending.

The fields are described in the payload reference. If you change the connection's Answer keys option, copy the sample again and regenerate the schema.


Good to know

  • The URL is a key. The sig part of the URL works like a password: anyone with the URL can run the flow. Encatch keeps it encrypted.
  • Old addresses. URLs on logic.azure.com were retired by Microsoft on 30 November 2025; Encatch refuses them. Copy the new URL from the trigger.
  • Partial responses arrive with response.status partial and the answers given so far, once, when Encatch closes the response. A response is sent as partial or as submitted, never both.
  • Anonymous respondents arrive with user.anonymous true, user.id empty and user.anonymous_id set.
  • Repeats. A retry can deliver a response twice: use event_id to skip repeats.
  • Rate limit. A new connection starts at 400 a minute. Power Automate takes 4,500 calls per 5 minutes per flow on Microsoft 365 and free licences (45,000 on others). Each response also counts against the flow owner's daily request allowance, which the rate limit cannot protect.

Troubleshooting

What Encatch showsWhat it meansWhat to do
This URL has no sig keyThe flow isn't set to AnyoneStep 1, save, copy the URL again
Set Who can trigger the flow to Anyone, or the URL's key changedPower Automate refused the callStep 1; copy the current URL
The flow is off or was deletedNo flow at this URLTurn the flow on, or copy the URL of the current flow
This is an old Power Automate addressA logic.azure.com URLCopy the new HTTP URL from the trigger

Was this page helpful?