Electronic signature for Power Automate and Microsoft 365
Import the Certyneo custom connector into Power Automate and connect your envelopes to SharePoint, Teams, Outlook, Dynamics 365 and thousands of other connectors. Trigger a flow the moment an envelope is sent, signed or declined, and create or send envelopes from any flow — without writing a line of code.
The Certyneo connector for Power Automate is a custom connector you import into your own environment — it is not yet listed in the certified Microsoft connector directory.
Why connect Certyneo to Power Automate
Power Automate bridges Certyneo and the rest of the Microsoft 365 / Power Platform stack. You automate signature tracking and contract sending without development.
Real-time trigger
Start a flow as soon as an envelope is sent, signed by a recipient, finalized, or declined. Events arrive via webhook, without polling.
Actions
Create an envelope from a template, send it for signature, check its status or upload a document, from any Power Automate flow.
Zero code
Assemble your automations in Power Automate's visual designer. No infrastructure to maintain, no webhook endpoint to host on your side.
Secured by API key
The connection authenticates with a limited-scope Certyneo API key, which you can revoke at any time from your dashboard.
Your signatures across Microsoft 365
There is no Certyneo app to install in Microsoft 365 — Power Automate is the app. Every standard connector in your subscription becomes a starting point or a destination for a signature, and your documents never leave the path you described.
SharePoint
A contract dropped in a document library goes out for signature; the signed PDF and its audit trail come back to a dedicated folder, and the original row keeps the outcome.
Teams
A declined signature is posted in the channel that cares, with the reason the signer gave — rather than in an inbox nobody reads twice.
Outlook
An attachment becomes an envelope, and a request that expires warns its owner with the list of recipients who never signed.
Microsoft Forms
A form response sends one of your envelope templates to the address it collected: job offer, mandate, waiver — the document stays the same, only the signer changes.
Excel and OneDrive
Every completed signature adds a row to an Excel table and drops the signed PDF into OneDrive: a log that keeps itself, with no double entry.
Dynamics 365 and the rest
Over a thousand standard connectors are available in the same flow. Whatever starts a signature at your company does not have to exist in our integrations catalogue.
The Certyneo connector is a premium connector: using it requires a Power Automate Premium licence, as it does with the other electronic signature vendors.
Available trigger
A single trigger covers every envelope event — pick which ones start your flow when you create it.
| Event | Triggers when… |
|---|---|
| Envelope sent | An envelope leaves draft status and goes to its recipients. |
| Recipient signed | A recipient completes their signature. Triggers once per signer, not just at the end. |
| Envelope signed | All recipients have signed: the envelope is finalized. |
| Envelope refused | A recipient refuses to sign the envelope. |
Available actions
Control Certyneo from any Power Automate flow.
Create an envelope
Build an envelope from a saved template, or straight from documents you uploaded — place each signature by quoting a phrase from the document, no coordinates needed. This action only creates the draft — no email is sent at this stage.
Send envelope
This is the step that actually sends the email to recipients. Always chain it right after "Create envelope", which only prepares the draft.
Get envelope
Check the current status and details of an envelope.
Upload document
Upload a PDF or image, then pass it to "Create envelope" under Documents.
Download signed document
Fetch the signed PDF, certificate page included, once every recipient has signed. Send it straight to SharePoint, OneDrive or your DMS.
Download audit trail
Fetch the evidence file: who signed, when, from which IP, with which authentication factors. Archive it next to the signed PDF — it is what a dispute turns on.
Delete draft envelope
Delete an envelope that was never sent — a flow that failed halfway, a wrong document. Drafts only: once an envelope has gone out it cannot be recalled from a flow.
These two actions are independent: "Create envelope" only saves a draft, no email is sent. Always add "Send envelope" right after it in your flow so the email actually reaches recipients.
Set up the integration
A few minutes are enough to import the Certyneo connector into your Power Automate environment.
- 1
Download the connector file
Download the Certyneo custom-connector definition — a ready-to-import OpenAPI file.
Download connector.json - 2
Generate your API key
Open Certyneo → Settings → API Keys and generate a key. Copy it: it is displayed only once.
- 3
Import the connector
In Power Automate, go to Custom connectors → New custom connector → Import an OpenAPI file, then paste "Bearer " followed by your API key when prompted for the connection.
- 4
Build your flow
Choose the Certyneo trigger or action and connect it to SharePoint, Teams, Outlook or any other connector.
Six flow templates, written and stress-tested
Signature flows break in the same few places: a document sent without a signature field, a PDF asked for before it is sealed, a retry looping on a document that was purged for good. Our six templates carry those guards — you should not have to discover them in production.
Publication in the template gallery follows connector certification
Send a new SharePoint file for signature
The file goes out for signature with a field placed next to your anchor phrase, and the library keeps the envelope ID.
File the signed PDF and its audit trail
As soon as an envelope completes, the sealed PDF and its eIDAS audit trail land in a dedicated folder, and the original row switches to "Signed".
Send a request from a form response
A Microsoft Forms response creates the envelope from one of your templates and addresses it to the signer it collected.
Post a declined signature to Teams
The channel receives the envelope, the person who declined and the reason they gave.
Log signatures to Excel
Every completed envelope adds its row to the table and archives the signed PDF to OneDrive.
Warn when a request expires
The owner gets an email listing the recipients who never signed, the day the envelope expires.
In the meantime all six are documented step by step: trigger, actions, values to fill in and failure cases to plan for. Each takes about ten minutes to build in the designer.
Security and compliance
The Power Automate connection is based on the Certyneo public API, with the same level of requirement as the rest of the platform.
- End-to-end encrypted exchanges over HTTPS.
- Limited-scope API keys: grant only necessary permissions.
- Hosting in Europe and GDPR compliance.
- Revoke a key at any time from your dashboard.
Frequently asked questions
Which Certyneo subscription is required to use Power Automate?
Access to the API and webhooks, which power the integration, is available on paid plans including developer access. The trigger relies on webhooks, actions on the REST API.
How do I get my API key, and how do I enter it in Power Automate?
From Certyneo, go to Settings → API Keys and generate a key. It starts with sk_live_ (or sk_test_ for the sandbox) and is displayed only once: copy it immediately. Power Automate's generic API-key field does not add the word "Bearer" for you, so enter exactly "Bearer sk_live_..." (with the space) when the connection asks for your API key.
Is there anything to install in Microsoft 365?
No. There is no app to deploy in your Microsoft 365 tenant and no admin consent to request. You import the Certyneo connector into your own Power Automate environment and authenticate it with an API key you generate — and revoke — from your dashboard. Your flows then use the SharePoint, Teams or Outlook connectors your subscription already grants you.
Is the connector listed in Microsoft's certified connector directory?
Not yet — it is a custom connector you import directly into your own Power Automate or Power Apps environment from the connector file Certyneo publishes. It works exactly like a certified connector once imported.
Which signature events are covered?
Envelope sent, recipient signed, envelope finalized and envelope declined. Other events in the envelope lifecycle are exposed by the API and can be added to the trigger's event list.
Are the flow templates already in the gallery?
Not yet. A template in the Microsoft gallery can only build on a certified connector, and our certification is under way. All six scenarios are fully specified in the meantime: the documentation gives the trigger, every action, the values to fill in and the failure cases to plan for. Nothing stops you from building them today in the designer.
Does my data transit through Power Automate?
Only metadata necessary for your automation (subject, status, signatories' emails) transits through Power Automate, over encrypted exchanges. The content of signed documents is not sent in trigger payloads.
Is the Power Automate integration paid?
Certyneo does not charge an additional fee for the integration. A Power Automate / Power Platform license may be required depending on flow volume and premium connector usage, on Microsoft's side.
Go further
Automate your contracts today
Connect Certyneo to Microsoft 365 and the Power Platform via Power Automate and let your signatures trigger the rest.