I’ve encountered a limitation you might want to know about.
Basically, if you use this plugin in a backend workflow and if a step returns no data, then the workflow will cause an error.
For example, when using this plugin in a backend workflow, if you use an “Add table” action that returns no data (eg DoSearchFor = 0 items) AND this table has no header, then this will cause an error in your workflow.
If it has either content or a header it will work.
So this is important if you’re not sure what will be the exact content of your PDF and if some searches might be empty.
Here’s a workadound you might want to use (with screenshot below):
- Put a condition on the action for it to run only if it’s not empty.
For example, if your table has a DoSearchFor Users, then your condition would be DoSearchFor Users :count >0
- However, doing this, you are creating a second problem: since this action will not always run, then you can’t reference it’s base64 content in further steps (when you fill “Previous step result”). Because it will return an empty content
- So you have to store that content in your database after each step, and use that field as a reference for “Previous step result”