How to save signed contracts in Google Drive automatically
When a contract is signed in fynk, Zapier files the PDF in Google Drive for you. Set it up once, and it runs on its own from then on.
Video transcript
Click any line to jump thereHello and welcome to this fynk Use case. In this video, I'm going to show you how to automatically save every fully signed contract from fynk to Google Drive. Let's get it started. It's really easy to do. We'll build a zap, sign a contract in fynk, and watch the PDF appear in your drive. The first step is building the zap.
Open Zapier, click Create and start a new zap.
The first step is the trigger. This tells Zapier when to start the automation. Add fynk as the trigger app and for the trigger event use new sign document.
Make sure your fynk account is already connected to Zapier, but if it's not, here's how you can do it. In fynk, open your account settings and choose API integrations. Then click on fynk API. In this page, you can create a new token and give the API key to Zapier. If you don't see this option, you need to contact your account owner and ask them to create an API token for you. After connecting fynk to Zapier, go back to Zapier and test the trigger.
The trigger works and now I can see a couple of my recent Fynk documents in my account. Choose any sample data that you like, but make sure the one that you choose is a signed document. Then just hit continue with selected record. For the next step, which is the action step, choose fynk Again. As the action event, choose Find Document Download URL.
Click continue and in the configure page make sure you click on these three dots and choose Costume.
and then search for document UUID from the previous step.
Go ahead and again test this step as well.
And you can see that now we have the document PDF URL.
The final step in our zap is to use this URL to save PDF into our Google Drive. So go ahead and add a new step.
Choose Google Drive this time. As the action event, search for upload and select upload file.
Make sure your Google account is already connected and then hit continue. In the configure page, choose the drive that you want to save the PDF in and also the folder that you want. For this example, I already have a folder as signed documents, and as the file you can choose the PDF URL that we already extract from the previous step. So I add it here. For the convert to documents section, just choose false and give your file a name. You already have the file name from the first step, so you can choose it from here. Type pdf as file extension and hit continue. And now test the final step.
Successful. So let's check out if it actually worked.
If I go to my Google Drive and click on the signed documents folder that I chose in the configure page of Zapier, I can see that it's already here, so our test was successful, and now we are ready to publish our Zap. So go back to Zapier and just hit Publish. In your Zap list, make sure this toggle is on. From this point forward, whenever a document becomes fully signed in fynk, Zapier will save the signed PDF to this Google Drive folder automatically.
Now that I have my zap up and running, let's check it out and let's sign a document in fynk to see if it saves it in Google Drive. So I already have this document in my account which is in signing stage and it is already signed by one party. Let's sign it as a counterparty to see what happens. I received an email from fynk inviting me to join the document and sign.
I just go down the page and add my signature.
And it's fully signed. Let's go back to our Google Drive. We should be able to see our signed document here in any moment. If I refresh And yes, here it is. That's how you can save a lot of time copy and pasting the PDF files into different folders by creating this very simple automation. Thanks for watching and I'll see you in the next video.
The goal
Keep a copy of every signed contract in Google Drive without lifting a finger. The moment a document is fully signed in fynk, Zapier grabs the PDF and files it in the Drive folder you pick.
- Build a Zap with fynk as the trigger
- Pull the signed PDF from fynk
- Save it to Google Drive on its own
Build the Zap
The whole automation is three steps inside one Zap: fynk tells Zapier a contract is signed, fynk hands over the PDF, and Google Drive files it. Open Zapier, click Create, and start a new Zap.
Set the trigger. Choose fynk as the trigger app and “New signed document” as the event, so the automation only fires once a contract is fully signed by every party. If your fynk account isn’t connected to Zapier yet, open Settings in fynk, go to API integrations, choose fynk API , and create a token to paste into Zapier. If you don’t see that option, your account owner can create the token for you.
Pull the signed PDF. Add a second step, choose fynk again, this time as an action, and pick the event “Find document download URL”. In the configure screen, click the three dots, choose Custom, and search for the Document UUID coming from the trigger. That UUID is what tells fynk which contract to hand over.
Save it to Drive. Add a third step, pick Google Drive with the “Upload file” action, and connect your Google account. Choose the drive and the folder you want, for example a “Signed documents” folder. For the file itself, use the PDF URL from the previous step, set “Convert to document” to false, name the file after the document name from the trigger, and set the extension to pdf.

Test the Zap
Test each step in Zapier before you publish anything, working top to bottom. On the trigger, pick a sample that is already a fully signed document. On the fynk action, a successful test returns the download URL for that contract’s PDF. On the Google Drive step, a successful test uploads that PDF for real.
Now open your Drive folder and confirm the file actually landed, with the right name and a readable PDF inside. If a step fails, Zapier tells you which field it choked on, and it is almost always the Document UUID mapping in the second step.
Test the automation
Hit Publish and make sure the Zap’s toggle is on. A published Zap listens for real events, which a test does not, so run one contract through properly: send a document out for signature in fynk and have every party sign it.
The moment it is fully signed, the PDF should appear in your Drive folder on its own. Follow the contract on its way there with live signature tracking , and check Zap History in Zapier if nothing shows up. From here it runs in the background, and nobody copy-pastes a signed PDF into a folder again.
What makes it fast?
No copy-pasting PDFs into folders
Every signed contract filed automatically
Set up once in about five minutes
Lands in any Drive folder you choose
Frequently asked questions.
Only fully signed documents. The Zap uses fynk's New signed document trigger, so a PDF is saved once every party has signed, not while the contract is still in progress.
Wherever you choose. In the Google Drive step you pick the drive and the folder, so every signed PDF lands in that exact location, for example a dedicated Signed documents folder.
Yes. You connect fynk to Zapier with an API token from Settings, API integrations, fynk API. If you don't see that option, your account owner can create a token for you.
Yes. Any drive and folder your connected Google account can reach is available in the Zapier step, including shared drives and nested folders.
Yes. The fynk half of the Zap stays exactly the same: the New signed document trigger, then Find document download URL. Only the last step changes, so swap Google Drive for OneDrive, SharePoint, Dropbox, Box, or any other storage app in Zapier and point it at the folder you want.
The Zapier connection runs on a fynk API token, and API access is part of the Business and Pro plans. On Free or Essential you can still file signed contracts by hand from the document, but the automation needs one of the two higher plans.
This Zap has three steps, one trigger and two actions, so it needs a Zapier plan that supports multi-step Zaps. Check your current Zapier plan before you publish, since the editor lets you build the Zap either way.
Yes. Add a filter step in Zapier straight after the trigger and let it continue only when a field matches, for example a document type, a tag, or a team. Everything that doesn't match stops there and never reaches Drive.
The file name is yours to build from trigger data, so document name, contract type, and date can all go into it. The Drive step points at one folder, so if you want contract types split across folders, run one Zap per type with a filter in front of it.
The run is held as an error in Zap History with the reason attached, and you can replay it once the cause is fixed. Nothing changes on the fynk side, so the signed contract and its PDF are always still there.
Still have questions?
Take control of your agreements. Move your business forward.
Run agreements the way they should run: fast, clear, and on your terms.
No setup headaches
Go live in days, not quarters
No lock-in
Full export anytime
No hidden fees
Unlimited signatures included





