Docupile EDRMS & Zapier Integration
Overview
Docupile now supports deep integration with Zapier, allowing users to automatically upload files from external apps.
Using Zapier, files uploaded or received in these services will be automatically pushed into your Docupile EDRMS without manual effort.
This guide explains:
- How to generate API key
- How to connect Docupile with Zapier
- How to build automation (Zaps)
- Zap examples for Gmail, Google Drive, Dropbox, OneDrive
This document is simple, step-by-step, and intended for non-technical users.
1. How Docupile – Zapier Integration Works
Zapier automates the workflow between your storage/email platforms and Docupile.
Example: A new file arrives in your Google Drive folder → Zap triggers → File automatically uploads into Docupile.
Flow Overview
2. Generating API Key in Docupile
Important Notes
- This API key stays valid until you generate a new one.
- If you regenerate the API key, old key stops working immediately.
- Do not share your API key with anyone.
- Paste this API key in all Zapier Zaps that use Docupile.
3. Using Docupile in Zapier
You will find the custom Docupile integration inside Zapier as:
App Name: EDRMS Docupile
Authentication in Zapier
Whenever Zapier asks for authentication:
Select API Key Authentication
Paste the same Docupile API key you generated earlier
After authentication, you can start building Zaps.
4. Creating Zaps (Automations)
Below are fully working Zap templates for:
Gmail
Google Drive
Dropbox
OneDrive
Use only the fields mentioned below to avoid permission or download issues.
1. Validate API Key
URL: https:///Zapier/validateApiKey
METHOD: POST
This endpoint validates the API key provided by the user for authentication.
| Header Name | Type | Description |
|---|---|---|
| Authorization | String | Required API key for authentication |
Response Error Codes
| Code | Type | Meaning |
|---|---|---|
| 200 | Success | The API key is valid. |
| 400 | Client Error | Missing or malformed headers. |
| 401 | Unauthorized | Invalid or expired API key. |
| 403 | Forbidden | Permission denied for this endpoint. |
| 429 | Too Many Requests | Rate limit exceeded. |
| 500 | Server Error | Internal error occurred. |
2. Upload File
URL: https:///Zapier/UploadFile
METHOD: POST
This endpoint uploads a file into the EDRMS using a file URL.
| Header Name | Type | Description |
|---|---|---|
| Authorization | String | Required API Key |
| Content-Type | String | Must be application/json |
JSON Body
| Field Name | Type | Description |
|---|---|---|
| file_url | String | Public file URL to upload |
Response Error Codes
| Code | Type | Meaning |
|---|---|---|
| 200 | Success | File uploaded successfully. |
| 400 | Client Error | Missing file_url or invalid request body. |
| 401 | Unauthorized | Invalid API key. |
| 403 | Forbidden | API key does not have upload permission. |
| 404 | Not Found | File URL not accessible. |
| 413 | Payload Too Large | File exceeds max upload size. |
| 415 | Unsupported | File type is not supported. |
| 429 | Too Many Requests | Rate limit exceeded. |
| 500 | Server Error | Internal upload failure |
