Skip to content
Tutorials Center
My learning

Topics

Lesson 16 of 38 ยท Connectors and Data

Power Automate Connectors: Standard, Premium and Custom

Learn what connectors are, how triggers and actions are grouped, the difference between standard, premium and custom connectors, and how to choose and find the right one.

A connector is a wrapper around a service's API that gives you ready-made triggers and actions. Instead of writing HTTP calls with authentication, you pick Send an email (V2) from the Office 365 Outlook connector. There are hundreds of connectors, and knowing how to choose one is a big part of the job.

What a connector contains

  • Triggers: events that start a flow (new email, row added).
  • Actions: operations you can run (create item, get file, send message).
  • A connection type: how it authenticates (OAuth sign-in, API key, basic auth, service principal).

Open Data > Connectors in the maker portal to browse. Every connector page lists its triggers and actions, and links to the documentation with throttling limits.

Standard, premium and custom

Kind Examples License need
Standard Outlook, SharePoint, OneDrive, Teams, Excel Online (Business), Planner, Forms, Approvals, Notifications Included with Microsoft 365 plans
Premium HTTP, SQL Server, Dataverse, Azure services, Salesforce, ServiceNow, many SaaS apps Power Automate paid plan
Custom Your own API described with OpenAPI Premium

Premium items show a diamond. The same connector may be standard in one case and premium in another, for example the Dataverse current environment connector has different rules from the legacy one. Always check the diamond in the designer, not memory.

Preview connectors are marked as preview and can change; avoid them in production if you can.

Built-in connectors

Some capabilities have no external service. These are built-in and run inside the flow engine:

  • Control (Condition, Switch, Apply to each, Do until, Scope, Terminate)
  • Data Operation (Compose, Select, Filter array, Join, Parse JSON, HTML table)
  • Variables
  • Schedule (Recurrence, Delay)
  • Request (HTTP trigger, Response)
  • HTTP (call any URL) - premium
  • Mobile and Notifications (Send me a mobile notification)

Built-in actions are fast and need no connection.

Choosing a connector

Ask three questions.

  1. Is there a first-party connector? Prefer the official one over a generic HTTP call. It handles authentication, paging and changes in the API.
  2. Which version is current? Use (V2), (V3) and so on over older ones.
  3. Do I own the licenses? Premium use must be paid for by whoever runs the flow.
Python Stand-in: pick connectors and flag the license needed

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Throttling and limits

Every connector has limits on calls per minute per connection (for example a few hundred for SharePoint, fewer for some SaaS apps). When you exceed them, the service answers 429 Too Many Requests. Power Automate then retries with a delay by default. Heavy flows can still stall. Reduce calls by using filters, Select instead of loops, and batch operations.

Custom connectors

A custom connector wraps your own REST API (or a public API without a connector) so that people can use it like a built-in one. Create one under Data > Custom connectors > New custom connector:

  1. General: host and base URL, icon, description.
  2. Security: none, API key, basic, OAuth 2.0.
  3. Definition: actions, each with a verb, a URL, parameters and a sample response. You can import an OpenAPI (Swagger) file instead of typing.
  4. Test: create a connection and run an action.

Share the connector with colleagues or package it in a solution. If you only need a few calls, the HTTP action may be simpler, but a custom connector is easier to reuse and secure. Calling APIs with the HTTP action shows the direct approach.

Here is what an OpenAPI path for a custom action boils down to, written as a stand-in dictionary so you can see the parts a connector action needs.

Python Stand-in: the parts of a custom connector action

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Triggers: polling, webhook and instant

Connector triggers can be polling, webhook or manual (see Automated flows and triggers). Connector documentation states the type, and whether the trigger needs a Split On setting.

Common mistakes

  • Using HTTP with a hard-coded password instead of the official connector and its connection.
  • Choosing a preview or deprecated connector for a production flow.
  • Ignoring throttling until the flow slows down in production.
  • Not sharing a custom connector with the people who must run the flow.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is a connector?

    Connectors expose a service's API as triggers and actions inside the designer.
  2. 2. Which is a premium connector or action?

    The HTTP action is premium; Condition and Compose are built in, and Outlook is standard.
  3. 3. What status code signals throttling?

    429 Too Many Requests means the connection exceeded the service's call limit.
  4. 4. What can you import to create a custom connector's definition quickly?

    An OpenAPI definition describes the operations, so the wizard can create actions from it.

Summary

  • Connectors package an API as triggers and actions; built-in connectors need no external service.
  • Standard connectors come with Microsoft 365, premium and custom ones need a paid plan.
  • Prefer official, current-version connectors over raw HTTP.
  • Watch throttling; custom connectors wrap your own API for reuse.

Next: Connections and authentication