Make, Zapier, n8n and other no-code tools

Any tool that can send an HTTP request can make a document. You do not write code: you fill in one "HTTP" or "Webhook" step with the values below. The first run should use "isTest": true, which is free.

No tool at all? A Word document you already wrote can be signed from the console: Flows, Sign a Word document (how).

The five values every tool asks for

{
  "data": { "customer": { "name": "Acme Srl" } },
  "settings": {
    "templateId": "YOUR_TEMPLATE_ID",
    "isTest": true,
    "responseFormat": "json"
  }
}

Why responseFormat: "json": most no-code tools cannot carry raw PDF bytes from one step to the next. With it the answer is text, and the PDF is in output.compose.documentBase64 (base64). Add a "convert base64 to file" step, or fetch output.compose.downloadUrl with the same header. n8n can take the raw file directly: set the node's response format to File and leave responseFormat out.

Make (Integromat)

1. Add the module HTTP → Make a request.
2. URL and method as above. Under Headers add the two headers. Body type: Raw, Content type: JSON (application/json).
3. Paste the body. Put Make's mapped fields (the customer's name from your Google Sheet, for example) inside data.
4. Turn on Parse response. The next module can read output.compose.documentBase64; use a base64 decode step or the file field of the Google Drive or Email module.

Zapier

1. Add the action Webhooks by Zapier → Custom Request.
2. Method: POST. URL, Data (the JSON body) and Headers as above.
3. Zapier shows the answer as fields. Use the download address or the base64 field in the next step.

n8n

1. Add the node HTTP Request. Method POST, the URL above.
2. Authentication: Generic credential → Header Auth, name Authorization, value Bearer YOUR_API_KEY.
3. Send body on, Body content type JSON, Specify body Using JSON, paste the body without responseFormat.
4. Options → Response → Response format: File. The next node receives the PDF as binary data.

Getting told when a signature is done

For a document sent for signature, give the call a callback address. In Make, Zapier or n8n create a Custom webhook trigger, copy its address into the call and every envelope event starts your scenario (callback environments).

When it does not work

The answer always has a code and a message. The usual ones: MISSING_CREDENTIALS (no Authorization header), INVALID_API_KEY (the key was copied with a space, or without Bearer ), INVALID_JSON (the body is not valid JSON: a straight quote turned curly, or a trailing comma), TEMPLATE_NOT_FOUND (check the template id). All the codes.

The same in code: PHP, WordPress, React, Java, C#, Go, Ruby, JavaScript, cURL.