Feature Requests

When generating PDFs from Google Docs templates using DocsAutomator, page breaks are not always preserved correctly when dynamic content varies in length. For example, a template may be structured as: Page 1: Main document content Page 2: Appendix, form, or follow-up section If the data populated on Page 1 becomes longer than expected, Page 2 may start at the bottom of the same page instead of beginning on a new A4 page in the generated PDF. While Google Docs supports manual page breaks and document tabs, these solutions are currently not reliable in this workflow: Manual page breaks are not consistently enforced during PDF generation when content expands dynamically. Document tabs (feature in Google Docs) are not recognized by DocsAutomator, as only the first tab is processed. It would be very helpful to have support for forced page breaks or clearly defined section boundaries in templates, ensuring that specific sections always start on a new page in the generated PDF regardless of content length. This feature would be particularly valuable for structured or formal documents where correct pagination is required.

Love being able to set conditional formatting, but it would be great if I could set a variable to be checked against - not just hard coded text. ie - If {{tag}} = {{tag-to-highlight}} then highlight This way, I could dynamically set which "Tags" for example are highlighted.

Please add DocsAutomator as a native app/module in Make, allowing template selection, field mapping, and API authentication without using raw HTTP modules.

Has there been any thought to adding a feature that would allow us to create pivot tables with Airtable data? This would be a very useful feature for me and I'm sure many others. Thanks.

Would like the possibility to pull linked record data that goes further than one table deep. Right now multiple line items tables must all be linked in the primary table.

Add a simple feature in DocsAutomators interface for every automation: “do you want to copy field mapping from a different base?”. This will speed up the mapping process in case you are duplicating an airtable base and want to replicate the same DocsAutomator automation in that new base.

When having a detailed invoice with hundreds of items including tax calculations and if/then functions, doing all calculations in a single row of a data source (whether Google Sheets, Glide, Airtable, etc) can be extremely cumbersome. In this case, it would be more efficient to use Google Sheets as the template (just as Google Docs is now) to be able to import the source data per row into it, then allow Google Sheets functions to compute related columns, then finally export as PDF.

Softr integration as part of Softr Workflows suite