Status Update
Comments
lo...@google.com <lo...@google.com> #2
Hello.
Can you provide in terms of cost/benefits the impact of this feature in your business ?
Have a nice day!
xd...@gmail.com <xd...@gmail.com> #3
Sure!
For one example, my higher ed institution currently generates Google Doc contracts for a couple hundred people at a time via Apps Script. We create a new copy of a Doc for each person, mail merge with some find-and-replace, and share the Document with the sign-er programmatically. The document currently has a text box that says "sign here" at the bottom where they type in a name and date. It would be lovely if I could use the Google Docs Approvals[1] system or this eSignature system via API to request this signature from them instead of manually checking to see who's typed their name and who hasn't.
lo...@google.com <lo...@google.com> #4
Hello.
This has been reported internally, any updates will be posted here.
Have a nice day!
is...@google.com <is...@google.com>
jp...@google.com <jp...@google.com>
du...@fullphysio.com <du...@fullphysio.com> #5
di...@cloudoffice.bg <di...@cloudoffice.bg> #6
I'm the Director of Cloud Office (Premier CEE Google Partner). We are currently bringing several million USD pipeline annual net revenue to Google and this feature is really important for our backoffice and our customers.
We want to build a contract management solution on top of Google Docs and allow the entire contract management for our thousands of customers to rely on Google Docs. This will be a showcase of Google commitment to be Enterprise product company.
Feel free to reach to me at our company's email if you have questions - info at
ey...@eifo.dev <ey...@eifo.dev> #7
My current workflow for platform use is using google docs and drive api:
1) creating a copy of the contract template per contract with drive api
2) retrieving doc with docs api
3) batchUpdate with docs api to replace values
4) drive permissions create
5) dropbox sign api for emailing contract for esignature.
Allow programtic request esignature and we willl be able to do it all with google, worth it!
vl...@gmail.com <vl...@gmail.com> #8
jo...@asseteducation.co.uk <jo...@asseteducation.co.uk> #9
mt...@gmail.com <mt...@gmail.com> #10
ev...@gmail.com <ev...@gmail.com> #11
he...@hope.edu <he...@hope.edu> #12
eSignature for Google Docs is rolling out to end users soon
In the coming weeks, we will roll out eSignature for Google Docs to end users on select Google Workspace editions. eSignature offers a variety of features to help you streamline requesting and capturing signatures, helping you stay organized and keep your work moving along. Specifically, you can:
- Request eSignatures, including signatures from more than one user and from non-Gmail users.
- View the status of pending signatures and find completed contracts.
- Keep contract templates to initiate multiple eSignature requests.
- View an audit trail of completed contracts,
- Use custom text fields to request additional information from signers, such as job titles, email addresses and more.
- Sign contracts from both mobile devices and PCs.
Sure would be nice to get an API right about now...
dg...@gmail.com <dg...@gmail.com> #13
wa...@verona.k12.wi.us <wa...@verona.k12.wi.us> #14
I'm also surprised at the original reply of "Can you provide in terms of cost/benefits the impact of this feature in your business ?" Most departments work with large number of staff and entities. To have to generate individually e-sign documents one at a time for each personnel or entity makes using Google eSignature unusable. if we want adoption of Google eSignature it should handle all workflows - from single e-sign situations to mass staff/entity e-sign ones.
or...@apexcaremn.com <or...@apexcaremn.com> #15
We have large amounts of documents that need to have an official "Sign Off" that they have been read and agreed to by staff. This is especially true in terms of policy documents that need annual signatures. Currently this is a large workflow to generate new documents twice a year and send esign requests for each document and then file them. An api that lets us make a ui extnesion to "Add" a pre set page to the document would be perfect. Even better wold be something like "Return the signed document to the same folder that the source doucment is from". Then we'd be able to process all of these documents in a single script instead of days of management.
Other industry use cases:
1. Annual Policy Agreements - Especially HIPAA organizations that need regular re-agreeement to the procedure manuals
2. Annual Medical/Staff notifiactions - Insurance forms, renewal of tax forms, anything that needs to be done regularly for efficiency
3. Re-Evanulations, Performance Reviews. Items that can be done on a regular schedule if the database triggers set the correct times to send the paperwork.
bm...@kas.tw <bm...@kas.tw> #16
ja...@influencer.com <ja...@influencer.com> #17
bo...@haiilo.com <bo...@haiilo.com> #18
sa...@summerwoodplace.com <sa...@summerwoodplace.com> #19
ru...@gmail.com <ru...@gmail.com> #20
ge...@gmail.com <ge...@gmail.com> #21
ad...@lab.rockdocinc.com <ad...@lab.rockdocinc.com> #22 Restricted+
ed...@web2action.nl <ed...@web2action.nl> #23
te...@bluevector.ai <te...@bluevector.ai> #24
ji...@cogniris.com <ji...@cogniris.com> #25
We would be happy to discuss our requirements if and when you are considering this feature.
lo...@rosabianca.tn.it <lo...@rosabianca.tn.it> #26
na...@embedism.com <na...@embedism.com> #27
ja...@influencer.com <ja...@influencer.com> #28
It has been in blocked status for a long while.
ad...@unionmadestickers.com <ad...@unionmadestickers.com> #29
ab...@finpace.com <ab...@finpace.com> #30
ry...@ryan-hunt.com <ry...@ryan-hunt.com> #31
ru...@aeco.cloud <ru...@aeco.cloud> #32
jp...@goodinc.co <jp...@goodinc.co> #33
sa...@everythingoncloud.com <sa...@everythingoncloud.com> #34
se...@triplea.agency <se...@triplea.agency> #35
ne...@gmail.com <ne...@gmail.com> #36
er...@flowdigitalstudio.com <er...@flowdigitalstudio.com> #37
sb...@gmail.com <sb...@gmail.com> #38
ph...@imlakeshorganics.com <ph...@imlakeshorganics.com> #39
Would love to be able to use Zapier to initiate an eSignature request from a doc/pdf template
de...@geewiz.co.za <de...@geewiz.co.za> #40
Can we automate the sending of an eSignature document on Google Docs through App Scripts or GCP?
Currently I think the answer is NO :(
No API connections exist that I could find.
Google I am on my knees begging for you to add this in. This would be super useful
le...@gmail.com <le...@gmail.com> #41
Apps Scripts would be the king, but I will take anything (GCP or a plain API)
ri...@thunk.co <ri...@thunk.co> #42
ch...@tscloud.work <ch...@tscloud.work> #44
If that works my company could approve legal docs (e.g. invoice, expense) with an e-signature and export as PDF programmatically with a GAS embedded in an Appsheet App.
ne...@elevateseattle.net <ne...@elevateseattle.net> #45
ma...@papernest.com <ma...@papernest.com> #46
As others have already said, we are interested in:
- Development of API to automate esignature.
- Feature to order signatures (signature request flow), where the signature of a user triggers the request for the next one.
I hope we can see this feature soon.
ty...@ashleyvance.com <ty...@ashleyvance.com> #47
da...@thejohnsonteam.net <da...@thejohnsonteam.net> #48
to...@business-happen.com <to...@business-happen.com> #49
in...@reneww.co.uk <in...@reneww.co.uk> #50
ii...@expobeds.ie <ii...@expobeds.ie> #51
in...@reneww.co.uk <in...@reneww.co.uk> #52
From my G-sheet i use fields to populate a google docs template creating a dynamic document and save as pdf. (pdf now supported which is great to see).
Have ability to call / place signature component onto dynamic doc / PDF. ie use {{signature}} and replace with signature component
Send this document for sign via api.
Return sent timestamp.
Bonus points for allowing api endpoint to check if a document status / if has been signed. (Would set up using an app script trigger) to call this endpoint at set intervals.
si...@gmail.com <si...@gmail.com> #53
we...@wiartonpropellerclub.ca <we...@wiartonpropellerclub.ca> #54
ra...@axistravelgroup.com <ra...@axistravelgroup.com> #55
xd...@gmail.com <xd...@gmail.com> #56
That Gemini sounds like he or she might not always be telling the truth 🤔
mi...@de-ru.net <mi...@de-ru.net> #58
in...@reneww.co.uk <in...@reneww.co.uk> #59
al...@tech-knowledge-ease.com <al...@tech-knowledge-ease.com> #60
Several of my clients really need the following:
- Ability to assign a person to an existing Signer block and initiate the Request Signature process via API
- Ability to trigger a webhook upon completion of the signing process
We don't [yet] have any use cases that require the ability to add/configure signature fields to documents programmatically, but there should at least be a way to integrate the signing process into another workflow when the signature fields already exist in the doc!
Please provide an update—with more information than the current "blocked" status—ASAP.
fy...@bs-energy.de <fy...@bs-energy.de> #61
ja...@jusd.k12.ca.us <ja...@jusd.k12.ca.us> #62
ad...@premiercloud.com <ad...@premiercloud.com> #63
ba...@projxon.com <ba...@projxon.com> #64
ca...@surepath.ai <ca...@surepath.ai> #65
ro...@pipefy.com <ro...@pipefy.com> #66
a....@datatile.eu <a....@datatile.eu> #67
Having the API would give us a huge advantage.
1. Assign signatories to predefined parties
2. Request signatures
3. Get notified when it’s signed
jj...@storyllp.com <jj...@storyllp.com> #68
al...@soldera.org <al...@soldera.org> #69
em...@business-class.fr <em...@business-class.fr> #70
er...@flowdigitalstudio.com <er...@flowdigitalstudio.com> #71
da...@climbcred.it <da...@climbcred.it> #72
Is there anything on the roadmap to get this feature request implemented?
au...@gmail.com <au...@gmail.com> #73
This would also allow for automated managing of signers (assigning emails to signer fields), and manual / automated sending of the PDF files to be signed through email (automated by company rather than google as an option.)
mi...@nuluxventures.com <mi...@nuluxventures.com> #74
am...@zapwizards.de <am...@zapwizards.de> #75
te...@gmail.com <te...@gmail.com> #76
km...@biocarbonpartners.com <km...@biocarbonpartners.com> #77
al...@thdesenvolvimento.com.br <al...@thdesenvolvimento.com.br> #78
A API é fundamental.
no...@gmail.com <no...@gmail.com> #79
Is there any pressure form Docusign to not make it?
Description
A short description of the request:
Google Docs now has eSignature support:
Please provide us a way to programmatically create these eSignatures via the Google Docs or Google Drive API. Bonus points for Apps Script support.
What is the purpose of this new feature?
Sometimes, people need to generate many contracts at once. It would be nice if we could form-fill create Google Docs and send the signature requests along to the other party without having to create them all by hand.
What existing APIs would this affect?
The Google Docs or Google Drive API
What existing data does this use?
Just Google Docs body contents and the new eSignature system.