Protect shared PDFs with a password and send them to cloud storage in one click. Great for teams that share contracts, reports, or invoices and want a simple way to add a password before sharing.

The flow starts on demand. It downloads a sample PDF from a public link, locks the file with a password using a ConvertAPI request, then saves the result locally and uploads it to Google Drive. The HTTP Request node sends the file as form data, sets the UserPassword value, and uses a query secret for ConvertAPI. Dual outputs let you keep a local copy and a cloud copy at the same time, which helps with backup and handoff.

You will need a ConvertAPI secret and a Google Drive connection. Set your own strong password in the UserPassword field and pick the Drive folder where you want the file to go. Expect faster handoffs and fewer mistakes, often cutting the task from several minutes per file to about a minute. This setup fits use cases like sending protected proposals, securing financial statements, or sharing HR documents.

• On demand start with a manual trigger for controlled runs
• Download a PDF from a link using the HTTP Request node
• Lock the PDF with a password via ConvertAPI using form data and query auth
• Write the protected file to local disk for backup
• Upload the protected file to Google Drive in the chosen folder
• Parallel outputs after protection save time by storing in two places at once

• Reduce manual work from 10 minutes to 1 minute per file
• Automate up to 90 percent of repetitive password steps
• Eliminate most file handling errors by standardizing the steps
• Connect ConvertAPI and Google Drive in a single run
• Keep a local backup while sending a cloud copy for sharing

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Google Drive and ConvertAPI. See the Tools Required section above for links to create accounts with these services.
3. In n8n Cloud, open the HTTP Request node named Protect File with Password. In the Credential to connect with field, click Create new credential and choose HTTP Query Auth. Add the query key named secret and paste your ConvertAPI secret as the value. Save the credential.
4. Still in Protect File with Password, confirm Method is POST, Content Type is multipart form data, and Response Format is file. In Body Parameters, keep file mapped to the binary field data and set UserPassword to a strong password you will share with recipients.
5. Open the HTTP Request node named Download PDF File and verify the URL points to a valid PDF link. Make sure Response Format is file so the output is binary.
6. Open the Google Drive node. In the Credential dropdown, click Create new credential and select Google Drive OAuth2. Follow the on screen instructions to sign in and grant access to your Drive.
7. In the Google Drive node, set the target folder and file name as needed. The sample uses the root folder and a simple name. Adjust to match your naming rules.
8. Open the Write Result File to Disk node and confirm the file name and binary property are correct. Keep fileName as document.pdf or change it to match your policy.
9. Click Test workflow to run it. After the run, check the local output for the protected PDF and confirm the file appears in your chosen Google Drive folder.
10. If you get a 401 or 403 error from the protect step, check the ConvertAPI secret. If the upload fails, recheck Google Drive credentials and folder permissions. If the output is not a file, ensure both HTTP Request nodes return a file response.