App Logo
Productivity Reduck MCP

Google Docs eSignature API: Automate Signature Requests Programmatically, No Public API Needed (2026)

Prompt template

Write an NDA between my company and other party in a new Google Doc, with a 'Signature: ____' line for each signer, then send it for eSignature to signer names and emails. Show me the document and the signers before you send it.

Overview

Reduck sends your Google Docs for eSignature from Claude or ChatGPT, with no API, and tracks who signed.

Founders, freelancers, recruiters and operations teams send the same documents for signature again and again: an NDA before a call, a contractor agreement, an offer letter. Many of them already pay for Google Workspace, which has eSignature built into Google Docs and Drive. What they want is one request to their AI agent, such as "Write an NDA with Acme and send it to Jane and Tom for signature", and the signature emails in Jane's and Tom's inboxes, without opening Google Docs.

Why there is no public Google Docs eSignature API (Apps Script, Zapier, Make)

  • Google eSignature has no public API. Google's help pages describe how to request a signature in the Docs and Drive interface (Tools, then eSignature), and mention no API. A public feature request on Google's Issue Tracker, under Google Workspace Developers and Docs API, asks Google to "provide a public API to programmatically trigger Google Docs eSignature requests" (issue 477131486). On the Make Community (December 2024) and the Zapier Community (April 2026), users asked how to send a Google eSignature request from an automation, and the answer was that it is not possible.
  • Apps Script stops before the signature. Apps Script can create the document and fill in the names, but it has no method to send the eSignature request. The last step stays a click in Google Docs.
  • The assistants stop there too. On November 17, 2026, we asked Claude and ChatGPT "how do i automate google docs esignature requests". Both answered that Google eSignature has no public API, that the last click stays manual, and pointed to DocuSign or another e-signature service.
  • The usual workaround is a second e-signature service. DocuSign, Dropbox Sign, BoldSign and signNow have an API or an MCP connector. You then pay for a second service and the document leaves Google, although your Workspace plan already includes eSignature.

How to automate Google Docs eSignature requests with Reduck

Your AI agent runs Reduck's Google Docs and Drive scripts in your own Chrome, where you are already signed in to Google. There is no API key, no Google Cloud project and no other e-signature service: the request is Google's own eSignature, sent from your own account.

  1. It writes the document. create_document creates a Google Doc with a title and the text. append_text adds text at the end, and replace_text fills in a template, for example a name or a date.
  2. It sends it for eSignature. request_signatures sends the Google Doc to up to 10 signers. Google makes a PDF copy and emails each signer a link to sign. If the document has no eSignature fields yet, the script adds one Signature field per signer, named after the signer: on the document's own signature lines when you give their text (signatureLine), else at the end of the document under each signer's name. If you prepared a template with fields in Google Docs, it uses them.
  3. It sends a PDF with fields where you want them. request_pdf_signatures takes a PDF in Google Drive and places each field (signature, initials, name, text or date) on its page and position for its signer.
  4. It tells you who has signed. list_signature_requests lists the requests you sent or the ones waiting for you. get_signature_request reads one request: each signer and whether they have signed.
  5. It signs, rejects or cancels. sign_document signs a request sent to you. reject_signature_request declines one. cancel_signature_request cancels one you sent.

Each send is a dry run by default: the script fills in the request, reads it back and cancels, so your agent can show you the document and the signers before anything goes out. Google asks you to confirm before it shares with signers outside your organisation, and the script sends to them only when you agree.

What you get: one request to your agent, and the document in each signer's inbox with Google's own signing link, then a signed PDF with Google's audit trail page in your Drive when everyone has signed.

Automate signature requests from Claude or ChatGPT: how to start

  1. Create a free account at reduck.ai.
  2. Install the Reduck extension in Chrome and pair it.
  3. Connect Reduck to your agent: docs.reduck.ai.
  4. Ask: "Write an NDA between {my company} and {other party} in a new Google Doc, with a 'Signature: ____' line for each signer, then send it for eSignature to {signer names and emails}. Show me the document and the signers before you send it."

