Power Automate connectors

Penneo publishes two certified connectors for Microsoft Power Platform. They let you create case files, poll for case file creation, poll for casefile status, and download signed documents from a Power Automate flow without writing any code.

Both connectors are open source and maintained in Microsoft's connector repository:

• certified-connectors/Penneo Sign
• certified-connectors/Penneo Sign Sandbox

Choosing an environment

The two connectors expose exactly the same actions with exactly the same fields. The only difference is which Penneo environment they talk to:

Build and test your flow with Penneo Sign Sandbox, then swap the connection over to Penneo Sign for production. Because the action names and fields are identical, no other changes to the flow are needed.

Prerequisites

• An active Penneo account (a sandbox account for the sandbox connector).
• A Power Automate, Power Apps, or Logic Apps environment.

Authentication

Both connectors use OAuth 2.0 Authorization Code Grant. When you create the connection, Power Platform redirects you to Penneo's login page and you sign in with your regular Penneo credentials - there are no API keys to manage in the flow.

The connectors request no scopes, and the connection acts as the signed-in user - so the case files it creates are owned by that user, and it can only read case files that user has access to.

Actions

Each connector ships four actions.

The typical flow

Case file creation is asynchronous, so a complete end-to-end flow has four steps:

1. Create a new case file - pass the title, base64 encoded PDFs, and signers. You get back a job uuid and a payloadHash.
2. Check job status - poll with that uuid and payloadHash until jobStatus is completed. The completed job's result contains the created caseFileId.
3. Get case file details - call with the case file id. Wait for status 5 (completed) before downloading; until then the signers haven't all signed.
4. Download document - call once per document id from step 3, then decode the base64 content into a PDF file.

Create a new case file

The request body is a single caseFile object.

Case file fields

Document fields

Signer fields

Only name is strictly required, but in practice you also want email so Penneo can send the signing request.

Available values for secureSigningMethods:

mitid.dk                    bankid_se                   bankid_no
itsme.be                    ftn.fi                      eid.belgium.be
passport-reader.eident.dk   ausweisapp.bund.de
qes.personal.mitid.dk       qes.erhverv.mitid.dk

Check job status

Send the uuid and payloadHash from the create step. The response includes:

Get case file details

Takes the caseFileId and returns the case file with its signers (name, id, and the signing request's email and status) and its documents (id, status, and whether the document is signable). The documentIds are what you pass to Download document.

Case file status values:

Use status 5 (completed) as the trigger for downloading signed documents.

Download document

Takes a document id and returns a content field with the base64 encoded document. The optional Signed parameter defaults to true.

If a case file contains several documents, loop over the document ids from Get case file details - the action returns one document per call.

Working with base64 in Power Automate

Both the request and response side of these connectors use base64 encoded PDFs:

• Uploading: use the base64() expression on the file content, for example base64(outputs('Get_file_content')?['body']).
• Downloading: use base64ToBinary() on the returned content before writing the file, for example in a Create file action for SharePoint or OneDrive.

Large PDFs take longer to process and inflate roughly 33% when base64 encoded, so keep an eye on document size in high-volume flows.

Known limitations

• Asynchronous creation. Creating a case file returns a job, not a case file. You must poll Check job status; there is no synchronous create.
• Polling, not webhooks. These connectors have no triggers, so a flow reacting to signing completion has to poll Get case file details. If you need push notifications, use webhooks against the REST API instead.
• Rate limit. 20 requests per minute per uuid + payloadHash on Check job status.
• Environment is fixed per connector. A connector cannot be pointed at a different Penneo environment - pick the connector that matches the environment.

Where to go next

• Field-level reference for every case file property: Create case file.
• Building something more custom than a flow? Start with the Direct REST API.