---
title: "Send Envelopes From Form Submissions"
description: "Turn Typeform, Jotform, Tally and Google Forms submissions into SignatureAPI envelopes through an automation tool's inbound webhook."
canonical: "https://signatureapi.com/docs/integrations/forms-to-envelope"
source: "https://signatureapi.com/docs/integrations/forms-to-envelope.md"
last_verified_api_version: "1.18.0"
---

# Send Envelopes From Form Submissions

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

_Last verified against API version 1.18.0._

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](https://signatureapi.com/docs/integrations/make), [Zapier](https://signatureapi.com/docs/integrations/zapier/http-recipe) or [n8n](https://signatureapi.com/docs/integrations/n8n).

## Connect the form

| Form tool    | How a submission reaches your URL                                                                               | Source                                                                                                  |
| ------------ | --------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Typeform     | Webhook that sends the response data to your URL. Reply `2XX` within 30 seconds.                                | [Typeform webhooks](https://www.typeform.com/developers/webhooks/)                                      |
| Jotform      | **Settings**, **Integrations**, **Webhooks**, then enter the URL. Requests time out after 5 seconds by default. | [Jotform webhooks](https://www.jotform.com/help/245-how-to-setup-webhooks-with-jotform/)                |
| Tally        | **Integrations** tab, **Connect** next to **Webhooks**. JSON in a `POST`, reply `2XX` within 10 seconds.        | [Tally webhooks](https://tally.so/help/webhooks)                                                        |
| Google Forms | An installable form submit trigger runs an Apps Script function.                                                | [Form trigger builder](https://developers.google.com/apps-script/reference/script/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](https://signatureapi.com/docs/integrations/google-apps-script) page has the request code. The function gets the submission in `e.response` ([Event objects](https://developers.google.com/apps-script/guides/triggers/events)).

## Send the envelope

HTTP request step settings for the "Form submission" request:

1. **Method**: POST
2. **URL**: `https://api.signatureapi.com/v1/envelopes`
3. **Header**: `X-API-Key: YOUR_API_KEY`

   Store the key in your tool's secret or credential storage when it has one.
4. **Header**: `Content-Type: application/json`
5. **Body (raw JSON)**:

   ```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](https://www.typeform.com/developers/webhooks/example-payload/)). In a Tally payload, answers are in a `fields` array with a key, label, type and value ([Tally webhooks](https://tally.so/help/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](https://signatureapi.com/docs/api/resources/documents/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](https://signatureapi.com/docs/api/guides/how-to/set-up-webhooks) in test mode, subscribed to [`envelope.completed`](https://signatureapi.com/docs/api/resources/events/envelope-events) 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:

1. **Method**: GET
2. **URL**: `https://api.signatureapi.com/v1/envelopes/eb4cf433-a8af-4161-b37b-7ef57d423e56`
3. **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](https://signatureapi.com/docs/api/webhooks).

## Related

- [Make](https://signatureapi.com/docs/integrations/make) and [Zapier](https://signatureapi.com/docs/integrations/zapier/http-recipe): the HTTP step for the envelope.
- [Google Apps Script](https://signatureapi.com/docs/integrations/google-apps-script).
- [Templates](https://signatureapi.com/docs/api/resources/documents/templates).

### Example: Form submission

One envelope per form submission.

```http
POST /v1/envelopes HTTP/1.1
Host: api.signatureapi.com
X-API-Key: YOUR_API_KEY
Content-Type: application/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"
    }
  ]
}
```

Response 201 Created:

```json
{
  "id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
  "title": "Service Agreement - Jane Doe",
  "label": null,
  "message": "Please review and sign the service agreement.",
  "status": "processing",
  "attestation": "none",
  "language": "en",
  "mode": "test",
  "routing": "sequential",
  "timezone": "UTC",
  "timestamp_format": "MM/DD/YYYY HH:mm:ss",
  "snapshot_url": null,
  "branding": {
    "logo": null,
    "accent_color": "#2463EB",
    "email": {
      "footer": null,
      "logo_position": "left",
      "from": "noreply@signatureapi.com"
    }
  },
  "deliverable": {
    "id": "del_6FF89lKNyTNamOJCJd1tLL",
    "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
    "name": null,
    "status": "pending",
    "type": "standard",
    "url": null,
    "password": null,
    "created_at": "2026-11-02T14:03:11.000Z",
    "generated_at": null,
    "timezone": "UTC",
    "language": "en",
    "timestamp_format": "MM/DD/YYYY HH:mm:ss",
    "included_documents": [
      "service_agreement"
    ]
  },
  "metadata": {
    "source": "form",
    "response_id": "resp_1042"
  },
  "sender": {
    "name": "Acme Corp Legal",
    "email": "legal@acme.example",
    "organization": "Acme Corp"
  },
  "captures": {},
  "documents": [
    {
      "id": "doc_HVl3Nj7XzTzX7jN3lVH5vn",
      "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
      "key": "service_agreement",
      "title": null,
      "page_count": 1,
      "url": "https://pub-9cb75390636c4a8a83a6f76da33d7f45.r2.dev/docs-samples/service-agreement.pdf",
      "format": "pdf",
      "fixed_positions": [
        {
          "page": 1,
          "top": 172,
          "left": 210,
          "place_key": "signer_signature"
        }
      ],
      "places": [
        {
          "key": "signer_signature",
          "type": "signature",
          "recipient_key": "signer",
          "height": 60
        }
      ]
    }
  ],
  "recipients": [
    {
      "id": "re_49r1R2jpPDz8hSpP75ZkPp",
      "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
      "type": "signer",
      "key": "signer",
      "email": "jane.doe@example.com",
      "name": "Jane Doe",
      "ceremony": {
        "authentication": [
          {
            "type": "email_link",
            "subject_override": null,
            "message_override": null
          }
        ],
        "embeddable_in": [],
        "redirect_url": null,
        "redirect_delay": 3,
        "url": null,
        "url_variant": "standard"
      },
      "ceremony_creation": "automatic",
      "delivery_type": "email",
      "signature_options": [
        "typed",
        "drawn"
      ],
      "status": "pending",
      "status_updated_at": "2026-11-02T14:03:11.000Z",
      "completed_at": null
    }
  ],
  "topics": [
    "no_code",
    "forms"
  ],
  "created_at": "2026-11-02T14:03:11.000Z",
  "completed_at": null
}
```

Response 422 Unprocessable Content:

```json
{
  "type": "https://signatureapi.com/docs/v1/errors/validation-error",
  "title": "Validation Error",
  "status": 422,
  "errors": [
    "recipients[0].email must be a valid email address."
  ]
}
```

Errors that any request can return (authentication, rate limits, server errors) are on the [Errors](https://signatureapi.com/docs/api/errors) and [Authentication](https://signatureapi.com/docs/api/authentication) pages.
