How to connect DocuSign to Google Sheets for status, not contents

To connect DocuSign to Google Sheets, export envelope status (which envelope, who has signed, who has not, how long it has waited) into a sheet, and link to each envelope instead of copying its contents. Status is metadata that a spreadsheet handles well. The signed agreement and its audit trail should stay in one controlled place, and a spreadsheet is not that place.

Key takeaways

• A sheet should hold envelope status, current recipient, age and a link, and never the contents of the agreement.
• The most useful column names the recipient the envelope is currently waiting on, because routing order means only one person can act at a time.
• The certificate of completion is the evidence of signing, so a status sheet must never be presented as an audit record.
• DocuSign Connect pushes status changes as they happen, so use it for declined envelopes and keep polling for the daily report.
• Alert immediately on declined envelopes, and flag envelopes approaching expiry before they expire.

What we'll cover

• Status yes, contents no
• The envelope lifecycle
• Building it with CodeWords
• Chasing what has stalled
• Recipients, routing, and where it gets stuck
• The audit trail you must not fragment
• Fields from the document, carefully
• DocuSign Connect, and when to push instead of poll
• Making it survive
• Limits worth knowing about
• What to set up first
• Frequently asked questions

Status yes, contents no

Put status in the sheet and keep contents out. Chasing status by hand is work nobody does consistently, while signed agreements are the documents an organisation most needs in one controlled place.

Status is metadata: which envelope, which recipients, what state, how long. It is useful in a sheet, shareable with a team, and not sensitive in the way the document is.

Contents are the agreement. Terms, prices, signatures and personal details belong in the document management system and its access controls.

A spreadsheet has none of those controls. It has no retention policy and no access audit, and its sharing tends to widen over time without review.

Extracting a few fields from the document into the sheet needs a deliberate decision, covered below.

Link, do not copy. A link to the envelope gives the document to anybody with permission and nothing to anybody without it, which is the correct behaviour.

The envelope lifecycle

The sheet tracks envelope states, so learn them precisely.

Created: not yet sent. This is a draft, and drafts are frequently forgotten.

Sent: delivered to the first recipient in the routing order.

Delivered: a recipient has opened the envelope. This differs from sent, and the distinction matters when chasing.

Completed: everybody in the routing has signed.

Declined: a recipient refused. Somebody needs to know immediately.

Voided: the sender cancelled the envelope.

Expired: the envelope timed out according to its settings. This state surprises people most, because the document simply stops being signable.

A sheet with a status column and the timestamp of the last change answers almost every question about a contract pipeline.

Building it with CodeWords

CodeWords connects to 3,000+ integrations (CodeWords pricing page, 2026), and each connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: which envelopes, which statuses, and which sheet.
3. Authorize the connection to DocuSign for the relevant account, plus access to the target spreadsheet.
4. Describe the exceptions: an envelope voided since the last run, a recipient whose email has bounced, an envelope approaching expiry.
5. Run it against a test account and confirm the statuses before pointing it at live agreements.

You describe the outcome; Cody builds it, connects it and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows (CodeWords pricing page, 2026). Details are on the pricing page.

Chasing what has stalled

Automated chasing replaces the manual work of clicking through envelopes to see what is stuck, and it is the reason to build the sheet.

Separate sent-and-never-opened from opened-and-not-signed. The first is often a delivery or address problem; the second is a person.

Report by age. A contract that has waited three days and one that has waited three weeks need different responses.

Name the specific recipient the envelope is waiting on, not just the envelope, because only one person can act at a time.

Flag approaching expiry before it happens. An expired envelope has to be resent, and countersigning starts again.

Alert on declined immediately. Delay is costly in this state, and DocuSign's own notification may go to somebody who is not watching.

Report the aggregate weekly: how many envelopes are outstanding, the average age and the oldest. Sales and legal teams rarely have these numbers and would act on them.

Recipients, routing, and where it gets stuck

Routing order decides who can act, so the sheet must show the current recipient. Signing is sequential, so recipient three cannot act until recipients one and two have, and "waiting on" has exactly one answer at a time.

Recipient types differ. A signer, a carbon copy and a certified delivery recipient are different roles. An export that treats them alike overstates how many people are holding things up.

Email addresses go stale. A bounced recipient leaves the envelope stuck, with no obvious signal in the status alone.

Delegation and reassignment happen, so the person who signs may not be the person it was sent to. This matters for the record.

Report the current recipient and their status. This is the most useful column in the sheet, and it turns a report into a task list.

The audit trail you must not fragment

Keep the audit trail in DocuSign and never rebuild it in a spreadsheet. The certificate of completion is the evidence that a document was signed, by whom, when and from where, and it lives with the envelope.

Do not reconstruct the certificate in a sheet. A sheet of statuses is a management report, not evidence, and presenting it as evidence is a problem.

Keep completed documents in one controlled place, with the certificate, rather than scattering copies into drives and sheets.

