How to integrate Unify with Microsoft Power Automate
To integrate Unify with Microsoft Power Automate, send a POST request from a Unify Play to the tool’s configured webhook trigger and map the received fields into the intended action. Use this connection to start a Microsoft Power Automate cloud flow from a Unify Play.[1][2][3]
- Connection
- Via webhook
- Automation
- Tool
- Microsoft Power Automate
- Microsoft Power Automate
- Data flow
- Unify → Microsoft Power Automate
- JSON payload
At a glance
- Via webhook: Microsoft Power Automate receives the handoff
- POST request with an explicit JSON contract and destination authentication
- Test scenario: Validate tenant restrictions
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
Microsoft-heavy teams often want an account handoff to enter an existing internal process. Keep the flow inside the right tenant and give it a maintained owner. Start with one connector action whose output the receiving team can inspect.
A good fit when
Teams that want to start a Microsoft Power Automate cloud flow from a Unify Play and have an owner for the receiving process. The destination account must permit the documented request and the chosen downstream action.
Reconsider the plan when
The receiving team has not agreed how this Microsoft Power Automate operation should behave when the same record arrives again. Resolve the matching rule before enabling retries.
Design the handoff
Use this framework to agree on the input, the next action, and who owns the result.
Suggested workflow design, based on the documented capabilities below.
| Stage | Decision to make |
|---|---|
| Business decision | Start a Microsoft Power Automate cloud flow from a Unify Play |
| Receiving contract | Agree which of the 5 example data fields the receiving process actually needs. Set missing-value and identity rules in the field mapping below. |
| Execution boundary | Give one owner access to inspect the Microsoft Power Automate request and its resulting action. |
| Completion | Decide who can confirm the Microsoft Power Automate outcome and recover a failed or repeated handoff. Use the completion check below as the acceptance criterion. |
Explore the scenarios
Choose the situation that fits your team and work through the proposed plan.
Open a scenario to explore its plan. Checklists track your selections in this page only.
Start a Microsoft Power Automate cloud flow from a Unify Play
Start with one controlled record and one intended Microsoft Power Automate outcome. Keep the test destination separate from live operations.
The receiving owner must distinguish accepted input from completed work. Agree on the evidence required before treating this handoff as successful.
- Prepare the destination using the Microsoft Power Automate setup checklist
- Resolve the sample fields for one known record and inspect the request before sending it
- Trace that handoff through the receiving operation and compare the actual destination values with the source
Validate tenant restrictions
Validate tenant restrictions: submit a test with missing or invalid authentication and confirm rejection. Then send an authorized sample and compare the destination tenant and owner before enabling the Play.
Decide whether this case should be held for review, corrected, or retried. Make that decision before running Microsoft Power Automate against live records.
- Isolate the test in a controlled destination and record the starting state
- Run the edge case described above and capture the actual response and destination state
- Recover the record once, then check that recovery did not create unintended additional work
Illustrative workflow, not a preconfigured automation. Complete these checks in your own account.
Define success before launch
Inspect the data and the intended outcome separately. Connection status is only the first check.
Expected, not tested
Start a Microsoft Power Automate cloud flow from a Unify Play
Check the flow run history and the result of the intended connector action under the expected Microsoft tenant.
Documentation-based reference. This workflow has not been tested end to end. Use a record or event you control before enabling live activity.
Questions answered
Common decisions when connecting Unify and Microsoft Power Automate.
Can Unify call a tenant-restricted flow with only its URL?
No. Restricted HTTP triggers require a token with the documented audience and tenant claims. Use an intermediary that obtains and renews that token when needed.[3]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + Microsoft Power Automate workflow.
POST / JSON
| Decision | What to know |
|---|---|
| Unify action | Outbound HTTP request with configurable method, authentication, headers, and body[1] |
| Receiving operation | Create a flow with When an HTTP request is received and define the JSON schema for the handoff. Choose who may trigger it before copying its generated URL.[3] |
| Response handling | Webhook response bodies are not available as inputs to later Unify Play actions[2] |
Technical setup reference
References and requirements for the Microsoft Power Automate connection.
Connection requirements and setup checklist
Before connecting
- A Unify Play with a Webhook action and a controlled record for testing
- Access to the intended Microsoft Power Automate environment and the permissions required by the cited API or trigger
- The destination identifiers, credentials, and schema used by the request below
- An agreed record identity, duplicate policy, and owner for failed handoffs
Prepare the Microsoft Power Automate destination
Create a flow with When an HTTP request is received and define the JSON schema for the handoff. Choose who may trigger it before copying its generated URL.[3]
Configure the destination action
Configure the target connector under an appropriate owner. If tenant authentication is required, place a token-managing receiver before the flow and point Unify at that receiver.[3]
Configure the Unify request
Use POST, the endpoint and authentication below, and JSON body format in the Webhook action. Replace setup placeholders, then inspect Expand preview with a controlled record. The receiver must respond within 8 seconds; webhook response bodies are not exposed to later Play steps.[1][2]
Validate the complete handoff
Run the success and edge-case scenarios in Explore the scenarios with a controlled record. Save the request identity and destination evidence, then apply the completion check before enabling live traffic.[3]
Request configuration
- Method
POST- URL pattern
https://YOUR_POWER_AUTOMATE_HTTP_TRIGGER_URL- Headers
Content-Type: application/json- Authentication
- Choose the HTTP trigger authentication deliberately. Tenant-restricted modes need a valid Entra bearer token with the required audience and claims, normally managed by an intermediary. The Anyone mode relies on possession of the generated URL.
Choose JSON as the body format. Unify sets Content-Type automatically. The receiver must respond within Unify’s 8-second timeout; request responses are not passed to later Play steps.[2]
Replace URL placeholders with the actual receiver URL from your account or deployed application. These example URLs are not working endpoints.
Example handoff payload
Start with a fictional prospect. Validate the resolved values before using a real record.
Inspect the sample payload and field mapping
{
"event": "prospect_handoff",
"handoff_id": "example-handoff-001",
"prospect_name": "Alex Morgan",
"prospect_email": "alex@example.com",
"company_name": "Example Company",
"company_domain": "example.com"
}Fictional data. Replace sample values before using a real Play.
Illustrative JSON for the documented receiving operation. All prospect values are fictional. Replace credentials, identifiers, schema-specific fields, and fixed example values before a controlled test. Use the field mapping to distinguish record data from fixed settings. Select available fields in your Play and inspect Expand preview; do not replace configuration values with prospect data.[1][2][3]
| Payload field | Value to send |
|---|---|
event | Keep the literal "prospect_handoff" required by this example request; change it only when deliberately changing the receiving contract. If missing: Keep this configured value in the request; do not replace it with a blank prospect field. |
handoff_id | Supply a stable identifier for this logical handoff. Reuse it on a retry, and use a different identifier for a genuinely new event. Do not assume Unify automatically creates this sample field. If missing: Hold the handoff until the receiver or upstream workflow can establish its identity. |
prospect_name | Select the available full name field for the controlled person or company record in Unify. Keep the receiving field a string. If missing: Skip or hold the handoff if this value is required by the destination; omit it only when the destination contract permits omission. Do not send a guessed value. |
prospect_email | Select the available email field for the controlled person or company record in Unify. Keep the receiving field a string. If missing: Skip or hold the handoff if this value is required by the destination; omit it only when the destination contract permits omission. Do not send a guessed value. |
company_name | Select the available company name field for the controlled person or company record in Unify. Keep the receiving field a string. If missing: Skip or hold the handoff if this value is required by the destination; omit it only when the destination contract permits omission. Do not send a guessed value. |
company_domain | Select the available company domain field for the controlled person or company record in Unify. Keep the receiving field a string. If missing: Skip or hold the handoff if this value is required by the destination; omit it only when the destination contract permits omission. Do not send a guessed value. |
Use properties from the trigger body in the destination connector. Treat tenant identity, flow owner, and prospect owner as different identities.
Troubleshooting
Start with the stage where the expected data or action stops appearing.
The request is rejected
Choose the HTTP trigger authentication deliberately. Tenant-restricted modes need a valid Entra bearer token with the required audience and claims, normally managed by an intermediary. The Anyone mode relies on possession of the generated URL. Check the receiving account, permissions, endpoint, and required fields against the cited documentation.[3]
The values or destination are wrong
Compare the resolved JSON with the field-by-field contract in Example handoff payload. Check identifiers against the selected Microsoft Power Automate environment, and distinguish an absent source value from an intentional static value. Fix the mapping before repeating the write.[3]
Receipt does not match the expected result
Find the request in the receiving logs, then inspect the actual Microsoft Power Automate resource or execution. If the request was accepted but no result exists, investigate the destination failure before retrying. Keep the same logical handoff identity when recovering a repeat.[3]
Sources & review
Official documentation reviewed on September 15, 2026.
Technical claims link to primary documentation from Unify and the destination tool. Scenarios, field choices, and recovery plans are editorial implementation examples. Documentation review is separate from execution testing.
Documentation reviewed; end-to-end execution not tested. No named technical reviewer has signed off on these articles yet.
Content updated: . Report a correction to Unify with the tool name, source URL, and behavior you observed.
Keep exploring
