What is a connector? Integrating external functions still needs account checks
Distinguish connectors, configured connections and underlying services, checking actions, fields and recovery.
Understand the concept
A connector exposes external actions, data or triggers to an application, often wrapping APIs. Availability does not establish account connection or complete feature coverage. Check authorization, actions and fields and verify target outcomes; connection success is not full task acceptance.
Connector definitions differ from account connections
Microsoft connectors define actions and triggers; Power Automate manages actual connections. Accounts can expose different data and permissions. Custom connectors still maintain underlying contracts. An integration icon does not grant every file. Confirm current actions and scope rather than inferring readiness from a product name.
Check actions and fields with public records
Query a public test table and check required dates and identifiers, empty results and failed authentication. For authorized test writes, inspect target state rather than a success sentence. No connection, private account or write was used here. Distinguish access scope, mappings and service errors; do not invent missing records.
Check dependent flows after interface changes
Account changes can invalidate connections and fields can affect multiple flows. Track dependents and replay public examples after repairs. Include integration and recovery; installation is not permanent availability. Reused connections still need task-specific checks. State covered actions and gaps rather than promising all business automation.
Checked sources
These sources support the concepts and methods described here. Examples and test scope are labeled separately; check the version of the tools you use.