App integration · All integrations

Send Signed PDFs to Google Drive — Without DocuSign

DocuSign charges per envelope and bundles features most small teams never use. The real need is simpler: collect a signature, generate a tamper-evident PDF, and park the file in a Google Drive folder the rest of the team can already access. Instead, teams end up managing a second document system, reconciling DocuSign folders with Drive manually, and paying for a seat-based plan when all they wanted was a signed PDF in a shared folder.

Formfy collects signatures, generates a signed PDF, and fires a webhook the moment a client signs. Your automation catches the event, pulls the PDF via the Formfy API, and stores it in Google Drive automatically — no DocuSign seat required.

Start a 15-day free trial Read the OpenAPI spec

The workflow at a glance

Trigger

A client signs a Formfy consent, intake, or waiver form

Action

Formfy fires a form.signed webhook and exposes the signed PDF via REST API

Result

Your script downloads the PDF and places it in the correct Google Drive folder

Step-by-step: connect Google Drive to Formfy

Wire Formfy webhook subscriptions to a lightweight handler that downloads the signed PDF and uploads it to Google Drive automatically.

  1. Generate a Formfy API key

    Open the Formfy dashboard, navigate to Settings → API Keys, and click Create key. Save the fk_live_… token immediately — Formfy shows it once. Use fk_test_… during development so test signatures do not count against your live quota.

  2. List or create the form to send

    Call GET /api/v1/forms to retrieve every form on your account, or POST /api/v1/forms to build a new consent, waiver, or intake form. Note the form id — you will reference it when constructing the signed-PDF download URL after a signature lands.

    GET/api/v1/formsSee in the OpenAPI spec →

  3. Subscribe to the form.signed event

    POST /api/v1/webhooks with your webhook receiver URL and event_types set to form.signed. Formfy returns a signing secret — store it in environment variables. Each delivery carries an X-Formfy-Signature header computed with HMAC-SHA256 so your handler can verify the payload before writing to Drive.

    POST/api/v1/webhooksSee in the OpenAPI spec →

  4. Download the signed PDF

    When your handler receives the form.signed payload, extract the form id and call GET /api/v1/forms/{id}/signed-pdf. Formfy returns a short-lived download token. Follow the redirect or call GET /api/v1/files/pdf/{token} to stream the binary PDF and pipe it into your Drive upload.

    GET/api/v1/forms/{id}/signed-pdfSee in the OpenAPI spec →

  5. Upload the PDF to Google Drive and verify

    Pass the binary stream to the Google Drive Files API and target the folder your team already uses. Name the file using the signer email and signed_at timestamp from the webhook payload so filenames stay sortable and every signed document is traceable.

Subscribe to form.signed and download the signed PDF

Create a Formfy webhook subscription for the form.signed event, then download the resulting PDF for upload to Google Drive.

# 1. Subscribe to form.signed
curl -X POST https://formfy.ai/api/v1/webhooks \
  -H "Authorization: Bearer fk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "target_url": "https://your-server.example.com/webhooks/formfy",
    "event_types": ["form.signed"]
  }'

# 2. After the webhook fires, download the signed PDF
curl -L "https://formfy.ai/api/v1/forms/FORM_ID/signed-pdf" \
  -H "Authorization: Bearer fk_live_YOUR_KEY" \
  -o signed-document.pdf

Frequently asked questions

Is Formfy a direct DocuSign replacement for Google Drive workflows?

For teams whose primary need is collecting e-signatures and storing signed PDFs in Google Drive, yes. Formfy provides a public REST API, webhook events, and a signed-PDF download endpoint. You route the PDF to Drive via a short script or automation tool, skip per-envelope pricing, and avoid the overhead of managing a second document platform.

What Google Drive API scopes does my script need?

Your service account or OAuth token needs the drive.file scope to create and manage files your app generates, or the drive scope for full account access. For most workflows, drive.file is sufficient — your script creates the PDF, names it from the Formfy payload, and stores it in a designated folder. No broader Drive access is required.

Does Formfy store signed PDFs, or must I download them immediately?

Formfy stores the signed PDF and makes it available via GET /api/v1/forms/{id}/signed-pdf for a retention window on your plan. The endpoint returns a short-lived download token rather than a permanent public URL — download and archive to Drive as soon as the form.signed webhook fires rather than relying on long-term Formfy storage.

How does Formfy pricing compare to DocuSign per-envelope fees?

Formfy bills on a subscription basis rather than per envelope. For teams sending many forms — clinic intake, agency onboarding, property waivers — a flat subscription is significantly cheaper than DocuSign per-envelope pricing at volume. See formfy.ai/pricing for current plan limits. Competitor pricing changes frequently; verify details directly on their site.

Can Formfy send forms by SMS as well as email?

Yes. The POST /api/v1/forms/{id}/send endpoint accepts a phone number parameter and delivers the signing link via SMS. This is useful for field-service waivers, clinic intake flows, and any workflow where the signer is on a mobile device rather than a desktop. SMS delivery and email delivery are both available on paid plans.

How do I verify the webhook payload before uploading to Drive?

Formfy signs every delivery with HMAC-SHA256 and includes the digest in the X-Formfy-Signature header. In your handler, recompute HMAC-SHA256 over the raw request body using your signing secret and compare it to the header value. Reject any request where the signatures differ — this prevents a bad actor from spoofing a form.signed event and injecting arbitrary files into your Drive folder.

What happens if my server misses a form.signed webhook delivery?

Formfy retries failed deliveries with exponential backoff for up to 24 hours. You can inspect every delivery attempt in the Formfy dashboard Webhook Deliveries log and replay any individual payload manually. As a fallback, poll GET /api/v1/forms/{id}/signed-pdf directly if your server was down during a critical signing window.

Can I use Google Apps Script instead of a custom server to receive webhooks?

Yes. Deploy a Google Apps Script Web App as the webhook target_url. The doPost handler receives the Formfy payload, verifies the HMAC signature, fetches the signed PDF via UrlFetchApp, and uploads it to Drive with DriveApp.createFile. The Apps Script URL is publicly accessible and requires no dedicated server or hosting plan.

Ready to wire Google Drive into Formfy?

Spin up an API key, run your first webhook, and route signed forms wherever your team already works.

Start a 15-day free trialSee pricing