Siggy + Microsoft Power Automate

Everything DocuSign's connector does for your signing workflow, with Siggy: send documents for signature from any flow, and trigger flows the moment an envelope is signed — for example, saving the sealed PDF back into SharePoint.

You need: a Siggy Business (or Unlimited) plan for API access, and a Power Automate Premium licence (custom connectors and the HTTP actions are premium features — the same licence the DocuSign connector's advanced use needs).

1. One-time setup: your API key

Create a Siggy API key

In Siggy, open Security → API keys and click New key. Copy the sk_live_… value — it is shown only once.

Keep it in the form Power Automate will send

Wherever this guide says API key value, enter the word Bearer, a space, then your key:

Bearer sk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxx

2. Recommended: import the Siggy connector

A custom connector gives you friendly actions (“Send envelope from template”, “Download the sealed PDF”…) instead of hand-building HTTP requests. Siggy ships a ready-made definition.

Download the connector definition

siggy-power-automate.swagger.json (OpenAPI 2.0 — the format Power Automate requires).

Import it

In Power Automate: More → Discover all → Custom connectors → New custom connector → Import an OpenAPI file. Name it Siggy and pick the downloaded file.

Check the security tab

It should show API Key auth with parameter name Authorization in the Header. Click Create connector.

Create a connection

First use of any Siggy action asks for the API key — paste the full Bearer sk_live_… value from step 1.

Test it

In the connector's Test tab, run List templates. A 200 with your templates means you are connected.

Actions you get

Send envelope from template	The workhorse — template + names/emails → sent. No coordinates needed.
Send a document for signature	Send any PDF (base64 file content) with signature fields placed by coordinates.
Get envelope status	Poll or branch on sent / completed / declined.
Download the sealed PDF	The tamper-evident signed document, once completed.
Download the completion certificate	The audit-trail certificate PDF.
List templates / envelopes	Discovery and reporting.
Void / remind	Stop an envelope, or re-email whoever it is waiting on.
Register webhook endpoint	Point Siggy events at a flow trigger (next section).

3. Trigger a flow when an envelope is signed

This is the equivalent of DocuSign's “When an envelope status changes” trigger. Siggy pushes a webhook; Power Automate receives it.

Start a flow with the HTTP trigger

New flow → When an HTTP request is received (premium). Set Who can trigger the flow to Anyone (the URL itself contains an unguessable signature key).

Paste this payload schema

In Use sample payload to generate schema, paste:

{
  "id": "evt_3f2…",
  "type": "envelope.completed",
  "created": 1718000000,
  "data": {
    "envelope": {
      "id": "9a8b…",
      "title": "Engagement letter — Jane Smith",
      "status": "completed",
      "document_id": "d41d…",
      "created_at": "2026-06-12T00:00:00+00:00"
    },
    "recipients": [
      { "id": "r1…", "name": "Jane Smith", "email": "[email protected]",
        "status": "signed", "role": "signer" }
    ]
  }
}

Save the flow and copy its URL

Power Automate generates the HTTP POST URL after you save.

Either in the dashboard (Security → Webhooks) or with the connector's Register webhook endpoint action. Siggy will now POST to the flow on envelope.sent, recipient.signed, envelope.completed and envelope.declined.

Branch on the event type

Add a Condition: type equals envelope.completed — so the flow only continues for fully-signed envelopes. Respond with 200 (Power Automate does this automatically); Siggy retries non-2xx deliveries with backoff.

4. Two ready-made recipes

A. Send an engagement letter when a row is added (Excel/Dataverse/SharePoint)

Trigger: e.g. When a new item is created (SharePoint).
Action: Siggy Send envelope from template — pick the template, map name and email from the trigger outputs.
Optionally store the returned id (envelope ID) back on the list item to correlate the completion webhook later.

B. Save the signed PDF to SharePoint when completed

Trigger: When an HTTP request is received (set up as in section 3).
Condition: type equals envelope.completed.
Action: Siggy Download the sealed PDF — pass triggerBody()?['data']?['envelope']?['id'].
Action: SharePoint Create file — file content = the previous step's body; name it from the envelope title.

5. Alternative: the plain HTTP action

No custom connector? Every Siggy call works with Power Automate's built-in HTTP action. Add a header Authorization = Bearer sk_live_… and Content-Type = application/json.

Send from a template:

POST https://siggy.com.au/api/be/v1/templates/{template_id}/send

{
  "title": "Engagement letter — Jane Smith",
  "recipients": [ { "name": "Jane Smith", "email": "[email protected]" } ]
}

Send any PDF in one call — Power Automate file content is already base64 in expressions, e.g. base64(body('Get_file_content')):

POST https://siggy.com.au/api/be/v1/envelopes

{
  "document_base64": "@{base64(body('Get_file_content'))}",
  "filename": "engagement.pdf",
  "title": "Engagement letter — Jane Smith",
  "recipients": [ { "name": "Jane Smith", "email": "[email protected]" } ],
  "fields": [
    { "recipient_index": 0, "type": "signature", "page": 1,
      "x": 0.62, "y": 0.78, "w": 0.25, "h": 0.06 }
  ]
}

6. Coming from DocuSign?

DocuSign connector	Siggy equivalent
When an envelope status changes (Connect)	Webhook → 'When an HTTP request is received' (section 3)
Create envelope using Template	Send envelope from template
Add documents to an envelope (base64)	Send a document for signature (document_base64)
Get envelope documents	Download the sealed PDF / completion certificate
Get envelope (status)	Get envelope status
Void envelope	Void an envelope
Resend envelope	Send a reminder

Stuck anywhere? Email [email protected] — we'll help you wire up your first flow, free.