How to Pass Different Tokens to a Power Automate HTTP Trigger
Question details
The user needs a way to pass an authentication token to a Power Automate flow using the HTTP request trigger.

- Product
- Microsoft Power Automate
- Device & OS
- not provided
- Scenario
- Configuring an instant flow to accept incoming HTTP requests with token-based authentication.
- Observed behavior
- There is no clear, built-in way to pass or validate a custom token directly within the generated flow URL.
Ensure you have a premium Power Automate license, as the 'When an HTTP request is received' trigger is a premium connector that requires proper licensing.
Consult the Microsoft Power Automate Community
For advanced security configurations and complex token handling, official community experts provide the best guidance.
Handling custom authentication tokens in Power Automate HTTP triggers often involves advanced workflow logic, Azure Active Directory, or Azure API Management.
Because this falls outside standard consumer support, posting your specific token architecture in the Microsoft Power Automate Community is the recommended channel.
Navigate to the official Microsoft Power Automate Community website.
Use the community search bar to look for 'HTTP request trigger token' or 'OAuth HTTP trigger' to see if similar queries have been resolved.
If no existing solution matches your needs, create a new post detailing your flow setup, the type of token you are passing, and the endpoint calling your flow.

Pass Tokens via HTTP Headers or Query Parameters
A common workaround for passing tokens without putting them in the URL path is to use HTTP headers or query parameters.
Looking for a simpler productivity suite? Try WPS Office
While Power Automate handles complex automated workflows, your daily document tasks shouldn't be complicated. WPS Office provides a lightweight, comprehensive, and highly compatible alternative to Microsoft Office for all your word processing, spreadsheet, and presentation needs.

Frequently Asked Questions
Is the HTTP request trigger in Power Automate free?
No, the 'When an HTTP request is received' trigger is a premium connector in Power Automate. It requires a standalone Power Automate premium license or a per-flow plan.
Can I use OAuth2 directly in the Power Automate HTTP trigger?
By default, the HTTP trigger relies on a Shared Access Signature (SAS) token included in the generated webhook URL. To enforce custom OAuth2 authentication, you typically need to route requests through Azure API Management or manually validate the token inside the flow.
How do I restrict who can call my Power Automate HTTP trigger?
You can secure the trigger by setting a 'Trigger condition' in the trigger's settings to check for a specific header value. Alternatively, you can validate an API key passed in the headers using flow logic, or place the endpoint behind a secure API gateway.




