Folderit is a document management system (DMS). Its integrations connect document work to the tools your organization already uses. Some help people edit or collect documents, others manage sign-in, and others connect a document process to an external application.
The right connection depends on the task. Signing in through an identity provider is different from provisioning users; saving an email attachment is different from synchronizing two document libraries. This guide explains the available options and the decisions to make before enabling them.
Microsoft Office 365 and Outlook
The Microsoft Office 365 integration lets users create and edit Office documents directly in Folderit. It is useful when the document should remain part of the Folderit filing and access structure while people work on its content.
The Folderit Outlook add-in lets users save selected emails and attachments to a Folderit folder. For example, an employee can file supplier correspondence beside the relevant invoice or contract. Decide which messages belong in the record and who is responsible for selecting the correct destination.
These capabilities do not, by themselves, mean that every Office or SharePoint location is synchronized with Folderit. If your process needs data to move between systems, define the transfer separately and verify the available connector or API operations.
Single sign-on and user provisioning
Folderit supports single sign-on through Okta SAML, Microsoft Entra ID and Google SAML. Single sign-on lets an organization use its identity provider for authentication.
Folderit also documents Okta SCIM user provisioning. Provisioning manages user lifecycle actions; it is a separate capability from signing in. Do not assume that configuring SAML automatically creates the intended users, removes departed staff or applies every document permission.
Before rollout, test an ordinary user, an administrator and a departing user’s access. Document who owns the identity configuration and check Folderit’s actual folder and item permissions. An identity connection should fit your access model, not substitute for designing it.
DocuSign and electronic-ID signing
The DocuSign integration sends documents stored in Folderit for signature through a connected DocuSign account. It is available on Folderit’s Medium and Tailor plans and requires a separate DocuSign subscription and available envelopes. For the connection steps and workflow choices, see the Folderit DocuSign integration guide.
Folderit also supports electronic-ID signing using supported national identification methods, including ID-card, Smart-ID and Mobile-ID. Method availability and the required signature level should be checked for the people and documents involved.
Folderit’s native electronic-signing method is another option, distinct from the DocuSign integration. Compare the actual signing requirements, recipient experience and plan terms before choosing a method. Connecting a signing service does not make every document compliant with every jurisdiction’s formalities.
Make and viaSocket for application workflows
Make, formerly Integromat, and viaSocket can connect Folderit to other applications. These automation platforms are useful when a process needs actions across systems rather than only within Folderit.
Begin with a specific requirement: which event starts the process, which document or record should move, and what information must accompany it? Then verify that the chosen platform provides the necessary operations. A platform listing does not guarantee that every feature in either connected application is available through its connector.
- Ownership: choose which system holds the authoritative record and which receives a copy or reference.
- Field mapping: define names, dates, currencies and required values before transferring data.
- Duplicate handling: decide what happens when the same event is delivered twice.
- Failures: assign someone to review unsuccessful runs and establish a safe retry process.
- Permissions: confirm what the connection can access and what users can access after a transfer.
Folderit’s knowledge base describes Make and viaSocket as providing automation functionality similar to Zapier and Microsoft Power Automate. That comparison should not be read as a claim that Folderit has a native connector for every one of those platforms.
Microsoft Power Automate and Folderit DMS
Folderit is developing a Microsoft Power Automate connector for document management. It is currently a private development preview and is not yet available in Microsoft’s public connector catalog.
The development connector supports creating folders, finding records, uploading and downloading documents, adding file versions, and reading and updating supported metadata. These document operations have been tested in a Folderit demo account, including a successful Power Automate flow that downloaded a file and passed its exact contents to the next step.
If you are evaluating a document management system (DMS) for Power Automate, start with one concrete requirement: file an incoming attachment, store a document generated by another business application, or retrieve the current version of a controlled document. Connections to Outlook, SharePoint, Teams or another application must be configured and tested for your process; those complete workflows are not implied by the development test.
Power Automate custom connectors require an eligible Microsoft license. The Folderit connection uses an authorized user’s existing permissions. Confirm Folderit API access, Microsoft licensing, field mapping and duplicate handling before rollout.
Contact Folderit about your Power Automate document-management requirements. We can discuss the current connector status and the work needed for your systems. Public catalog availability will be announced after certification and release.
WordPress document and e-form plugins
The Folderit document plugin, currently in beta, embeds lists of downloadable files from a Folderit account on a WordPress website. Choose the documents intended for website visitors and test the resulting access before publishing a list.
The Folderit e-forms plugin hosts Folderit e-forms on a WordPress website and sends submitted data to Folderit. Define the destination, fields and follow-up process so a submission becomes an actionable record.
The current integrations knowledge-base page links to the plugin downloads and individual setup guides.
The Folderit API for custom connections
Folderit’s public API documentation provides the starting point for a custom integration. This route is appropriate when the required workflow is specific to your systems or is not covered by an available connector.
Ask the implementer to demonstrate the exact operations your process needs. Agree on access scope, error handling, ownership and maintenance, including what happens if either service changes. An API makes integration possible; building and operating the connection remains a separate piece of work.
Use a proof of concept to choose the right approach
Start with a small set of representative documents and written acceptance criteria. Check the successful path, an invalid input, a repeated event, an unavailable service and a user who should not have access.
For example, a document-transfer test should confirm that the correct file and metadata arrive, that retries do not create unwanted duplicates, and that someone can diagnose a failed transfer. Our DMS proof-of-concept guide helps structure that evaluation.
Use built-in connections where they meet the requirement, automation platforms for supported cross-application steps, and a custom API implementation when the process needs it. Confirm the required Folderit plan and any external subscription before rollout, using the current knowledge-base setup instructions.
