Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Question

Modusign document URL expiration issue

  • December 9, 2025
  • 3 replies
  • 33 views
M

Hello,

I am the Technical Support Manager at Modusign.

 

Through the Trigger (document_all_signed) event, Modusign currently provides access to the finalized document using a pre-signed URL delivered via file.downloadUrl. Due to security constraints, this URL has a 10-minute validity period.

 

We identified an issue where a specific customer is using this trigger to pass the URL into a Google Drive folder as an Action. In this flow, the document itself is not being stored; instead, only the URL string is being saved, which becomes invalid after the expiration period.

 

Although retrieving the actual file is feasible by issuing a GET request within the Webhook Response of the same trigger, adding an additional Action—as was previously required—may result in unnecessary Zap consumption on Zapier. We would appreciate your review of this behavior to confirm the optimal implementation.

This post has been edited by moderator to move it into the Developer Zone.

moid-space

3 replies

Sparsh from Automation Jinn
Forum|alt.badge.img+6

Hey ​@Modusign-Dustin,

I think customer can do a Get request using Webhooks in Zapier action but I think it would be user friendly if you include the Download file action in the Zapier integration itself to make it easier for the customer. Make sure that the URL is publicly accessible because otherwise the customer may not be able to download it through Zapier.

I think some of the other sign apps do like that so I guess you shouldn’t worry about the Zap consumption. Hope it helps!

https://zapier.com/partnerdirectory/automation-jinn | Zapier Silver Solution Partner| Automationjinn.com
M

​@Sparsh from Automation Jinn  

Thank you for your prompt response.

 

The pre-signed URL could previously be accessed via a GET request without requiring the end user’s credentials. In the earlier Trigger setup, the Zap performed a GET request within Modusign to retrieve the document content. Since the document was already permission-validated at that stage, the file could be successfully backed up to Google Drive.

 

Below is the URL of the related Zap for your reference.

 

Sparsh from Automation Jinn
Forum|alt.badge.img+6

Hey ​@Modusign-Dustin,

Please share screenshots of Data In, Data Out as well as how each Zap step is configured for us to have more context rather than sharing a link.

If you could do the file retrieval in trigger itself then great as well but if it’s something not possible then have a Download File action can also be user friendly. You will have to do file dehydration to handle the files probably because each step only gets 30 seconds to run its API calls and any additional code before it would time out. See more about it here- https://docs.zapier.com/platform/build-cli/hydration. You can also reach to Zapier Developer Platform team for any specific questions- https://developer.zapier.com/contact. Hope it helps!

https://zapier.com/partnerdirectory/automation-jinn | Zapier Silver Solution Partner| Automationjinn.com
Terms & ConditionsAccessibility statement