Testing Your Connector
Power Automate's connector editor has a built-in test console. After saving your connector definition, navigate to the Test tab, create a new connection (which triggers the authentication flow), and run each action manually with sample inputs. The console shows the raw HTTP request sent to your API, the response headers, status code, and body — invaluable for debugging.
Pay particular attention to response schemas. Power Automate uses the response schema to generate the dynamic content picker that makers see in the flow designer. If your schema is incorrect or incomplete, makers won't be able to reference output fields from the connector action — they'll get a generic "body" output instead of named fields. Test with real API responses and update your schema definitions to match.
Sharing and Deploying to Your Organisation
Custom connectors created in the default environment are only visible to their creator by default. To make a connector available to other makers, share it with specific users or promote it to a managed solution that can be deployed across environments. For enterprise-wide deployment, package the connector in a solution, export as a managed solution, and import into production and other target environments through your ALM (Application Lifecycle Management) pipeline.
Microsoft's recommended ALM toolchain for Power Platform uses GitHub Actions or Azure DevOps pipelines with the microsoft/powerplatform-actions runner. This enables automated connector deployment as part of your CI/CD pipeline — connectors ship alongside the flows that depend on them, in a tested, version-controlled package.
Advanced: Webhook Triggers
Webhook triggers require your API to support a subscription model: when a flow subscribes, it calls a registration endpoint on your API with a callback URL. Your API stores this URL and POSTs to it whenever the relevant event occurs. When the flow is disabled or deleted, Power Automate calls an unsubscription endpoint to clean up the registration.
In your OpenAPI definition, you define the webhook trigger with x-ms-trigger: single for triggers that fire once per event, and specify the subscription and unsubscription endpoints using the x-ms-notification-content extension. The Power Platform handles all the callback URL management — your API just needs to implement the subscribe/unsubscribe pattern and call the provided URL when events occur.
Key Takeaways
Custom connectors are the right tool whenever an internal API will be used in multiple flows or by multiple makers — the upfront investment pays back quickly.
OAuth 2.0 with Entra ID is the most secure and maintainable authentication approach for enterprise connectors — it centralises credential management and uses the standard Microsoft identity platform.
Webhook triggers outperform polling triggers for event-driven scenarios — use them whenever your API supports the subscription pattern.
Related Articles
Need a custom Power Automate connector?
We build custom connectors that integrate your internal APIs with the Power Platform — securely, repeatably, and ready for enterprise-scale deployment.