Proposal - PolyDoc (Independent Publisher)

[blue-d3v]

Proposal: PolyDoc (Independent Publisher)

This PR 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 now included in this PR under
independent-publisher-connectors/PolyDoc/. The three operation screenshots and
the final paconn validate run against a tenant will be added, and the
Proposal - prefix dropped, once the verified credentials setup is complete. 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 once screenshots are added.)
• 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

[vmanoharas]

Hi @blue-d3v,

Thank you for interest to submit IP connector. Kindly go through below documents and follow duly.

Please prepare connector package and upload as part of the artifacts. - https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission

Please go through IP connector certification process - https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip

Additionally, please ensure that the title of the PR as per the guidelines (remove proposal when the IP connector policy met)

[blue-d3v]

Hi @vmanoharas,

thanks for the guidance. The connector files are already in the PR under independent-publisher-connectors/PolyDoc/:

• apiDefinition.swagger.json — two operations (Convert to PDF, Capture screenshot) with full request and response schemas
• apiProperties.json — API-key connection, brand color #da3b01
• readme.md

Two things remain on my side before I drop the Proposal - prefix:

1. Verified credentials (OneVet). I have not received the form link yet. Could you point me to how to start the verified-credentials process, or trigger the outreach? That is currently my main blocker.
2. Screenshots of the three operations running in a flow, plus the test operations screenshot. I will add these with the final submission and remove the prefix at the same time.

If a packaged artifact (a paconn connector package) is required in addition to the three files above, let me know and I will add it.

Thank you!

[blue-d3v]

@vmanoharas In the meanwhile I've tested every operation in a Power Platform environment. Screenshots are below.

1. ConvertToPdf — 200, content-type: application/pdf (body %PDF-1.7).

 

2. CaptureScreenshot — 200, content-type: image/png.

 

3. ConvertToPdf in e-invoice mode (Factur-X / EN16931, verify: true) — 200, application/pdf with the embedded e-invoice XML. E-invoice is a mode of ConvertToPdf (one PDF endpoint), not a separate operation, so this connector has two operations by design.

 

4. Definition tab — both operations (ConvertToPdf, CaptureScreenshot), verb POST, host api.polydoc.tech.

 

One question on process: could you point me to how the verified-credentials (One Vet) step is initiated? I haven't received the verification form at my GitHub-registered email yet, and I'd like to complete it so this can move forward. Thanks!

[vmanoharas]

Hi @blue-d3v,

Thank you for your response.

We expect the connector zip package as described in the below document. Please prepare the same and upload as part of the PR.

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission

[blue-d3v]

Hi @vmanoharas,

I've attached package.zip.

It's built per the certification-submission packaging guide: a Package Deployer package (a PkgAssets folder containing the connector solution and a test-flow solution, plus ImportConfig.xml) alongside intro.md. It passes the package validator (ConnectorPackageValidator.ps1 reports "Validation successful: The package structure is correct").

Contents:

• Connector solution: the PolyDoc custom connector.
• Flow solution: a test flow that calls the Convert to PDF action, with its connection reference.

Both connector operations, Convert to PDF and Capture screenshot, were tested end to end (HTTP 200) in a Power Platform environment (screenshots in my earlier comment).

Thanks!