As you mentioned, Enfocus does this with PDFs.
When i say data driven, n8n, Zapier they all process data. Enfocus actually moves a PDF through folders with data.
I personally wouldn't use a cloud base system that does what enfocus does.
Why? because now if i have files on my PC, i need to upload & download them. sure, i could connect website to a cloudbase version, prepress, then send to my pc, etc.
and i believe most RIPs could do the same level of prepress that you could do on a cloud version if there was a such thing.
For example, we have enfocus doing a lot of stuff. Generating cut files, Print ready files. Data for other apps. so we have files pushed to different machines, RIPs and other apps internally.
The Zapier vs N8N, i've used both. Zapier is more for the end user as they make things more simple. n8n is more for the individual with a larger skill set as you can do way more with it an do more complex routes.
n8n is also opensource, you can self host it on your own server. that gives you more options such as picking up files from a local PC, rather than uploading them to drobox or google drive.
Although you could use an app called NodeRed, which again is self hosted and can process PDFs though folders. But you need to script all prepress actions and i dont think it can carry metadata. Been a while since i've used it.
Hi Pauly,
Thanks for your insights! I appreciate your input and want to add a few thoughts—not to oppose your thoughts, but to explore some possibilities that could open up if more vendors embraced low-code platforms.
You're absolutely right; the idea of repeatedly uploading and downloading files seems inefficient. Imagine if more print-centric cloud services integrated with automation platforms like Zapier. This could allow files to remain in the cloud until they're ready for final printing on the ground. BTW, I’m using Zapier as an example here, simply because it's widely recognized. As you know there are other solutions.
Consider this: our system, Good2Go, incorporates Pitstop for PDF preflight. Its possible that we could allow users full access to custom preflight profiles and action lists. Similarly, every file processed through Good2Go generates a dataset containing customer information, document details, and preflight results. This rich metadata, much like that in Switch, can trigger, route, and sort files based on various conditions.
With access to action lists in Good2Go, if a file needed bleed added, this adjustment could be managed directly within the cloud through a workflow or manually by an operator. The file remains securely in the cloud application, reducing unnecessary movement. Whether it’s user-initiated or automatically triggered by Switch or even Zapier, the process stays streamlined. Once the bleed is made, the workflow along with Good2Go could route the file back to prepress as an electronic proof for approval or rejection—again, without any physical file transfer.
Now, imagine if Ultimate Impostrip had a cloud service for imposition supported both Switch and Zapier. The file could be imposed directly from a checkpoint in Switch or a custom trigger in Good2Go, moving seamlessly in the background between services.
The bottom line is, whether it's Switch, Zapier, Make.com, or n8n, data drives the automation, and files can be passed between cloud systems securely and easily, not bogging down networks with multiple copies, corrections, or production versions.
Plus, by integrating more cloud-based pre-production and print production applications with platforms like Zapier, files could feasibly remain in the cloud for the majority of their processing journey until final print.
What we really need to push the industry forward is broader support for a few key integration and automation platforms like Zapier, Make.com, or n8n. This will drive our industry into the future.
Looking forward to more discussions on this topic and exploring how we can collectively move towards these innovations!
All the best,
Michael