You can define the duration to execute this project which can be completed in as little as 5 days, but this article highlights the steps you will take and resources that will be useful as you create and submit your very own independent publisher connector.
(Note: Even if you have never heard of connectors before, don't worry. If you have interacted with APIs before, this is a project you can easily get started on)
Skills that you will learn
Working with APIs – You will select a public API to build a custom connector for.
Brief introduction to concepts that will be useful to know prior to creating your custom connector.
1. What is Power Platform and why is it important?
The power platform contains components that allow citizen developers to create business solutions without requiring a coding background. This concept is important to you since connectors are used by these citizen developers creating Power Apps, Power Automate and Logic Apps.
2. What is Fusion Development and why is it important?
Fusion development is the enablement of code-first developers (Pro-Devs) and citizen developers to cross-collaborate, each entity using their favorite development tools and environments. Citizen developers create business apps and flows used daily while the code-first developers extend the capabilities of power platform or solve complexities using code.
For this project, you will be creating an Independent Publisher Connector since you will be working with an API that is available publicly and owned by someone else, and once certified, your connector can be accessed globally.
If you do not know which connector to build, see a list of the Top Connector Asks today for ideas.
Something important to note: Submit a proposal for the connector you intend to build before you start working on it to inform other developers and avoid duplication. Failure to do this might result in the submission of similar connectors and someone else might just beat you to it.
Title the pull request "Proposal -<Connector Name>(Independent Publisher)". For example, Proposal - HubSpotCRM (Independent Publisher).
Commit areadme.mdfile with as many details as you can provide, including your contact email (if you’re open to finding a collaborator).
Microsoft Certification Engineers will review within 1-2 weeks, and you will be notified in GitHub (on your PR). Please include the below files in your pull request. • apiDefinition.swagger.json • apiProperties.json • Readme.md (you can find an example here and for raw view for code here) • Screenshots of the connector testing
d) Microsoft will test your connector, and we expect all tests to be completed within 1-2 weeks.
e) If your connector passes all tests, the deployment process begins, and it typically takes up to 3-4 weeks to deploy your connector to all our regions.
If you have development questions, go to the Power Automate Forum. This is where you can review answers to existing questions or submit a new question. You can reach out to us directly on this GitHub Discussion
Frequently Asked Questions (FAQs)
1. What are the limits for connectors and API requests? API Limits