Connecting a Custom AI API to Power Automate (What’s actually possible for free)

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.

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.

1. You add an HTTP action.
2. You set the Method to POST.
3. You enter your AI API's Endpoint URL.
4. You add your Authentication Headers (e.g., Authorization: Bearer YOUR_API_KEY).
5. 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 (the one that comes with Office), you cannot use the HTTP action to call your custom AI API. You must have a standalone Power Automate Premium per-user license.

---

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 is the exact same engine under the hood. In Logic Apps, the HTTP connector is standard, not premium. You pay fractions of a penny per execution. If your volume is low, this is essentially "free" compared to a $15/month Power Automate license.

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.

1. Power Automate writes the prompt to a text file in OneDrive.
2. 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.
3. The script writes the AI response to a new text file.
4. 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 are using Logic Apps), here is the standard pattern to connect your AI:

1. 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.
2. The HTTP Action:
   • Method: POST
   • URI: https://api.openai.com/v1/chat/completions (or your endpoint)
   • Headers:
     • Content-Type : application/json
     • Authorization : Bearer YOUR_KEY
   • Body: (Format this according to your specific AI provider's documentation).
3. Parse JSON: The AI will return a large, messy JSON response. Use the Parse JSON action to extract just the actual content or message out of the response so you can use it in your next steps (like sending an email).

Summary

You cannot connect to a custom AI API natively in Power Automate using a strictly free/standard Office 365 license because the HTTP connector is Premium.

If this is a business requirement, the $15/month Premium license is well worth the cost. If this is a personal or low-volume project, Azure Logic Apps is the perfect, virtually free alternative that uses the exact same interface.