- Home
- Resources
- Integrations
- Folderit DMS
Folderit DMS Zapier integrationAutomate Folderit DMS with Zapier.
The Folderit DMS Zapier integration gives you 2 triggers and 2 actions, and nothing more. Both triggers check Folderit on a timer, the app runs on the free plan (Zapier still tags it beta), and you pay in tasks: one per action that succeeds.
Beta app Zapier still marks this integration as beta.
Verified Trustpilot reviews · AI, automation & growth agency
What the Folderit DMS Zapier integration actually does
It links your Folderit document space to the other tools your team uses, without code. Zapier watches a Folderit folder or an API path, and when something new shows up, it hands it to the next app. In the other direction, it can drop a file into a Folderit folder or call the Folderit API for you.
Three results come up again and again. First, a heads-up: New Folderit File spots a document added to a folder, and the next step warns the right person in a chat tool or creates a to-do. Second, a filing job: Import File places a file coming from an earlier step into the folder you pick, so nobody has to download and re-upload it. Third, the custom route: New Record and Send API Request read from or write to any Folderit API path you type, which covers what the two ready-made operations leave out.
Now the limits. There is no instant trigger here: both triggers poll, so on the free plan a new file can wait up to 15 minutes before the Zap notices it. There is no search step either, so a Zap cannot look up an existing Folderit file by itself. Moving, renaming or deleting has no dedicated action; the only door left open is Send API Request, and it expects you to know the API path you are after.
Comparing tools? The Folderit DMS Make integration page covers the same app on the other side, and the n8n vs Zapier comparison helps you pick a platform before you build anything.
The Zapier words you'll meet on this page
Eight terms, one line each. Read them once and the rest of the page goes faster.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event that starts the Zap. With this app, it is a new file in a Folderit folder or a new record returned by the API.
- Action
- The step that does the work once the Zap is running: here, importing a file into Folderit or sending it an API request.
- Task
- The unit Zapier bills: one action that completes successfully. The free plan gives you 100 of them every month.
- Polling vs instant
- Polling means Zapier asks the app for new items on a timer. Instant means the app calls Zapier itself. Both Folderit triggers poll.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
- Connection
- Your Folderit account linked to Zapier once, then reused by every step of every Zap that touches Folderit DMS.
- Multi-step Zap
- Anything beyond one trigger and one action. A second action or a filter turns a Zap into one, and it then needs a paid plan.
What a Folderit DMS Zap costs you
Watching Folderit is free. Zapier only counts the actions that go through.
- Trigger check0 task
- Successful action1 task each
- Free plan100 tasks a month, two-step Zaps
- Premium appNo, works on Free (beta)
The trigger never costs a task, however often Zapier checks the folder. Each action that succeeds counts once, and an action that fails is not billed. Folderit DMS is not a premium app, so the free plan is enough to start. That plan stops at two steps, though: one trigger, one action. Add a filter or a second action and the Zap becomes multi-step, which means a paid plan. Plan for that before you sketch a bigger workflow.
Connect your Folderit account in three moves
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. Have your Folderit login ready, with access to every folder you want the Zap to read or fill.
- 02
Pick Folderit DMS
Type Folderit DMS in the search box of the dialog, select it, then click Add connection. The connection you create here is the one every future Folderit step will reuse.
- 03
Sign in and allow access
Log in to Folderit in the tab that opens and grant Zapier access to the account. Once that is done, the connection shows up on the Apps page, ready to be picked in the editor.
Your first Zap: a Slack ping when a client file lands
GoalAn accounting team gets a Slack message in its channel when a client drops a matching document into a shared Folderit folder.
- 01
Create the Zap and set the trigger
Create a new Zap, pick Folderit DMS as the app and New Folderit File as the event. Choose your connection, then fill in the Root UID of the shared client folder.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent files of that folder, so you work on a real one. Note which value tells you a file is worth a message.
- 03
Add the filter
Click the plus icon, choose Filter, then set the field, the rule and the value spotted in the test. Pick a text rule for text, or the filter will never pass.
- 04
Add the Slack action
Add Slack with Send Channel Message, pick the channel and map the file details from the trigger into the message. Test this step once and read what came back.
- 05
Publish
Click Publish to switch the Zap on. With a filter it is a multi-step Zap, so it needs a paid plan; on Free, drop the filter and keep two steps.
Folderit DMS triggers
2 events start a Zap when something happens in Folderit DMS. Zapier checks for them at the interval your plan allows.
New Record
Polling triggerIn Zapier“Triggers when a Folderit API GET request returns a new record.”
Point this trigger at a path of the Folderit API and it starts the Zap each time that path returns a record it has not seen before. It is the open-ended option: whatever the API can list, this trigger can watch.
/entities/all.New Folderit File
Polling triggerIn Zapier“Triggers when a new file is added to the selected Folderit folder, optionally including subfolders.”
This one keeps an eye on a single Folderit folder and starts the Zap whenever a file is added to it. A checkbox lets you stretch the watch to the subfolders as well, which matters for folder trees sorted by client or year.
Folderit DMS actions
Folderit DMS gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Send API Request
ActionIn Zapier“Sends a request to a Folderit API endpoint with custom parameters.”
Calls a Folderit API path with the method and parameters you set. Think of it as the spare key for anything the Import File action does not do.
/folders.Import File
ActionIn Zapier“Imports a file into the selected folder.”
Drops a file handed over by an earlier step into the Folderit folder you choose, so the document ends up filed without a manual download.
When a Folderit DMS Zap breaks
Zapier links no help article to this app, so the traps below are the ones every Zap meets.
None of them is specific to Folderit. They still hit document workflows harder than most, because folders fill up in bulk and files are easy to write back where they came from. If one of them bites anyway, the Zapier troubleshooting page walks through the fixes.
Old files are never picked up
A Zap only reacts to files added after you publish it. The documents already sitting in the folder stay where they are; moving that backlog is a separate job.The Zap sets itself off
Import a file into the very folder that New Folderit File watches and every import starts the Zap again. The task count drains fast, so aim at another folder.A bulk upload gets held back
Drop hundreds of scans at once, after a migration for example, and Zapier's flood protection can hold that huge batch back instead of running it.The same file never runs twice
Zapier remembers what a polling trigger has already returned. A file that shows up in several checks still starts the Zap once, which is usually what you want.
Need help automating Folderit DMS with Zapier?
A person reads every message.



