Make - FlowSign

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).

In your scenario, add the Webhooks app’s Custom webhook module and create a new webhook.
Make gives you a webhook URL. Paste it into the endpoint’s 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.

Every delivery is a POST with three headers and a JSON body:

Header	Value
`X-FlowSign-Event`	The event name, for example `PACKAGE_COMPLETED`
`X-FlowSign-Delivery-Id`	A stable id for this delivery; retries reuse it
`X-FlowSign-Signature`	Hex-encoded HMAC-SHA256 of the raw body, keyed with the endpoint secret

{
  "event": "PACKAGE_COMPLETED",
  "timestamp": "2026-09-17T03:40:11.000Z",
  "data": {
    "packageId": "pkg_9f3c2e",
    "packageTitle": "Employment agreement: Ana Reid",
    "completedAt": "2026-09-17T03:40:10.884Z"
  }
}

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.

Compute a hex HMAC-SHA256 of the raw body with the endpoint secret and compare it to X-FlowSign-Signature. Make’s built-in sha256 function returns an HMAC when called with a key argument: sha256(text; encoding; key). Add a Filter on the route straight after the Custom webhook module, with this condition:

sha256(1.body; "hex"; "your_endpoint_secret") = {{1.headers.x-flowsign-signature}}

1.body is the module’s raw body output and 1.headers its headers, keyed lower-case. Keep the filter’s label something like “Signature valid” so a failed check is obvious in the scenario’s run history, and hold the secret in a Make Data Store or connection rather than typing it into the filter directly.

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:

Header	Value
`Authorization`	`Bearer fsk_your_key_here`
`X-Workspace-Id`	Optional; the workspace to act in. Omit to use the organisation’s default workspace.

Create the key at Settings > API keys; see Authentication.

List packages

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

{
  "data": {
    "packages": [
      {
        "id": "pkg_9f3c2e",
        "title": "Employment agreement: Ana Reid",
        "status": "IN_PROGRESS",
        "description": null,
        "recipients": [
          { "name": "Ana Reid", "email": "[email protected]", "action": "Sign", "actionType": "SIGNER", "signed": false }
        ],
        "documentsCount": 1,
        "signingProgress": { "completed": 0, "total": 1 },
        "createdAt": "2026-09-17T01:12:44.000Z",
        "updatedAt": "2026-09-17T01:12:50.000Z",
        "expiresAt": null,
        "completedAt": null
      }
    ],
    "totalCount": 1,
    "page": 1,
    "pageSize": 25
  }
}

Create a package from a template

Method POST, URL https://my.flowsign.app/api/v1/packages/from-template, body type Raw (JSON):

{
  "templateId": "tmpl_abc123",
  "recipients": [
    { "role": "Employee", "name": "Ana Reid", "email": "[email protected]" },
    { "role": "Manager", "name": "Ben Toa", "email": "[email protected]" }
  ],
  "fields": { "start_date": "1 October 2026" },
  "externalId": "order_4471",
  "status": "sent"
}

role must match one of the template’s role names and fields keys must match its merge field keys; 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.

{ "data": { "packageId": "pkg_9f3c2e", "externalId": "order_4471", "status": "IN_PROGRESS" } }

Creating requires the key’s user to have the send permission; see Errors for the full status code list.

Plan and cost notes

The Custom webhook and HTTP modules used here are part of Make’s free core apps, with no premium gate.

​Receiving events

​Verifying the signature

​Calling the API

​List packages

​Create a package from a template

​Plan and cost notes

Receiving events

Verifying the signature

Calling the API

List packages

Create a package from a template

Plan and cost notes