How to Redirect a Power Automate HTTP Request to Another URL
Question details
The user needs to redirect an HTTP GET request to another URL or Microsoft Teams page after running a SharePoint-triggered Power Automate flow, preventing the browser from showing a blank page.

- Product
- Power Automate
- Device & OS
- not provided
- Scenario
- A user is setting up an automated flow in Power Automate triggered by SharePoint and wants the end user to be seamlessly routed to a specific destination URL once the HTTP request executes.
- Observed behavior
- Standard HTTP redirect status codes (like 308) fail to route the user properly, resulting in a blank page rather than the intended destination URL.
Ensure you have edit permissions for the Power Automate flow in question and have access to test the SharePoint trigger that initiates the HTTP request.
Return Status Code 200 with an HTML Meta-Refresh
Instead of using standard HTTP redirect codes, returning a successful 200 status code with an embedded HTML meta-refresh reliably forces the user's browser to redirect to the new page.
SharePoint Online does not offer a built-in feature to cleanly handle standard HTTP redirects in this specific trigger scenario. The most reliable workaround involves faking a successful page load (200 OK) that instantly tells the browser to load the new destination.
Open your Power Automate flow in edit mode and navigate to your HTTP response action at the end of the flow.
Change the 'Status Code' field from 308 (or any other 3xx redirect code) to 200.
In the Headers section, add a new row. Set the Key to 'Content-Type' and the Value to 'text/html'.
In the Body field, insert the following HTML snippet: <html><head><meta http-equiv="refresh" content="0; https://example.com/"></head></html>. Replace 'https://example.com/' with your actual target URL or Microsoft Teams link.
Save your flow changes, return to SharePoint, and trigger the action to ensure it correctly redirects without leaving a blank page.

Seek Advanced Customization in Microsoft Q&A
If the basic HTML meta-refresh does not meet complex enterprise needs, custom SharePoint Framework (SPFx) development may be required.
Discover WPS Office for Your Everyday Productivity Needs
While Power Automate and SharePoint manage complex automated workflows, WPS Office is an excellent lightweight alternative for your daily document, spreadsheet, and presentation tasks. It offers robust capabilities without the hefty subscription costs.

Frequently Asked Questions
Why does a 308 redirect status code cause a blank page in Power Automate?
When a SharePoint trigger invokes a Power Automate HTTP request, the client-side environment may not automatically follow standard 3xx HTTP redirect headers. The browser effectively stalls on the response URL, resulting in a blank page rather than following the redirect instruction.
Can I add a delay before the HTML redirect happens?
Yes. In the meta-refresh tag (<meta http-equiv="refresh" content="0; https://example.com/">), change the '0' to the number of seconds you want the browser to wait before it executes the redirection.
Does SharePoint Online have a built-in action for redirecting users after a flow?
No, SharePoint Online does not currently provide a native, built-in feature to redirect the user's interface after triggering a background Power Automate HTTP flow. This is why the HTML meta-refresh workaround is widely recommended.
What if I need to redirect to a Microsoft Teams page?
The meta-refresh approach works identically for Microsoft Teams. You simply replace the destination URL in the meta tag with the specific Microsoft Teams deep link or channel URL you wish to route users to.




