Skip to main content
You can automate Flowsign with Make using its own Custom webhook and HTTP modules: trigger a scenario when a package completes, or create and send a package from another system through a scenario.

Receiving events

Create a webhook endpoint in Flowsign at Settings > Webhooks (my.flowsign.app/settings/webhooks), or with the API (see Webhooks).
  1. In your scenario, add the Webhooks app’s Custom webhook module and create a new webhook.
  2. Make gives you a webhook URL. Paste it 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 scenario acts on any unauthenticated POST to its webhook 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). Make’s Custom webhook module hands the scenario the parsed body, and re-serialising it isn’t guaranteed to reproduce the bytes Flowsign signed (whitespace and key order can differ), so a Make filter can’t verify the signature reliably. Two practical options:
  • Keep the webhook URL secret. Make generates it for this scenario only. Don’t share it, and if it leaks, create a new webhook in Make and update the endpoint’s Endpoint URL in Flowsign.
  • Verify before Make. Point the Flowsign endpoint at a small HTTP endpoint you control (an Azure Function, AWS Lambda or Cloudflare Worker) that checks the signature and timestamp against the raw body, then forwards only valid deliveries to the Make webhook URL.

Calling the API

Use the HTTP app’s Make a request module 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.

List packages

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

Create a package from a template

Method POST, URL https://my.flowsign.app/api/v1/packages/from-template, body type Raw (JSON):
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 scenario files every completed package as a PDF in a SharePoint document library or a Google Drive folder. It has three modules: catch the event, download the PDF from Flowsign, and hand it to the storage app.
1

Catch the completed event

Set up the Custom webhook module 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 scenario can download straight away.
2

Download the signed PDF

Add the HTTP app’s Get a file module, which keeps the response as a file the next module can use: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 app’s Upload a File module.
Use the Microsoft SharePoint Online app. Choose the site, the document library and the folder, then map:
Send a test from the endpoint’s Send test event button so Make learns the event’s shape and the data fields become mappable. The test event’s packageId is pkg_test, which has no file, so the download module 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(1.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 {{1.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.

Plan and cost notes

The Flowsign API and webhooks are included in the Enterprise plan. Creating a webhook endpoint needs the manage webhooks permission. The Custom webhook and HTTP modules used here are part of Make’s free core apps, with no premium gate.