App Logo
docs.google.com

Google Docs: request eSignatures on a document

Automatically request eSignatures on a document on docs.google.com. Send a Google Doc out for eSignature: Google makes a PDF copy and emails each signer a link to sign it. Signers are given in the order of the document's signer roles (Signer one, Signer two, ...). When the document has no fields yet, it adds one signer role per email (up to 10) and one Signature field per signer at the end of the document. Returns the PDF's link, which sign_document, get_signature_request and cancel_signature_request take. 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 check the request without sending it. Needs edit access and a Google account that has eSignature (most Workspace plans and Google One Premium). When the browser is signed in to several Google accounts, pass the account to act as.

Input

url required

Link to the Google Doc (https://docs.google.com/document/d/<id>/...) or the bare document id.

signers required

Signer emails, one per signer role, in order: the first is Signer one, and so on. When the document has fields already, the count must match its signer roles; when it has none, one role and one Signature field per email are added.

dryRun optional

True fills in the request and reads it back, then cancels: nothing is added to the document and nothing is sent. 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. It does not appear in the signed document.

reminders optional

Send automatic reminders to signers who have not signed.

Default: false
documentName optional

Name of the PDF to sign. Google's default is the document title 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

id required
sent required

True when the request was sent.

pdfUrl required

Link to the PDF sent for signature; null in a dry run.

signers required
fieldAdded required

True when a Signature field was added at the end of the document (or, in a dry run, would be).

accountUsed required
signerRoles required

The signer roles the document has fields for, as Google names them.

pdfId optional

FAQ

Send a Google Doc out for eSignature: Google makes a PDF copy and emails each signer a link to sign it. Signers are given in the order of the document's signer roles (Signer one, Signer two, ...). When the document has no fields yet, it adds one signer role per email (up to 10) and one Signature field per signer at the end of the document. Returns the PDF's link, which sign_document, get_signature_request and cancel_signature_request take. 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 check the request without sending it. Needs edit access and a Google account that has eSignature (most Workspace plans and Google One Premium). 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/docs.google.com/request_signatures, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/docs.google.com/request_signatures
You do not need one. "Google Docs: request eSignatures on a document" drives the real docs.google.com pages in a browser, so it works whether or not docs.google.com offers an API for this.
Required: url, signers. Optional: dryRun, account, message, reminders, documentName, allowExternal.
It returns id, sent, pdfId, pdfUrl, signers, fieldAdded, accountUsed, signerRoles.
Yes. It acts as you on docs.google.com: on your own Chrome it reuses your session, and on a Reduck-hosted browser it loads the docs.google.com cookies saved by the Reduck extension.
It makes changes on docs.google.com, like sending, posting, booking or buying something.
Ask an AI agent connected to Reduck to run reduck/docs.google.com/request_signatures, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/docs.google.com/request_signatures
It is part of Reduck's official curated catalogue.

Related scripts

docs.google.com

Create a Google Sheets spreadsheet

Create a new Google Spreadsheet in My Drive, optionally with a title. Returns spreadsheetId, url, and firstGid (always 0). The file lands in Drive root (My Drive); moving it elsewhere is a Drive action, not a Sheets one.

docs.google.com

Sheets: write cells

Write a 2D block of values into one tab of a Google Spreadsheet, top-left at startCell, like the Sheets API: null leaves a cell as it is, "" clears it, anything else replaces it as if typed (dropdown rules and formatting stay; clearing a dropdown cell removes its dropdown). Returns range, rows, cols, saved once every edit is saved. A value the sheet refuses (data validation, outside the grid) stops the run with the sheet's own message. Values are parsed per the spreadsheet locale ("1.5" in a FR sheet becomes 1 May; prefix ' to force text); leading = enters a formula; needs edit rights.

docs.google.com

Sheets: add tab

Add a tab to a Google Spreadsheet, optionally naming it in the same pass. Returns the new tab's gid and final name. Waits for the editor's save before resolving; needs edit rights.

Start building not clicking

Get started for free