Sometimes its easyer to ask then to try to figure out by myself, as we have here some Tape wizards that might have passed through the same challenges before…
Our client asked us how to send documents to Docusign automatically.
Did anyone here already had to send files generated in tape to e-signature platforms? If so, what would be the best path for that?
I will update this topic if I find out by myself, but i’m wide open for indications now!!
@toni is Docusign a requirement for your use case?
To be honest, I haven’t personally tried connecting Docusign to Tape. But historically, it has been Docusign that doesn’t play nicely with integrated tools (unless you’re willing to pay very large fees!)
I have used Tape to create a PDF with text-tags for Sign Now and then email that doc (via tape automatio) into the sign now account which is received, text tags auto processed, and sent out for e-signature.
I like SignNow far more than Docusign for these types of integrations
The client is ready to migrate for any other tool that would work well with Tape on that workflow:
Custom Doc created at Tape > Send for e-signing > Signing process > Signed Doc coming back to Tape (or notification)
We actually tried connecting with Pandadoc after @tomaz repply, but it works with Templates inside Pandadoc instead of allowing us to upload a new file with custom data through connection.
So, we could indeed try SignNow for this purpose. I’d love to understand better how does those “text tags” would work at this workflow.
I have integrated DocuSign for a client - it was a pain to set up but we did get it successfully sending and receiving documents via an oAuth connection.
This was several months ago so the details are fuzzy, but I believe we first had to create an app in the DocuSign dev environment. They require you to get document sending working within the dev environment before you can request production keys.
Once you have your production keys, the general flow is:
Get the file binary and convert it to base64
Generate the DocuSign request JSON following their Envelopes endpoint documentation
Post to the endpoint using the oAuth connection
DocuSign was a requirement for this customer - if I were doing this from scratch I would recommend another service with a more user-friendly API, but I can at least attest that a DocuSign integration is possible if your client is set on using that.
I haven’t tried create an document inside tape to docusign, but most of the client I have is that document was created inside docusign and we integrate that docusign to tape. The automation will pin point on what client in CRM the docusign will attached.
last time when I checked is that docusign will only allow generation of document using templates. but not sure if this is already allowed today.
thank you Jacquelin, by the way I am very thankfull also for your integration tool!!
indeed, I had to create a developer account to generate key, but it seemed to be very complex to integrate, so the client is not requiring Docusign, the workflow is more important then the tool.
Thanks Toni, glad you’ve been able to make use of it!
I agree with that - the integration was definitely more pain than it was worth. I’m not sure of any other esignature services that let you send file data rather than using a template, but I am definitely interested to hear if anyone else has found something that works nicely.
If anyone is looking for a developer friendly, affordable and feature rich eSignature platform, I highly recommend checking out Docuseal (https://docuseal.com). Not only are API generated documents super cheap (only $0.20 USD per and only if the doc is signed) but you can not only use templates, but also generate PDFs with text tags and pass them to Docuseal, just like PWA used to allow for RightSignature files. It’s really super easy to use!