I have a use case where I would like to send Document Notification emails to an address that is set while a Form is being filled out.
The Document is currently “manually” triggered via a Rule/API call that is essentially just doing a Post to https://api.feathery.io/api/document/fill/ on the document with a body of
It’s worth noting that the person signing the document is not the same one filling out the form. That’s why I’d like to add the ccNotificationEmail.
Can I just add/create {{ccNotificationEmail}} in the Document->Settings->Notifications->Signature Notifications Emails field?
If I can’t get a “dynamic” notification email, can I add a second email to the “signer_email” parameter?
If neither of those are options, how can I retrieve the returned JSON body with the envelope url after calling await feathery.http.connect(‘Send Chaffin GWO Retainer’);?
At this time dynamic input in the notification email within the Documents section is not supported - this can be flagged as a feature request
The signer_email is meant for one address only.
Would there be a particular reason for using a manual posting via API over using the document autofill + native email integration?
With the document autofill, you can map your form fields accordingly (it seems this has been done on your document). Then you can use the email integration to attach the file and/or include a document link for signing. This way you can also add dynamic recipients. (This would be similar to your bullet point #2 where possibly more than one email can view the document)
I have several documents and depending on how the form is completed I send one or the other. Because of this I can not rely on the Document Settings to determine when/if the document should be sent for signing.
I have implemented the secondary email integration you suggested to attach the document link. Thank you for the suggestion.
Is there any chance of getting dynamic emails for the notifications on a dev roadmap for the future?