The flow
Starts it 1Service 14
The steps in the order they run, from what starts it.
- 1List TemplatesHttp Request ToolService
- 2Create TemplateHttp Request ToolService
- 3PreviewHttp Request ToolService
- 4DeleteHttp Request ToolService
- 5List Templates 1Http Request ToolService
- 6Update TemplateHttp Request ToolService
- 7Generate PdfHttp Request ToolService
- 8List Http Request ToolService
- 9CreateHttp Request ToolService
- 10Delete Http Request ToolService
- 11Get TemplateHttp Request ToolService
- 12UpdateHttp Request ToolService
- 13Get FileHttp Request ToolService
- 14FillHttp Request ToolService
- 15doqs.dev | PDF filling MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 15
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 15 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Before you run itNothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 15 steps before you point it at anything that matters.