I have a web application wherein our users create contracts and we have integrated with DocuSign through an embedded recipient experience.
My web application is fairly involved in gathering the appropriate signers, sending emails, requesting signatures, keeping up with signer statuses, etc., and so I believe that an embedded recipient experience makes the most sense for us.
However, our first client using the integration has already been using DocuSign for some time and their signers (CEOs, CFOs and the like) are accustomed to logging into DocuSign, seeing envelopes in their inbox and clicking on them to sign - which is only possible in an integration by adding them as remote recipients. Embedded recipients cannot be associated to a DocuSign user account.
I'd like to keep using embedded recipients, but my client desperately wants to see envelopes created from my application in their DocuSign user account inbox and sign them from there without first having to log into my application.
Is there any clever way to deliver such a request with an embedded recipient experience? Even an atypical workaround, like sharing documents between the embedded recipient and the user account or some other recipient type of which I'm not aware, etc.?
Unfortunately not. When creating an embedded signing session the recipient becomes what's referred to as a Captive Recipient. Captive Recipients follow a different set of rules in regards to email notifications and presence in an inbox.
For example, Captive Recipients don't receive email notifications by default -- but they can supply an email to be CC'ed onto the envelope.
Since the Captive Recipient also has a universal account number, the user is technically part of an account outside of yours or your recipients.
IE: Your recipient views his inbox linked to his userId on account XXXXXXXXX.
The Captive Recipient is part of account YYYYYYYYYY with its own unique userId, so there's nothing for it to match up to.
If your app relies on embedded signing to load DocuSign envelopes into something like an iFrame, you can still do that without using an embedded recipient, which would give you the ability to load them through your webApp as well as let your signer access them via his DocuSign inbox.
To retrieve the signing URL, you make a POST call to https://{endpoint}.docusign.net/restapi/v2/accounts/{accountId}/envelopes/{envelopeId}/views/recipient with the following call body:
{
"returnUrl": "http://localhost/returnUrl",
"authenticationMethod":"email",
"email": "{recipientEmail}",
"userName": "{recipientFullName}",
"recipientId":"{recipientId}"
}
Related
I have been trying to find the way to read the inbound and outbound emails prior reaching the recipients and if the email contains sensitive data, I would modify or rather stop delivering or quarantine that email.
Also, is there any admin setting to schedule send all the email send from org(basically delay sending the emails). I'm aware that this functionality is available in user's mailbox, want to now if any admin setting is available which can be enabled by default for all emails.
I have integrated messages.get and webhook's to fetch all the emails, but those are all either emails which are already delivered. Is there any api or way to detect sensitive emails in real time before getting delivered?
enter image description here
We have used DocuSign Rest API and at times we are seeing duplicate entries against one receiver in DocuSign account under "Sent Items". Though the receiver is receiving the email once only. See attached image for reference. What does the "waiting for others" status indicates and under which scenarios this status will be generated?
waiting for others means that one or more of the signing recipients and/or certified copy recipients has not yet completed their action on the envelope.
The multiple rows in the Sent list means that you have sent the envelope more than once, you'll need to check your code to see how that is happening. I suggest that you have your code make a log entry every time your code calls the DocuSign eSignature API (and for create envelope calls, record the envelope id.)
If you can't figure out how your app is sending multiple envelopes when you expect that only one is being sent, use the API Request Logger to see what is being sent to DocuSign from your app.
Re: only one email was sent even though there were two or more envelopes:
Using the DocuSign web app, examine the envelopes that are in flight to check their recipients. It could be that the email address is incorrect in some of the cases.
Check your email tool. The two email notifications for two different DocuSign envelopes will be very similar and are collapsed by some email agents.
I'm wondering if I can use the GMail API, or some Google Workspace Add-On to aautomatically handle emails received by a specific address.
I have my own web app API, and I'd like any email sent to a specific address to trigger an API call to my web app, without a user having to manually do anything. (I can only seem to find references to how to do this using a visual interface that a user must interact with)
Ideally, this would work for a group address, but an actual account works too if that's a limitation.
Cheers!
The problem....
We have a Web Application that bring in articles from various sources such as (google, bing, yandex).
We wish to add another source. The source is email subscriptions from scientific journals of which there are thousands.
We want our userbase to be able to signup for email subscriptions and pull them into the Web Application. As the subscription process requires an email and a confirmation of email step, this is pretty user unfriendly if an admin has to go and check emails all the time. We have a proposed workflow and would be interested to implement something like the following.
Proposed workflow
User goes to a custom subscription management page in our web
application
User enters the name of the subscription.
User presses 'save' User receives a unique email address from the application (i.e. subscription1233167845#mydomain.com)
user then takes this email and uses it to sign up for the email subscription with the scientific journal
system receives email from scientific journal asking for confirmation
system automatically verifies email address
email alerts received for journal
From here there are 2 possibilities
1) the application parses all resources in email and extracts links
which are submitted to the applications custom crawler
2) information
is scraped directly from email and added to the web application list
of articles
can it be done? Do you have a better way?? Thoughts?
An app that I'm developing needs to test whether, for a given email address, the user has previously sent or received email from the address on the user's gmail account. However, this should be done without the app having the credentials to the google account, and without allowing the app to get any other information other than a true/false result to such a query.
How can this be achieved?
The solution should, if at all possible, use some existing google service to minimize or even completely avoid setting up my own server app to facilitate this.
An initial idea I had for this: use a google apps script that will get an authorization by the user to access email, and then scan all emails to collect the set of unique recipients and senders. Then, those emails will be saved in such a way that some URL handler can practically instantly respond to a query about whether or not a specific email exists in this set.
It's a better architecture to have the app query Gmail directly for this information, instead of using an Apps Script web app as an intermediary. The new Gmail API's Users.messages.list() method allows you to search for messages, and the q parameter takes the same types of queries that the Gmail UI supports, such as "to:person#example.com". Additionally there is a read-only scope supported by the API, so that users can feel more comfortable with the app gaining access to their inbox.