Skip to main content
You can automate Flowsign with Power Automate using its own HTTP trigger and action: trigger a flow when a package completes, or create and send a package from another system through a flow.

Receiving events

Create a webhook endpoint in Flowsign at Settings > Webhooks (my.flowsign.app/settings/webhooks), or with the API (see Webhooks).
  1. Create a flow that starts with When an HTTP request is received and save it once so Power Automate generates its URL.
  2. Paste that URL into the endpoint’s Endpoint URL field in Flowsign.
  3. Tick the events to subscribe to (for example Package completed) and save. Flowsign shows the endpoint’s signing secret once; store it.
The endpoint receives events for the packages in the workspace it was created in. Every delivery is a POST with four headers and a JSON body:
data differs per event. See Events for every event’s shape.

Verifying the signature

Skipping verification means your flow acts on any unauthenticated POST to its trigger URL, not just genuine Flowsign deliveries.
The signature is a hex HMAC-SHA256 of the x-flowsign-timestamp header, a ., and the exact raw body, keyed with the endpoint secret (see Webhooks). Power Automate’s workflow expression language has no built-in keyed-hash function, and the trigger hands the flow a parsed body whose re-serialised JSON isn’t guaranteed to match the bytes Flowsign signed. The practical option is to verify before the flow runs. Point the Flowsign endpoint at a small HTTP endpoint you control (an Azure Function is the usual choice) that builds the signed content from the raw body and the x-flowsign-timestamp header, checks it against each v1= entry in x-flowsign-signature, refuses timestamps more than 5 minutes old, and forwards only valid deliveries to the flow’s trigger URL. Keep the trigger URL itself private, since anyone holding it can start the flow.

Calling the API

Use the HTTP action for any Flowsign API call. Base URL: https://my.flowsign.app. Every request needs: Create the key at Settings > API keys and choose the workspaces it can act in; see Authentication. Keep it in an environment variable or Azure Key Vault reference rather than typing it into the action.

List packages

Method GET, URI https://my.flowsign.app/api/v1/packages?status=IN_PROGRESS.

Create a package from a template

Method POST, URI https://my.flowsign.app/api/v1/packages/from-template, body:
role must match one of the template’s role names and every role must be filled; fields keys must be merge fields the template asks the sender for. A mismatch returns 422 with the unknown or missing names in details. status is "draft" (default) or "sent", which sends immediately. externalId is optional and makes the call idempotent: retrying with the same value returns the existing package instead of creating a duplicate.
Creating requires the key’s role to have the send packages permission and Use access to templates. A key can use only the templates its issuer created or has been shared, so share a colleague’s template with the issuer first. A key that acts for members can use only the templates the named member can see. See Errors for the full status code list.

Recipe: save signed PDFs to SharePoint or Google Drive

This flow files every completed package as a PDF in a SharePoint document library or a Google Drive folder. It has three steps: catch the event, download the PDF from Flowsign, and hand it to the storage connector.
1

Catch the completed event

Set up the When an HTTP request is received trigger as in Receiving events, and subscribe the Flowsign endpoint to Package completed only.Flowsign sends the event once the signed copies are ready, so the flow can download straight away.
2

Download the signed PDF

Add an HTTP action:The response is the PDF itself: every document in the package merged into one file. certificate=true appends the certificate of completion; leave it off for the documents alone.
3

Save the file

Add the storage connector’s Create file action.
Send a test from the endpoint’s Send test event button to check the trigger fires. The test event’s packageId is pkg_test, which has no file, so the download step returns 404 until a real package completes. Things to know:
  • File names. Naming the file by packageId is always safe. To use the title instead, strip the characters SharePoint refuses (" * : < > ? / \ |) first, for example @{replace(triggerBody()?['data']?['packageTitle'], ':', ' -')}.pdf. Two packages can share a title, so keep the id in the name if the folder must never overwrite.
  • Filing by custom field. data.metadata carries the package’s custom field values, so a value such as @{triggerBody()?['data']?['metadata']?['client_code']} can pick the folder.
  • Separate files. For one file per document instead of a merged PDF, call /download/zip and save the zip, or list the package with GET /api/v1/packages/{packageId} and download each document id with ?documents=.
  • Large packages. A package too large to merge returns 413. Use /download/zip for those.
  • Permissions. The key’s role needs the send packages permission, and the key must act in the workspace the package belongs to.

Recipe: send from Dynamics 365 and write the result back

Dynamics 365 runs on Dataverse, so Power Automate’s Microsoft Dataverse connector covers both directions. This uses two flows: one sends a package when a record is ready, the other updates the record and attaches the signed PDF when the package completes. The examples use the Opportunities table; any table works the same way.
1

Send when a record is ready

Start a flow with the Dataverse trigger When a row is added, modified or deleted. Set Change type to Modified, Table name to Opportunities, and use Select columns and Filter rows so it only fires when the record reaches the stage you sign at.Add an HTTP action that calls Create a package from a template, filling recipients and fields from the row’s columns. Set externalId to the row’s id, for example @{triggerOutputs()?['body/opportunityid']}. That ties the package to the record and makes retries safe.
2

Look up the record when the package completes

In a second flow, set up the When an HTTP request is received trigger as in Receiving events and subscribe the Flowsign endpoint to Package completed.The event carries the packageId but not the externalId. Add an HTTP action named Get package that calls GET https://my.flowsign.app/api/v1/packages/@{triggerBody()?['data']?['packageId']} with your Authorization header. The record’s id is then @{body('Get_package')?['data']?['externalId']}.
3

Update the record

Add the Dataverse Update a row action with Table name Opportunities and Row ID set to the externalId above, and set whichever columns record the signed status or date.
4

Attach the signed PDF

Add an HTTP action named Download PDF that calls /download?certificate=true as in the SharePoint recipe. Then add the Dataverse Add a new row action on the Notes table:The note appears in the record’s timeline with the PDF attached.
Things to know:
  • Attachment size. Dataverse limits note attachments to 5 MB by default. An administrator can raise it in the environment’s email settings, or the second flow can save the PDF to SharePoint instead and link it from the record.
  • Which user sends. To send as the Dynamics user who owns the record, use a key that acts for members and pass their email in X-Act-As. See Calling the API.
  • Other statuses. The same pattern handles Package declined and Package voided: subscribe the endpoint to them and branch on x-flowsign-event.

Plan and cost notes

The Flowsign API and webhooks are included in the Enterprise plan. Creating a webhook endpoint needs the manage webhooks permission. Microsoft lists both the HTTP action and the When an HTTP request is received trigger as premium, so a flow using either needs a Power Automate plan that includes premium connectors, not just a Microsoft 365 seat. Check Microsoft’s current licensing before you build.