DocuMotor - Frequently asked questions | Document Automation

Frequently asked questions about DocuMotor

There are many opportunities associated with DocuMotor and document automation in general:

What is it, how can I use it the best, is it relevant for my business, is it safe, and so on?

We’ve listed the 14 most asked questions about DocuMotor below.

If you can’t find the answer to your questions, please get in touch with one of our document automation experts. 

Frequently asked questions about DocuMotor

1. Which output formats are supported?
Currently, we support Word, PowerPoint, HTML, Plain Text, and PDF.

2. Why are you using MS Office for document automation?
Our experience from more than a decade helping enterprises with MS Office templates and automation is that the admin experience in non-MS Office file-based solutions gets difficult and, in some cases, “unfriendly.”

By using MS Office files for automation, we ensure that all of the visual elements supported by MS Office are backed by our tools and admins can do most of the graphic work and set up connectors without any programming skills.

3. Do I need a dedicated server with MS Office running?
We use the MS Office file format and allow admins to maintain core visuals and automation items in MS Office files where needed. Our Automation Services will typically run using OpenXML, and you will, therefore, not be relying on a server-side MS Office installation.

4. What happens once the document is populated?
Our services will send the document/presentation/PDF to your web application if no end-user input is needed. If end-user finalization is required, the populated file is available for editing using ordinary MS Office.

5. Will you have access to all our files processed?
Our solution runs in memory. We do not store any files. If you are using sensitive data, we offer our service to run in your own Azure infrastructure.

6. Do you have a maximum capacity for documents/presentations?
Our services run in Azure and are fully scalable.

7. Do you integrate to common workflow/document management tools?
Our services have a native API, but we also offer custom APIs to this so that you do not need to adjust your tools/services.

8. What integrations have you done with the Document Automation Services so far?

9. Can your Automation Services manage more than plain text?
Absolutely. While creating documents and presentations, we support inserting images and rich text (OpenXML/HTML formatted). Tables and charts with formatting are also fully supported.

10. Can the Omnidocs Automation Services run on more integrations simultaneously?
As we are not SharePoint/Salesforce/SAP/… specific but act on data that is sent to us from these services, our Automation Services can run on top of multiple data inputs if needed.

11. How are your services usually triggered?
They are either triggered by a user in, e.g., Salesforce. It could be on an opportunity – we then generate the quote based on data on the given opportunity. It could also be triggered by an event with no user action required.

12. How does a collaboration with Omnidocs on Automation Services typically work out?
Most of our clients have an existing dataset and can push these data to us. With this, we can do a POC to show that the data streams/document streams work as expected.

13. Is it possible to manage changes to the documents/presentations on our own once the document automation is set up?
When handing over the solution, we will have set up the initial document(s) and or presentation(s) and give you training in how you can do more documents and/or connect more data to the service. There is no dependency on our consultants, but we are happy to help you configure the tools as well as explore further options using the tools.

14. The integrations to your document automation service, can they also be used inside MS Office
triggered by a user?
Integrations to MS Office are something we are just as focussed on as automation. Our in-office integrations are typically user-invoked and can trigger lookups in Templafy/Excel sheets/SharePoint lists/SharePoint documents, Jira/web services, etc.
The purpose is to allow users to not need to visit other tools and/or go through a massive copy/paste exercise to update documents/presentations. Read more on this at