I’m hoping to get some help, I’m stuck on how to create a multiple page PDF with dynamic data.
Can I use the PDF Conjurer to conjure dynamic PDF files by nesting a child API workflow inside the parent API workflow? Or can dynamic PDF’s only be conjured using the repeating structures?
In the screenshot, I nested another API workflow that runs on a list of things. Inside of Step 3 there is Add Image and Add Text actions by Conjurer. These get stored in a data field, and later used in the Step 4 Conjure PDF action. The issue is when Step 3 runs on a list that has more than 1 (so 2 or more) images/texts, it doesn’t create a file. I am not sure if the setup is not right or if that is a bug.
In this next screenshot, there are 2 strings that are being passed from Step 3 - each containing image and text (beginning of string is highlighted in yellow to easily find it in this chunk of code), and when this is the input in the Step 4 Conjure PDF action, the file is not created.
So the file is generated only when there is 1 such string, but when there are 2 or more, like shown in the screenshot, nothing happens.
I am not sure if this is a bug or nothing happens because nested API creates strings that are not recognizable by Conjure PDF action.
This is Zeroqodes PDF Conjurer plugin.
If someone has achieved creating a multi page PDF with dynamic content, be it with the Conjurer plugin or some other plugin, I’d love to learn from your experience.
Thanks for following up and providing more detail.
Based on what you’ve shared, it seems the issue isn’t with the plugin itself but with how the configuration object is being passed and accumulated across your nested workflow.
As mentioned earlier, we don’t currently have a documented use case for generating multi-page PDFs using nested workflows with the PDF Conjurer plugin. That said, your approach is technically feasible — but it depends heavily on how the configuration object is handled.
The Conjure PDF action expects a single, accumulated configuration object. If your nested API workflow returns a list of configuration chunks (as suggested by your screenshots), the final step won’t work.
Recommended Flow
Initialize PDF Document → creates base config.
Schedule API Workflow on a List → pass the base config into the child workflow.
Conjure PDF → use the final, single config returned from the child workflow.
Child API Workflow (build-drill-pages):
Start with the incoming config.
For each item:
Add Image
Add Text (chained from the previous)
Update the config sequentially.
Return one final config object with all additions applied.
Alternative Option
If the nested setup becomes too complex, using repeating structures in the main workflow can simplify this — they allow you to iterate over dynamic content while maintaining proper configuration chaining.
