Settings and activity
7 results found
-
4 votes
Timothy Hall
supported this idea
·
-
23 votes
Hi,
Thank you for taking the time to leave your request. We have great news – the option you are looking for already exists.
PandaDoc makes 3 attempts to deliver a webhook. After this, you can manually retry failed webhooks, as shown in the picture.
For more information, please check the link below:
An error occurred while saving the comment Timothy Hall
supported this idea
·
-
10 votesTimothy Hall
supported this idea
·
An error occurred while saving the comment Timothy Hall
commented
If no one has signed the document, simply putting the document back into draft and resending works just fine. However, if a subsequent signer has deleted the email it would be nice to send to them directly.
Another work-around is to post a public comment, which if was available from the API could server as a proxy to the resend. A quick API call to post a public comment would allow for a simple "Please Review" message that would go out to all parties.
-
16 votes
Hi,
Thank you so much for reaching out – this is a great suggestion and we have had other customers asking about this feature as well. While we’re looking into the possibility of developing it, it isn’t on our product roadmap for the next few months. Please feel free to upvote or leave your comment to let us know how and why this functionality is important for you. Thank you!
An error occurred while saving the comment Timothy Hall
commented
Very important feature for the embedded use case. There is no way to understand the current status of the document outside of an arbitrary state which gives no insight into the recipient actions or attempts.
Timothy Hall
supported this idea
·
-
10 votesTimothy Hall
supported this idea
·
-
20 votes
An error occurred while saving the comment Timothy Hall
commented
This is crucial for client engagement and for the embedded api case is completely missing. The decline reason could be provided in a webhook, the document details endpoint or even a new endpoint entirely.
Timothy Hall
supported this idea
·
-
4 votes
An error occurred while saving the comment Timothy Hall
commented
For the embedded use case, since the user cannot be created with an email outside of the organization's domain, there is no way to have the reply be to the user that created and sent the document. This means that all replies from a client perspective are completely lost, breaking the chain of communication.
Timothy Hall
supported this idea
·
This is mission critical for us. Servers go down sometimes or there is a network blip, this would help with intermittent issues.
The work around is quite clunkly without a retry from the API. We have to keep track on our side of which failed webhooks we have grabbed the request data for and already processed.