Trusted Signatures Zapier Integration
Sign PDFs without code using our Zapier integration and get the Adobe Acrobat green checkmark.
Table of Contents
- What You Can Do
- Prerequisites
- Step-by-Step Setup
- Field Reference
- Common Use Cases
- Testing & Troubleshooting
- Support
What You Can Do with the Zapier Integration
Automate PDF signing workflows:
- Sign PDFs from Google Drive, Dropbox, OneDrive
- Trigger signing when e.g., a form submits, or spreadsheet updates
- Send signed PDFs via email, Slack, or cloud storage
- Get Adobe Acrobat green checkmark verification for compliance
Prerequisites
- Zapier account (free or paid)
- Trusted Signatures account with API access
- Basic Zapier knowledge (creating Zaps, connecting apps)
- PDF source (Google Drive, form uploads, etc.)
Step-by-Step Setup Guide
Step 1: Create Your Trigger

Choose your PDF source (Google Drive, form submission, etc.). This triggers when new PDFs need signing.
Step 2: Configure PDF Source

Set up your PDF source trigger. Common sources:
- Google Drive: New file in folder
- Forms: New form submission with PDF
- Email: New email attachment
- Dropbox/OneDrive: New file upload
Step 3: Add Trusted Signatures Action
Authentication Setup:
Go to Trusted Signatures Dashboard
Create a new API Key with a descriptive name
Copy the API Key ID and API Key
In Zapier, paste these into the authentication fields
When you're done, the fields should be configured
Step 4: Configure PDF Signing

Required Fields:
- PDF To Sign: Select from previous step
- Filename: Original name or custom
Step 5: Set Up Output Destination

Popular Destinations:
- Email: Send as attachment
- Google Drive: Save to folder
- Slack: Share in channel
- Dropbox: Upload to folder
Field Reference
Sign PDF Action Fields
Field | Required | Description | Example |
---|---|---|---|
PDF File | ✅ | PDF file to sign | From Google Drive trigger |
Filename | ✅ | Output filename | contract (signed).pdf |
Common Use Cases
1. Contract Workflow
Trigger: New Google Docs → PDF in Drive
Action: Sign PDF
Output: Email to client + save to “Signed Contracts” folder
2. Form Processing
Trigger: New Typeform submission with PDF
Action: Sign PDF
Output: Send via Slack notification
3. Compliance Documents
Trigger: New file in “Pending” folder
Action: Sign with timestamp
Output: Move to “Completed” folder
Testing & Troubleshooting
Testing Your Zap
- Use Zapier’s “Test” button for each step
- Check that PDF file transfers correctly
- Verify signed PDF has green checkmark in Adobe Acrobat
- Confirm output destination receives file
Common Errors
Authentication Failed
- Verify API Key ID and API Key are correct
- Check API key hasn’t expired
PDF Processing Error
- Confirm file is a valid PDF
File Not Found
- Ensure PDF file field is mapped correctly
- Check file permissions in source system
- Verify file exists when Zap runs
Support
Need help? Contact us:
- Matrix Support: #support:trusted-signatures.com
- Email: support@trusted-signatures.com
- Documentation: API Docs