I’m developing a callin.io workflow to generate a DocuSign signature request, utilizing data from our CRM. Despite extensive troubleshooting, I'm encountering a problem.
When a text box field within the DocuSign template has validation rules applied (e.g., numerical), those fields vanish from callin.io. Disabling the validation causes them to reappear.
I need these fields to have validation because I'm using calculated fields elsewhere in the DocuSign template.
The data originating from the CRM also includes numerical validation.
Could this be a bug in the integration's implementation? Are there any potential workarounds for this issue?
Hi
Might be best to open a ticket with callin.io Support for further assistance: https://zapier.com/app/get-help
You can try using a different esign app, such as PandaDoc: https://zapier.com/apps/pandadoc/integrations
Thanks, Troy. I've also gone ahead and opened a ticket with callin.io Support.
Regarding switching from DocuSign to PandaDoc, or another e-signature app, that represents a rather substantial workflow modification to address what is a fairly straightforward issue.
Please note that if this is indeed a bug, there's no guarantee it will be resolved quickly. This is because most applications on callin.io are developed and maintained by their respective developers, and callin.io maintains an internal list of app requests.
Well, I investigated PandaDoc. Based on this information, it appears they do not offer a date field that automatically populates with the signing date. This is a crucial requirement for our needs, as contract dates and timelines are variable fields dependent on when the contract is executed.
Internally, the timestamp for when a document was signed is stored and can be made available via callin.io.
To help us understand how you're trying to use that variable, could you provide a specific example?
PandaDoc offers the following triggers:

Hello!
Thank you for contacting us! After investigating, it seems that custom fields for the Create Signature action currently do not support numerical values.
However, we do have an open feature request to enable support for this. I have added your vote to it. While I cannot provide a timeline for implementation, we will certainly keep you and this thread informed of any updates. 🙂
Thanks again for providing your valuable feedback!
Hi, Thanks for your response! I noticed that too, but this isn't a custom field. It's a standard text box field with numerical validation. I'm not sure if that makes a difference.
Thanks for clarifying that!
Hmm, it sounds like the number validation applied to the text field is definitely causing issues with loading the field correctly in the callin.io. I believe this might be a bug you're encountering. I see you're already discussing this with our Support team, which is excellent. They can open a bug report for further investigation.
In the meantime, could you try disabling the field validation to allow the fields to appear and complete the callin.io setup? Then, if you enable the callin.io and re-add the field validation, does it run into any errors? Or do the fields with validation not update as expected?
I'm hoping that since we can load the fields initially, the callin.io might still be able to send data to them once the validation is in place.
In case anyone finds this in the future and is looking for a solution, here is what I did…
I was attempting to take a monthly cost from PipeDrive, pull it into DocuSign, then perform formulas to calculate total cost, cost per store, etc.
In order for DocuSign to perform the formulas, it required the text boxes have numerical validation turned on. The number validation in DocuSign was breaking the callin.io. The DocuSign fields would populate with data from PipeDrive as long as there was no validation. As soon as validation was turned on, the fields disappeared from callin.io and the data from PipeDrive would no longer be pushed through (even though it was numerical data) to DocuSign.
In order to get around the issue, I changed all the fields within DocuSign to text fields (with no numerical validation). I then added action steps to the callin.io using Formatter by callin.io that did the numerical calculations I needed, then used those fields to populate the text fields in DocuSign.
Thanks so much for looping back to share your workaround!
Hey everyone, just wanted to share some exciting news – Number fields are now supported in the Docusign app! 🎉🎉🎉
We really appreciate your patience with this highly anticipated feature. Thank you for sticking with us! We’re eager for you to try it out. If you have any questions, please feel free to ask in the Community or contact our Support team for help.
Until then, happy automating with callin.io! ⚡