Skip to content

Power Automate

Can Power Automate call REST APIs?

By Suresh Girinathuni

Quick answer

Power Automate calls REST APIs three ways, in preference order: a purpose-built connector (managed auth, best triggers), the generic HTTP action for direct calls with headers, queries, and OAuth via Entra ID app registrations, and custom connectors that package an API with its auth for reuse across flows and environments. Reserve raw HTTP for gaps; promote repeated integrations to custom connectors under solution ALM.

Key takeaways

  • Connector first, HTTP action second, custom connector for reuse.
  • Authenticate via Entra ID; store URLs in environment variables.
  • Premium licensing applies — verify; wrap calls in error handling.

Detailed Explanation

Power Automate calls REST APIs three ways, in preference order: a purpose-built connector (managed auth, best triggers), the generic HTTP action for direct calls with headers, queries, and OAuth via Entra ID app registrations, and custom connectors that package an API with its auth for reuse across flows and environments. Reserve raw HTTP for gaps; promote repeated integrations to custom connectors under solution ALM.

How it works

The flow presents an Entra ID identity (delegated user or service principal context depending on design), acquires tokens, and calls endpoints with parsed JSON responses. Store base URLs in environment variables and connections behind connection references so Dev, Test, and Production rebind cleanly.

Limitations and considerations

HTTP actions and custom connectors carry premium-licensing implications — verify currency per scenario. External APIs add timeout, throttling, and secret-rotation burdens that belong in Try/Catch scopes with logging, not inline hope.

This Q&A page is the short-answer layer for “Can Power Automate call REST APIs?” Use the related guides below when you need implementation steps, architecture trade-offs, or troubleshooting detail.

For broader context, visit the Power Automate Hub. It connects this topic to surrounding Microsoft 365, Power Platform, SharePoint, Copilot Studio, Dataverse, migration, and Dynamics 365 guidance.

When to use it

Call REST when no connector exists (Microsoft Graph edge cases, line-of-business APIs, webhooks) and wrap every call with error handling and owner notifications.

Practical example

A flow calls the Graph API over HTTP to list inactive Teams, writes candidates to a SharePoint list for owner review, and logs failures with the failing team ID.

Related Questions

What is Power Automate?Power Automate is Microsoft’s cloud automation platform for creating workflows between apps, services, data, and APIs.How should errors be handled in Power Automate?Enterprise flows should use structured error handling with scopes, run-after rules, logging, notifications, and retries where appropriate.What is Microsoft Graph?Microsoft Graph is the unified API for Microsoft 365: one endpoint model to read and manage users, groups, Teams, SharePoint, mail, calendars, and more — governed by explicit permissions and consent.Can Power Automate call Microsoft Graph?Yes — via the HTTP action with an Entra ID app registration (delegated or application permissions plus admin consent), or through purpose-built connectors where they cover the need.

Related nextM365 Guides

Power AutomatePower Automate Error Handling: Build Reliable FlowsLearn how to build reliable Power Automate cloud flows with run after settings, Try Catch Finally scopes, retry policies, error logging, notifications, validation, and monitoring.Microsoft 365Microsoft Graph API Explained for BeginnersA beginner-friendly Microsoft Graph API guide explaining what Graph is, how requests work, permissions, tokens, endpoints, common use cases, and safe API design.

Sources