Skip to content

Conversation

@OfficeProConsulting
Copy link

This pull request proposes a new independent publisher connector named “MYOB Business - OPC”.

The connector integrates with the MYOB Business API and is intended for use with Power Automate, Power Apps, Logic Apps, and Copilot Studio.

The proposal includes an intro.md file outlining the connector purpose, authentication approach, and commercial model.


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.

@OfficeProConsulting OfficeProConsulting requested a review from a team as a code owner January 2, 2026 06:10
@OfficeProConsulting
Copy link
Author

@microsoft-github-policy-service agree company="OfficePro Consulting"

@vmanoharas
Copy link
Contributor

Hi @OfficeProConsulting,

Thank you for your interest to submit IP connector. Our IP connector certification process has been changed. Please refer the below link and upload the connector package.

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

Additionally, the contact information should contain the email in the swagger file. Please update this fields so we can reach you for Onevet verification

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