Skip to content

Automation platforms

Send Envelopes From Form Submissions

Turn Typeform, Jotform, Tally and Google Forms submissions into SignatureAPI envelopes through an automation tool's inbound webhook.

A form submission can start a signature: the signer’s name and email come from the answers, and one envelope goes out per submission. Typeform, Jotform and Tally send each submission to a webhook URL. Google Forms does it through an Apps Script trigger. No SignatureAPI app is needed.

How the pieces fit

Each form tool posts its own payload. The payload is the submission, not a SignatureAPI request, so the form’s webhook can’t be pointed at the envelope endpoint. Point it at an inbound webhook in an automation tool instead, and let that tool’s HTTP step send the envelope with your key:

  1. The form sends the submission to the tool’s inbound webhook.
  2. The tool’s HTTP step calls POST https://api.signatureapi.com/v1/envelopes.
  3. SignatureAPI emails the signer. Your key stays in the automation tool, never in the form.

Use the page for your tool: Make, Zapier or n8n.

Connect the form

Form toolHow a submission reaches your URLSource
TypeformWebhook that sends the response data to your URL. Reply 2XX within 30 seconds.Typeform webhooks
JotformSettings, Integrations, Webhooks, then enter the URL. Requests time out after 5 seconds by default.Jotform webhooks
TallyIntegrations tab, Connect next to Webhooks. JSON in a POST, reply 2XX within 10 seconds.Tally webhooks
Google FormsAn installable form submit trigger runs an Apps Script function.Form trigger builder

For Google Forms, the trigger runs a function in Apps Script, and that function calls the API with UrlFetchApp. The Google Apps Script page has the request code. The function gets the submission in e.response (Event objects).

Send the envelope

HTTP request step

Settings for the "Form submission" request.

SettingValue
Method POST
URL https://api.signatureapi.com/v1/envelopes
Header X-API-Key: YOUR_API_KEY

Store the key in your tool's secret or credential storage when it has one.

Header Content-Type: application/json
Body (raw JSON)The JSON below.
Body (raw JSON)
{
  "title": "Service Agreement - Jane Doe",
  "message": "Please review and sign the service agreement.",
  "metadata": {
    "source": "form",
    "response_id": "resp_1042"
  },
  "topics": [
    "no_code",
    "forms"
  ],
  "documents": [
    {
      "key": "service_agreement",
      "url": "https://pub-9cb75390636c4a8a83a6f76da33d7f45.r2.dev/docs-samples/service-agreement.pdf",
      "format": "pdf",
      "fixed_positions": [
        {
          "place_key": "signer_signature",
          "page": 1,
          "top": 172,
          "left": 210
        }
      ],
      "places": [
        {
          "key": "signer_signature",
          "type": "signature",
          "recipient_key": "signer"
        }
      ]
    }
  ],
  "recipients": [
    {
      "type": "signer",
      "key": "signer",
      "name": "Jane Doe",
      "email": "jane.doe@example.com"
    }
  ]
}

Map the form answers into the body:

  • recipients[0].name and recipients[0].email come from the name and email answers. In a Typeform payload, an email answer has type email and an email key, and you match it to its question with field.id (example payload). In a Tally payload, answers are in a fields array with a key, label, type and value (Tally webhooks).
  • metadata.response_id carries the submission id, so the envelope links back to the response. Typeform’s form_response.token is the submission id.
  • The forms topic groups these envelopes, so a webhook endpoint can receive only them.

To put the answers into the document, send a DOCX with a data object, and the {{ field }} values are merged in. See Templates. Keep sensitive answers out of metadata: it appears in every webhook event.

Get the result back

Register an automation-tool URL as a webhook endpoint in test mode, subscribed to envelope.completed with the forms topic. Anyone who knows that URL can call it, so read the envelope with your key before you act:

HTTP request step

Settings for the "Completed envelope" request.

SettingValue
Method GET
URL https://api.signatureapi.com/v1/envelopes/eb4cf433-a8af-4161-b37b-7ef57d423e56
Header X-API-Key: YOUR_API_KEY

Store the key in your tool's secret or credential storage when it has one.

Then write the result back to your own records, using metadata.response_id to find the submission. SignatureAPI retries a failed delivery for up to 48 hours, and the same event can arrive twice. See Webhooks.