You've built or found a great AI API (like OpenAI, Anthropic, or a custom self-hosted model) and you want to trigger it from Power Automate. The catch? You don't want to pay for premium connectors.
Connecting AI to Power Automate is one of the most exciting ways to supercharge your workflows. However, the Microsoft ecosystem heavily pushes its own premium AI Builder and premium third-party connectors.
Can you connect to a custom AI API for free in Power Automate? The short answer is: it depends on your environment, but usually no if you need the generic HTTP action or a custom connector in a production cloud flow.
Last verified: May 13, 2026. Microsoft licensing changes over time, so confirm against the current Power Automate licensing overview and Power Automate licensing error reference before designing around a license assumption.
Let's break down why, and how to actually connect your AI.
The Reality of the HTTP Connector
The standard way to connect to any external API in Power Automate is using the HTTP action.
- You add an HTTP action.
- You set the Method to
POST. - You enter your AI API's Endpoint URL.
- You add your Authentication Headers (e.g.,
Authorization: Bearer YOUR_API_KEY). - You pass your prompt in the JSON Body.
The Catch: HTTP is Premium
Here is the roadblock most users hit: The generic HTTP action is a Premium connector.
If you are on a free or standard Microsoft 365 license, assume you cannot rely on the generic HTTP action for production custom API calls without additional licensing. Microsoft’s current licensing guidance treats premium connectors, HTTP, Dataverse, SQL Server, and custom connectors differently from standard Microsoft 365-seeded use rights.
For production, validate whether the flow needs a Power Automate Premium user license, a Process license, or another approved licensing model.
Are there any "Free" Workarounds?
If you absolutely cannot get a Premium license, there are a few highly restricted workarounds, though they are not recommended for production.
Workaround 1: Azure Logic Apps (Pay-per-execution)
While not technically Power Automate, Azure Logic Apps uses a similar workflow model and often fits custom API orchestration better. In many Logic Apps scenarios, HTTP is a built-in/standard operation and billing is usage-based. At low volume this can be very inexpensive, but it is not literally free: price the trigger, actions, runtime model, and any connected Azure services.
Workaround 2: Custom Connectors (Still Premium)
Building a "Custom Connector" via OpenAPI/Swagger definition makes the integration cleaner, but Custom Connectors also require a Premium license in Power Automate.
Workaround 3: The SharePoint/OneDrive Script Hack
This is a messy, advanced workaround.
- Power Automate writes the prompt to a text file in OneDrive.
- A free local script (e.g., Python or PowerShell) running on your desktop monitors that folder, sees the file, and runs the API call locally.
- The script writes the AI response to a new text file.
- Power Automate reads that new file.
Why you shouldn't do this: It's slow, relies on your PC being turned on, and defeats the purpose of cloud automation.
How to do it the Right Way (With Premium/Logic Apps)
If you have the right license, or you are using Logic Apps/custom code, here is the standard pattern to connect your AI:
- Keep Keys Secure: Never paste your API key directly into the HTTP action if you are sharing the flow. Use Environment Variables or Azure Key Vault.
- The HTTP Action:
- Method: POST
- URI: your AI provider endpoint, such as the current OpenAI Responses API or another provider-specific endpoint
- Headers:
Content-Type:application/jsonAuthorization:Bearer YOUR_KEY
- Body: (Format this according to your specific AI provider's documentation).
- Parse JSON:
The AI will return a large, messy JSON response. Use the Parse JSON action to extract just the actual
contentormessageout of the response so you can use it in your next steps (like sending an email).
Summary
You generally should not plan on connecting to a custom AI API natively in Power Automate using only a strictly free/standard Microsoft 365 license, because the generic HTTP action and custom connectors are premium scenarios.
If this is a business requirement, price the correct Power Automate license against the value of the workflow. If this is a personal or low-volume project, Azure Logic Apps or a small custom service may be a cleaner usage-based alternative.
