App Logo
drive.google.com

Google Drive: request eSignatures on a PDF

Automatically request eSignatures on a PDF on drive.google.com. Send a PDF stored in Google Drive out for eSignature: places each field you give (signature, initials, name, text or date) on its page and position for its signer, then Google makes a copy of the PDF and emails each signer a link to sign it. Positions are fractions of the page width and height from the top-left corner, as get_signature_request returns them. Signers are numbered in the order given (signer 1 is the first email); up to 10. Returns the copy's link, which sign_document signs (send it to yourself to sign your own PDF). Google asks to confirm before sharing with signers outside the sender's organisation: pass allowExternal only when the user agrees, otherwise nothing is sent. Use dryRun to place the fields and fill the request without sending it. Needs a Google account that has eSignature. When the browser is signed in to several Google accounts, pass the account to act as.

Input

url required

Link to the PDF in Google Drive (https://drive.google.com/file/d/<id>/...) or the bare file id.

fields required

Fields to place. Every signer needs at least one signature field.

signers required

Signer emails; the first is signer 1, and so on.

dryRun optional

True places the fields and fills the request, then cancels: nothing is sent and the PDF is unchanged. Pass false to send.

Default: true
account optional

Google account to act as when the browser is signed in to several.

message optional

Message in the email to signers.

reminders optional

Send automatic reminders to signers who have not signed.

Default: false
documentName optional

Name of the copy to sign. Google's default is the PDF's name with the date and time.

allowExternal optional

True when the user agrees to share the PDF with signers outside the sender's organisation, which Google asks to confirm. Without it, such a request stops and nothing is sent.

Default: false

Output

sent required
fields required

The fields as Google received them (in a dry run, as placed).

fileId required

The PDF the request was made from.

signers required
pdfId optional

The copy to sign; pass it to sign_document. Null in a dry run.

pdfUrl optional
accountUsed optional

FAQ

Send a PDF stored in Google Drive out for eSignature: places each field you give (signature, initials, name, text or date) on its page and position for its signer, then Google makes a copy of the PDF and emails each signer a link to sign it. Positions are fractions of the page width and height from the top-left corner, as get_signature_request returns them. Signers are numbered in the order given (signer 1 is the first email); up to 10. Returns the copy's link, which sign_document signs (send it to yourself to sign your own PDF). Google asks to confirm before sharing with signers outside the sender's organisation: pass allowExternal only when the user agrees, otherwise nothing is sent. Use dryRun to place the fields and fill the request without sending it. Needs a Google account that has eSignature. When the browser is signed in to several Google accounts, pass the account to act as.
Ask an AI agent connected to Reduck to run reduck/drive.google.com/request_pdf_signatures, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/drive.google.com/request_pdf_signatures
You do not need one. "Google Drive: request eSignatures on a PDF" drives the real drive.google.com pages in a browser, so it works whether or not drive.google.com offers an API for this.
Required: url, signers, fields. Optional: dryRun, account, message, reminders, documentName, allowExternal.
It returns sent, pdfId, fields, fileId, pdfUrl, signers, accountUsed.
Yes. It acts as you on drive.google.com: on your own Chrome it reuses your session, and on a Reduck-hosted browser it loads the drive.google.com cookies saved by the Reduck extension.
It makes changes on drive.google.com, like sending, posting, booking or buying something.
Ask an AI agent connected to Reduck to run reduck/drive.google.com/request_pdf_signatures, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/drive.google.com/request_pdf_signatures
It is part of Reduck's official curated catalogue.

Related scripts

drive.google.com

Move a Google Drive file to the Bin

Moves a file to Drive's Bin (never a permanent delete), given just the file's id — its parent folder is resolved automatically.

drive.google.com

Upload a file to Google Drive

Upload one file into a Google Drive folder, or into My Drive when no folder is given, and return the stored file's id, name and link. Pass filename to choose the name it is stored under. When the folder already holds a file with that name, ifExists decides: fail (the default) uploads nothing, keepBoth adds a second file with a numbered name, replace adds a new version of the existing file and keeps its id.

drive.google.com

List a Google Drive folder

List the files and sub-folders directly inside a Google Drive folder, without recursing or downloading anything. Returns each item's id, name, type, size, dates, owner and link, folders first, one page at a time: pass nextPageToken back as pageToken to read the next page. Omit folderId to list My Drive's root. An empty folder returns empty lists.

Start building not clicking

Get started for free