Proposal - PolyDoc (Independent Publisher)

[blue-d3v]

Proposal: PolyDoc (Independent Publisher)

This proposal reserves the connector name and starts the verified credentials
process. PolyDoc converts HTML or a URL into PDFs and
screenshots and generates EU-compliant hybrid e-invoices (ZUGFeRD / Factur-X),
rendering in a real browser engine.

The complete, validated connector files (apiDefinition.swagger.json,
apiProperties.json, readme.md) are ready and will be added to this same PR,
along with the required operation screenshots, once verification is set up. The
full definition is also public at
https://github.com/polydoc-tech/power-automate-polydoc.

Checklist

• I attest that the connector doesn't exist on the Power Platform today. I verified by searching the pull requests and the connector documentation.
• I attest that the connector works and I verified by deploying and testing all the operations. (Pending tenant import; will be completed with the final submission.)
• 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 by running paconn validate. (Validated against OpenAPI 2.0 offline; paconn validate requires a tenant login and will be run before final submission.)
• Independent publisher: brand color is #da3b01 and no connector icon is submitted.
• PR named "Connector Name (Independent Publisher)". (Prefixed "Proposal -" for now; the prefix will be dropped at final submission.)
• Screenshots of 3 unique operations succeeding in a flow. (Pending; added at final submission.)
• Screenshot from the Test operations section of the Custom Connector UI. (Pending; added at final submission.)
• OAuth: not applicable. The connector uses API key authentication.

[blue-d3v]

@microsoft-github-policy-service agree