Before the first request:

  • Check that your Google account has eSignature. In a Google Doc, open Tools: eSignature is there if your plan includes it.
  • Put one signature line per signer in the document. Ask your agent to write a 'Signature: ____' line for each signer, as in the prompt above, and to give the signers' names: each Signature field then goes on its signer's line. Without such lines, the fields go at the end of the document, each under its signer's name.
  • Stay signed in to Google in that Chrome.

Ways to automate Google Docs eSignature requests, compared

As each tool's own page describes it, read on November 17, 2026. "Not documented" means we did not find it on their page.

Sends Google's own eSignature Writes the document too Tracks who signed Setup Price
Reduck Yes Yes, in Google Docs Yes Chrome extension, no API key There is a free tier
Google Docs by hand Yes No Yes, in Drive None Included in eligible Workspace plans
Apps Script No Yes No Script in your Google account Free
Zapier or Make No Yes, from a template Not documented A Zap or a scenario Zapier or Make plan
DocuSign, Dropbox Sign, BoldSign or signNow No, their own e-signature With Zapier, Make or an agent Yes An account with that service, API key or connector That service's plan

Where the others are stronger: DocuSign and the other e-signature services work from servers, also when your computer is off, and offer signing order, bulk send and templates through an API. Google by hand needs no setup at all. Reduck is for teams that already have Google eSignature and want their agent to write, send and follow up the document without a second service.

FAQ

No public one. Google's eSignature help pages describe the feature in the Docs and Drive interface only, and mention no API, and a feature request on Google's Issue Tracker (477131486) asks for a public API to trigger eSignature requests programmatically. Answers on the Make Community (December 2024) and the Zapier Community (April 2026) say the same: Apps Script, Zapier and Make cannot send a Google eSignature request. Reduck does it in your own Chrome, where you are already signed in, so it needs no API.
As Google's help page lists it, read on November 17, 2026: Workspace Individual, and Business Standard, Business Plus, Enterprise Starter, Standard and Plus, Enterprise Essentials and Essentials Plus, and Education Plus when the administrator turns it on. Business Starter is not in the list. Reduck uses the eSignature of your own Google account, so your account must have it.
Yes. Google asks you to confirm before it shares the PDF with signers outside your organisation. The script sends to them only when you agree (allowExternal); without your agreement, it stops and nothing is sent.
On the signature lines of the document, when you give their text. When the document has no eSignature fields yet, request_signatures adds one Signature field per signer: with signatureLine (for example the underscores after "Signature:"), each signer's field goes on one of those lines, in order; without it, the fields go at the end of the document, each under its signer's name. When the document already has fields, for example a template you prepared in Google Docs, it uses them. To place each field at an exact spot on a page, send a PDF with request_pdf_signatures.
Yes, and it is the default. request_signatures and request_pdf_signatures run as a dry run unless your agent passes dryRun false: they fill in the request, read it back and cancel, so nothing is sent. Ask your agent to show you the document and the signers first.
Yes. list_signature_requests lists the files waiting for your signature, or the ones you sent. get_signature_request reads one request: each signer, whether they have signed, and every field they must fill.
Yes, with sign_document. It fills every field you have, on any page, from your full name and initials, and completes the signature. Google asks the signer to accept its eSignature terms first: the script accepts them only when you agree (acceptTerms).
Yes. With reminders, Google sends automatic reminders to the signers who have not signed. cancel_signature_request cancels a request you sent, with an optional message to the signers.
No. The scripts run in your own Chrome, so your computer and Chrome must be on when the agent sends or checks a request. Google itself emails the signers and sends the reminders, so signers can sign when your computer is off.

Similar use cases

Gmail

Send Gmail attachments with Claude or ChatGPT

Claude and ChatGPT can send a Gmail email, but their Gmail connectors cannot attach a file. With Reduck, your AI agent sends a Gmail email or a reply with up to 10 files from your computer, from your own Gmail in your own Chrome. No Google Cloud project, no OAuth app.

Productivity
Google Sheets

Google Sheets MCP

Let ChatGPT, Claude, Cursor or any MCP client read, write and organize your Google Sheets as your own account, with no Google Cloud project, no OAuth app and no service account.

Productivity

Start building not clicking