LanguageTool (Independent Publisher)

[fordosa90]

---

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.

[fordosa90]

[fordosa90]

@Amjed-Ayoub no screenshots from the "TEST" screen of the connector itself, as apparently PowerAutomate has some bugs and can not test POST requests with application/x-www-form-urlencoded content type. Nonetheless, screenshot from an actual flow proves success

[Amjed-Ayoub]

[[certify-connector]]

[Amjed-Ayoub]

Hello @fordosa90,
I hope you are doing well.
Congratulations, your pull request is approved. We will move forward with the certification process. We are preparing your connector for production deployment and will queue up for the next deployment schedule. Once your connector onboards the next deployment schedule, it starts to deploy your connector in our production environments that typically takes 3-4 weeks.
Please let us know if you have any questions.
Thank you very much for working with us.

[fordosa90]

@Amjed-Ayoub thank you for the quick process!
One question. When needing to update the info/contact/email information in the apiDefinition.swagger.json, does it need also a version bump for the connector too from 1.0.0 to 1.0.1? Or not, as it actually does not change the connector itself, rather just the contact details for the MSFT documentation?

[Amjed-Ayoub]

@Amjed-Ayoub thank you for the quick process! One question. When needing to update the info/contact/email information in the apiDefinition.swagger.json, does it need also a version bump for the connector too from 1.0.0 to 1.0.1? Or not, as it actually does not change the connector itself, rather just the contact details for the MSFT documentation?

Since it is a small change then you can leave the version as is. It is optional :-)

[Amjed-Ayoub]

Hello @fordosa90,
I hope you are doing well.
Your connector is in production deployment and queued up for the next deployment schedule. This process typically takes 3-4 weeks. Please note that the documentation for your connector will not be generated until the deployment process is in the final steps.
Please let us know if you have any questions.
Thank you very much for working with us.

[Amjed-Ayoub]

Hello @fordosa90,
I hope you are doing well.
Congratulations, the deployment of your connector and documentation page was already completed, We have a short survey on the connector certification process that we would like for you to complete. Your feedback is appreciated and will help us improve the program.
Thank you very much for working with us.