Link from the sheet to the envelope, so the authoritative record is one click away and DocuSign still governs access.

Note retention. Completed agreements usually carry a retention obligation, and a spreadsheet copy sits outside the process that enforces it.

Fields from the document, carefully

Extract a value from inside a document only when you genuinely need it, such as a contract value, a start date or a selected option.

Use form fields, which are structured for this, rather than parsing the document.

Name fields consistently across templates. The export finds fields by name, and templates get copied and edited.

Extract the few that matter, and decide each one deliberately.

Never extract signatures, identifiers or payment details into a spreadsheet.

Consider whether the value belongs in the customer relationship management (CRM) system instead. A CRM usually has better access control, and it is where somebody will look anyway.

Report the missing field rather than producing an empty column. Otherwise a template edit that renamed a field fails silently.

DocuSign Connect, and when to push instead of poll

Use DocuSign Connect to push events when latency costs something, and poll for the daily report. Polling is the obvious approach and the more expensive one.

DocuSign Connect pushes envelope events to an endpoint when status changes, so you learn about a signature within moments rather than at the next poll.

A declined envelope justifies it. Waiting up to a day to find out somebody refused is a real cost, and a push removes it.

Verify the payload. The endpoint is public and will receive things you did not send.

Handle retries. Delivery is retried, so key on the envelope and the status to ignore repeats.

Keep a scheduled reconciliation. Pushes are occasionally missed, and a daily pass comparing the sheet with the account catches what slipped.

Poll for the daily report, where a few hours of latency costs nothing. The two approaches suit different questions, and using both is normal.

Making it survive

Five practices keep the export reliable.

Export incrementally by modified date, since a full account export gets large.

Replace a named range rather than appending. Envelope status changes, and a log of state transitions is a different sheet from a current-status sheet.

Handle the token refresh, which is where these integrations break after weeks of working.

Report envelopes in unexpected states rather than bucketing them.

Report the outcome: envelopes exported, statuses changed since the last run, and anything approaching expiry.

Limits worth knowing about

Five limits affect this build.

Rate limits apply per DocuSign account, so a full history export needs pacing. Check your plan's limits in DocuSign's developer documentation.

Tokens expire and must be refreshed, and the user can revoke consent.

Demo and production environments are separate, with separate credentials and separate data.

Google Sheets allows up to 20 million cells per spreadsheet (Google Docs Editors Help, 2026), which a multi-year envelope export can reach.

Some envelope detail requires additional calls, so a sheet with recipient-level columns costs several requests per envelope and needs pacing.

What to set up first

Set up a current-status sheet first: one row per open envelope, with the status, the recipient it is waiting on, the age and a link to the envelope. It replaces the weekly exercise of clicking through a list to see what is stuck, and it takes an afternoon.

Two habits make the difference. Name the specific recipient the envelope is waiting on, since only one person can act and chasing the wrong one wastes everybody's time. And link to the envelope rather than copying anything from inside it, so the document and its certificate stay in one place with access controls intact.

Frequently asked questions

Should the sheet contain the documents?

No. Status, recipients and age belong in a sheet. The agreements and their certificates of completion belong in a controlled system. Link to the envelope rather than copying it, so DocuSign still governs who can open the document.

What is the most useful column?

The most useful column names the recipient the envelope is currently waiting on. Routing order means only one person can act at a time, so a sheet that names that person turns a status report into a chase list.

Why did an envelope stop being signable?

The envelope most likely expired, according to its settings. This state surprises people most, because nothing dramatic happens: the document simply stops working and must be resent. Flag envelopes approaching expiry so you can act before it happens.

Are sent and delivered different?

Yes. Sent means the envelope went out, and delivered means a recipient opened it. An envelope sent and never opened is often a delivery or address problem. One opened and not signed is a person. Each needs a different chase.

Can I extract values from the contract?

Yes, using form fields, which are structured for this, and only the few values that matter. Never extract signatures, identifiers or payment details. Often the value belongs in the CRM rather than in a spreadsheet.

Is a status sheet acceptable as an audit record?

No. The certificate of completion is the evidence of signing, and it lives with the envelope. A status sheet is a management report, and presenting it as evidence is the mistake to avoid.

Why does the integration stop working?

Usually the access token expired and was not refreshed, or consent was revoked. Both are ordinary, and both look like a credential problem. Test both during setup, not on the morning somebody needs the report.

Should I poll for status or use webhooks?

Use webhooks for anything where latency costs, especially a declined envelope, and poll for the daily report, where a few hours of lag does not matter. Using both is normal, with a scheduled reconciliation to catch missed pushes.

What is the one event worth an immediate alert?

Declined. Everything else can wait for the next report, but a refused agreement needs attention the same hour. DocuSign's own notification often goes to a sender who is not watching their inbox.

Related reading

• DocuSign and CodeWords
• Connecting QuickBooks to Google Sheets
• CodeWords integrations and templates