Connect Folderit to Zapier
Connect Folderit to other applications with Folderit DMS on Zapier. You can start an automation when a new file is added to a selected folder, import files from another application, or use the Folderit API for a more advanced workflow. The integration is available in public beta; an invite code is not required.
Start with a ready-made Zap template
Choose a workflow below to open its guided setup in Zapier. You will connect your own accounts, choose folders and destinations, review the mapped fields, test with non-sensitive sample data, and then turn on the Zap.
Notify and track new Folderit files
Import files into Folderit
See all Folderit DMS integrations on Zapier to build another workflow.
If a template does not match your workflow, start with the Folderit events below and choose the receiving app you already use.
Before you start
- A Zapier account and a Folderit account with API access. Folderit API access is available with the Tailor plan. See API access information.
- Your Folderit API Client ID, Client Secret, and Account UID. Ask your Folderit administrator if you do not have these details.
- The UID of the Folderit folder you want to monitor or import into. This is a folder identifier, not the Account UID or the folder’s name. Your administrator can help identify it using the Folderit API.
Connect your Folderit account
- Open Folderit DMS in Zapier and create a workflow, called a Zap.
- Select Folderit DMS as the app for a step and choose the event you need.
- Choose the option to connect an account. Enter your Client ID, Client Secret, and Account UID in the connection form.
- Complete the connection test. Use an account that has access to the folders your automation needs.
Enter your Client Secret only in the account connection form. Do not put it in a workflow’s content, file metadata, or support message.
Start an automation when a new file is added
- Choose Folderit DMS and the New Folderit File event as the first step.
- Connect your Folderit account.
- Enter the folder identifier in Folderit Root UID.
- Set Include files in subfolders? to True if you also want files from folders beneath the selected folder. Leave it False to monitor only that folder.
- Test the step. If you need a new test record, add a harmless test file to the selected folder and use Find new records.
- Add an action in the receiving app. Map the file name, UID, folder path, or other available output fields into the action.
- Test the action with non-sensitive sample data, review the result, and turn on the Zap.
This is a polling trigger: it checks periodically, rather than running immediately after an upload. The interval depends on your Zapier plan. It detects new files; do not use it as a general notification for every edit to an existing document.
The trigger returns file information. A file’s URL may be empty when the API does not return one, and a link does not grant the recipient access to a private document. Check the actual test output before mapping it into another application.
Import a file into Folderit
Start with a trigger in the source application, then add Folderit DMS and choose Import File. Map the source application’s output into these fields:
| Field | What to enter |
|---|---|
| File | The source file object or a direct HTTPS download URL that Zapier can retrieve. A page that only displays a preview is not a file download. |
| Source File ID | A stable identifier for the source file. Keep it consistent when processing the same file again. |
| Source File Name | The file name, including its extension. |
| Source MIME Type | The content type, for example application/pdf. |
| Source File Size | The source file’s size in bytes. |
| Source Created At / Source Modified At | The source file’s creation and modification timestamps, preferably in ISO 8601 format. |
| Source URL | The source file’s reference URL. This is separate from the downloadable File input. |
| Folderit Root UID | The destination folder’s UID. |
| Folderit Path | Optional subfolder path beneath the destination, such as Invoices/2026. Leave blank to use the destination folder itself. |
Test with a disposable file first. Importing a file may create folders and can update or replace an existing matched document. Inspect the returned Status and Message: the status can be created, updated, skipped, or failed. Do not treat completion of the step alone as proof that the import succeeded. If later actions require a successful import, filter for the appropriate status.
Advanced API workflows
New Record polls a Folderit API GET endpoint for records. Send API Request sends a request with a selected HTTP method, endpoint path, and optional JSON parameters. These events are intended for users familiar with the Folderit API documentation. Enter the endpoint path after /v2/accounts/{account UID}, such as /entities/all. For New Record, choose a stable, unique Result ID Path so records can be recognised across polls.
Troubleshooting
- Cannot connect: check the Client ID, Client Secret, Account UID, and API access with your administrator. Reconnect the account if its credentials have changed.
- No new files: check the folder UID and subfolder setting, add a new test file, and allow for the polling interval. Previously processed files do not normally start the same Zap again.
- Import fails: inspect Status and Message, check every required source field, and confirm the File input is downloadable. Use a small test file to isolate download or size issues.
- An action did not run: open Zap History and inspect the affected step and any filters. Check that the Zap is on and that the account has available tasks.
For workflow failures, contact Zapier Support from the account running the Zap so they can inspect its history. For Folderit API access or folder permissions, contact Folderit. Include the event name, error text, and time of failure, but never include credentials or confidential document content.