Receiving events
Create a webhook endpoint in Flowsign at Settings > Webhooks (my.flowsign.app/settings/webhooks), or with the API (see Webhooks).- In your Zap, add Webhooks by Zapier as the trigger app and choose the Catch Hook event.
- Zapier gives you a catch URL. Paste it into the endpoint’s Endpoint URL field in Flowsign.
- Tick the events to subscribe to (for example Package completed) and save. Flowsign shows the endpoint’s signing secret once; store it.
POST with four headers and a JSON body:
data differs per event. See Events for every event’s shape.
Verifying the signature
Build the signed content from thex-flowsign-timestamp header, a ., and the raw body. Compute its hex HMAC-SHA256 with the endpoint secret and accept the delivery when it matches any v1= entry in x-flowsign-signature and the timestamp is within 5 minutes of your clock (see Webhooks). The Catch Hook event parses the body into fields before your Zap sees it, so re-serialising those fields to JSON isn’t guaranteed to match the exact bytes Flowsign signed (whitespace and key order can differ). For verification that has to match byte-for-byte, use the Catch Raw Hook event instead, which passes the unparsed body and headers through.
Add a Code by Zapier step (JavaScript) after the trigger:
inputData.rawBody, inputData.timestamp and inputData.signature from the raw hook’s body and its x-flowsign-timestamp and x-flowsign-signature headers, and inputData.secret from a Zapier storage value or environment-style input holding the endpoint secret. Follow with a Filter by Zapier step that only continues when valid is true.
Calling the API
Use Webhooks by Zapier’s Custom Request 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.
List packages
Method GET, URLhttps://my.flowsign.app/api/v1/packages?status=IN_PROGRESS.
Create a package from a template
Method POST, URLhttps://my.flowsign.app/api/v1/packages/from-template, with a JSON 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.
Recipe: save signed PDFs to SharePoint or Google Drive
This Zap files a completed package’s signed PDF in a SharePoint document library or a Google Drive folder. Zapier’s upload actions take a file from a link, and they fetch that link without your API key. So instead of downloading the PDF, the Zap asks Flowsign for a short-lived download link and hands the link to the storage app. That takes four steps.1
Catch the completed event
Set up the Catch Hook 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 Zap can fetch them straight away.
2
Find the package's documents
Add a Webhooks by Zapier Custom Request action:
The response lists the package’s documents under
data.documents, each with an id and a title.3
Get the download link
Add a second Custom Request action:
The response’s
data.downloadUrl is a link to the signed copy, valid for one hour.4
Save the file
Add the storage app’s Upload File action.
- Google Drive
packageId is pkg_test, which is not a real package, so the second step returns 404 until a real package completes. Test the later steps with a real completed package.
Things to know:
- One file per document. The link is for a single document, so this Zap saves each document separately, without the certificate of completion. The merged PDF and the certificate come back as file data rather than a link, which Zapier’s upload actions cannot take from a Custom Request step.
- Packages with several documents. The second step returns every document id. Add Looping by Zapier between the second and third steps to repeat the last two steps for each one.
- File names. Naming the file by package id or document id is always safe. Titles can contain characters SharePoint refuses (
" * : < > ? / \ |); clean them with a Formatter by Zapier step first. - Filing by custom field.
data.metadataon the event carries the package’s custom field values, so a value such as Data Metadata Client Code can pick the folder. - Permissions. The key must be able to see the package and act in the workspace it belongs to.

