Skip to content

Conversation

howellchrisj
Copy link
Contributor

@howellchrisj howellchrisj commented Aug 26, 2025


When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)

If this is your first time submitting to GitHub and you need some help, please sign up for this session.

  • I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
  • I attest that the connector works and I verified by deploying and testing all the operations.
  • I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
  • I attest that I have added response schemas to my actions, unless the response schema is dynamic.
  • I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
  • If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

  • I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
  • Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
  • Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
  • If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

…endent Publisher)/apiDefinition.swagger.json
…endent Publisher)/independent-publisher-icon.png
…endent Publisher)/ConnectWise API Connector 1.png
…endent Publisher)/ConnectWise API Connector 2.png
Added Metadata section
…endent Publisher)/apiDefinition.swagger.json
@howellchrisj howellchrisj requested a review from a team as a code owner August 26, 2025 12:37
@howellchrisj
Copy link
Contributor Author

I keep seeing the branch has conflicts and must be resolved, but I don't see any details.

@vmanoharas
Copy link
Contributor

Hi @howellchrisj,

Our IP connector certification process has been changed. Kindly refer the below link. As per the process, we have shared Form through email that you mentioned in the swagger. Please fill the form to proceed for the next process and please reply here once the form is filled.

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip#step-5-onevet-verification

@howellchrisj
Copy link
Contributor Author

howellchrisj commented Oct 6, 2025 via email

@vmanoharas
Copy link
Contributor

This is not a problem; can you please send the link to the form?  The steps are stating the form will be sent by the connector connection team. On Monday, October 6, 2025 at 11:03:20 AM EDT, vmanoharas @.> wrote: vmanoharas left a comment (microsoft/PowerPlatformConnectors#3979) Hi @howellchrisj, Our IP connector certification process has been changed. Kindly refer the below link. As per the process, we have shared Form through email that you mentioned in the swagger. Please fill the form to proceed for the next process and please reply here once the form is filled. https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip#step-5-onevet-verification — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.>

That's correct email sent by connector certification team @howellchrisj. Kindly fill the form.

@howellchrisj
Copy link
Contributor Author

howellchrisj commented Oct 6, 2025 via email

@howellchrisj
Copy link
Contributor Author

@vmanoharas , I just made a slight update to the .json thinking it would trigger an email, but I have yet to see an email for me to start the process. I have even verified my email address in my profile.

@vmanoharas
Copy link
Contributor

Hi @howellchrisj,

We have just triggered the email again to "[email protected]" from "[email protected]"

@howellchrisj
Copy link
Contributor Author

Hi @howellchrisj,

We have just triggered the email again to "[email protected]" from "[email protected]"

I filled out the form and submitted yesterday. Awaiting the next step to verify my credentials.

@vmanoharas
Copy link
Contributor

Hi @howellchrisj,

Apologies for the delay, we have sent you OneVet request based on the data provided by you. Kindly verify and let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants