# Adobe Acrobat Sign - Fields not Saved

**URL:** <https://community.hubspot.com/t/adobe-acrobat-sign-fields-not-saved/147833>\
**Category:** HubSpot-built Apps\
**Created:** [March 30, 2026, 8:25pm UTC](https://community.hubspot.com/t/adobe-acrobat-sign-fields-not-saved/147833 "2026-03-30T20:25:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![SBasile](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/sbasile/32/88586_2.png) [@SBasile](https://community.hubspot.com/u/SBasile)\
**Post date:** [March 30, 2026, 8:25pm UTC](https://community.hubspot.com/t/adobe-acrobat-sign-fields-not-saved/147833/1 "2026-03-30T20:25:41Z")

</div>

We are having issues with the Adobe Acrobat Sign App. If a user uses the app card to upload a template, adds the recipeint information, and adds fields to the template, the inserted fields do not get saved to the document when the Send button is pressed.

If the user starts the process from HubSpot but exits instead of sending the document, they can open the draft in Adobe Sign, place the fields and send the document. In this situation, the fields are sent with the document.

Any help or ideas would be appreciated.

---

<div class="post-metadata">

**Author:** ![stassey](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/stassey/32/36_2.png) [@stassey](https://community.hubspot.com/u/stassey)\
**Post date:** [March 30, 2026, 9:03pm UTC](https://community.hubspot.com/t/adobe-acrobat-sign-fields-not-saved/147833/2 "2026-03-30T21:03:36Z")

</div>

Hey @SBasile,

Thanks for the details! The fact that the workaround (exiting and continuing in Adobe Sign directly) preserves the fields is definitely an interesting clue worth exploring further!

Tagging in some of our top contributors to see if they’ve come across this one:

Hey @RubenBurdin, @SteveHTM, @evaldas -- Has anyone encountered this specific behavior with the Adobe Acrobat Sign integration?

Thank you in advanced!

Sam, Community Manager

---

<div class="post-metadata">

**Author:** ![SBasile](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/sbasile/32/88586_2.png) [@SBasile](https://community.hubspot.com/u/SBasile)\
**Post date:** [March 31, 2026, 4:44pm UTC](https://community.hubspot.com/t/adobe-acrobat-sign-fields-not-saved/147833/3 "2026-03-31T16:44:12Z")

</div>

Hello-

I think I may have found the issue. In Step 4, there are two buttons that will close and send the document. I think that the one at the top right, although enabled, does not save the changes to the document before closing and sending.

You must instead use the Send button at the bottom of the toolbar on the left to submit your changes before the document is sent.

 ![SBasile_1-1774975443819.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/b/1/b186eacdba7261ac5dee09cde889d36e63558351.png)

---

<div class="post-metadata">

**Author:** ![SCaracand](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/scaracand/32/228533_2.png) [@SCaracand](https://community.hubspot.com/u/SCaracand)\
**Post date:** [October 6, 2026, 10:00am UTC](https://community.hubspot.com/t/adobe-acrobat-sign-fields-not-saved/147833/4 "2026-10-06T10:00:44Z")

</div>

Hi @SBasile, if you’d like the fields to already be in the document before it goes out for signature, our app DocuGen builds them into the template itself. The HubSpot fields are placed once in your Word template. Each document is then generated from the record with that deal’s contact, company and line item data filled in, and sent for e-signature without leaving HubSpot. The PDF saves to the deal’s attachments too.

You can find us on the [marketplace listing](https://ecosystem.hubspot.com/marketplace/listing/docugen).

P.S. The free plan covers 400 documents or 200 e-signatures a month, with unlimited users so your whole team can send documents to sign at no cost.